Win 10 PC ethernet cable stuck in “unplugged” and “identifying” loop












1















I have a PC that has problems connecting to the internet via cable. The ethernet adapter is stuck in a loop of "cable unplugged" "identifying" "unknown network" and back to "cable unplugged". After random amount of times of the loop, it successfully connects to the internet. Sometimes 10min, sometimes 1 hour.
Video of it: https://vimeo.com/313365533?



I have tried so far:




  • Verified that cable and router are not the problems. Same setup works on other machine.

  • Tried uninstalling, reinstalling, updating, enabling and disabling the Realtek PCIe GBE Family Controller driver in various forms

  • Changed the "Speed and Duplex" from Auto Negation to "100MBps Full Duplex". I also tried all the other forms. But this one made the loop faster so to speak.

  • IPConfig shows only "Media Disconnected"


I have looked at similar questions and none have provided a solution for it for me. I have 50/50 mbps connection coming in through the cable, not sure if that's related. I have a CAT5+ cable that should support up to 100Mpbs. Regardless this started happening randomly after the PC crashed yesterday. (Literally closed down). Maybe it shorted something somewhere and the hardware has now become faulty? How can I make sure?



Best regards










share|improve this question













migrated from serverfault.com Jan 25 at 13:03


This question came from our site for system and network administrators.



















  • Regarding your 3rd point, disabling autonegotiation will only make things worse (unless it's changed identically on both ends of the cable). Most Ethernet devices, if they don't receive an autonegotiation signal, will use the slowest 10M/Half mode.

    – grawity
    Jan 25 at 13:29











  • Verified that cable and router are not the problems - How did you verify that? Also, have you replaced the network adapter?

    – joeqwerty
    Jan 25 at 13:38











  • I have tested the cable coming from the router on other machines and it works just fine. What's weird is that after X amounts of retries, it gets and stays connected until next reboot/hibernate. I have not replaced the adapter yet. Leaving that as a last resort. @joeqwerty

    – student126
    Jan 25 at 14:57








  • 1





    Why would you leave replacing the adapter as a last resort? You've looked at all of the obvious causes except the adapter. What are you going to do, keep chasing a ghost? Replace the adapter and see if that resolves the problem. With network problems you should always troubleshoot from the physical layer up, that means replacing the adapter. Only by doing that can you rule it out.

    – joeqwerty
    Jan 25 at 16:20
















1















I have a PC that has problems connecting to the internet via cable. The ethernet adapter is stuck in a loop of "cable unplugged" "identifying" "unknown network" and back to "cable unplugged". After random amount of times of the loop, it successfully connects to the internet. Sometimes 10min, sometimes 1 hour.
Video of it: https://vimeo.com/313365533?



I have tried so far:




  • Verified that cable and router are not the problems. Same setup works on other machine.

  • Tried uninstalling, reinstalling, updating, enabling and disabling the Realtek PCIe GBE Family Controller driver in various forms

  • Changed the "Speed and Duplex" from Auto Negation to "100MBps Full Duplex". I also tried all the other forms. But this one made the loop faster so to speak.

  • IPConfig shows only "Media Disconnected"


I have looked at similar questions and none have provided a solution for it for me. I have 50/50 mbps connection coming in through the cable, not sure if that's related. I have a CAT5+ cable that should support up to 100Mpbs. Regardless this started happening randomly after the PC crashed yesterday. (Literally closed down). Maybe it shorted something somewhere and the hardware has now become faulty? How can I make sure?



Best regards










share|improve this question













migrated from serverfault.com Jan 25 at 13:03


This question came from our site for system and network administrators.



















  • Regarding your 3rd point, disabling autonegotiation will only make things worse (unless it's changed identically on both ends of the cable). Most Ethernet devices, if they don't receive an autonegotiation signal, will use the slowest 10M/Half mode.

    – grawity
    Jan 25 at 13:29











  • Verified that cable and router are not the problems - How did you verify that? Also, have you replaced the network adapter?

    – joeqwerty
    Jan 25 at 13:38











  • I have tested the cable coming from the router on other machines and it works just fine. What's weird is that after X amounts of retries, it gets and stays connected until next reboot/hibernate. I have not replaced the adapter yet. Leaving that as a last resort. @joeqwerty

    – student126
    Jan 25 at 14:57








  • 1





    Why would you leave replacing the adapter as a last resort? You've looked at all of the obvious causes except the adapter. What are you going to do, keep chasing a ghost? Replace the adapter and see if that resolves the problem. With network problems you should always troubleshoot from the physical layer up, that means replacing the adapter. Only by doing that can you rule it out.

    – joeqwerty
    Jan 25 at 16:20














1












1








1








I have a PC that has problems connecting to the internet via cable. The ethernet adapter is stuck in a loop of "cable unplugged" "identifying" "unknown network" and back to "cable unplugged". After random amount of times of the loop, it successfully connects to the internet. Sometimes 10min, sometimes 1 hour.
Video of it: https://vimeo.com/313365533?



I have tried so far:




  • Verified that cable and router are not the problems. Same setup works on other machine.

  • Tried uninstalling, reinstalling, updating, enabling and disabling the Realtek PCIe GBE Family Controller driver in various forms

  • Changed the "Speed and Duplex" from Auto Negation to "100MBps Full Duplex". I also tried all the other forms. But this one made the loop faster so to speak.

  • IPConfig shows only "Media Disconnected"


I have looked at similar questions and none have provided a solution for it for me. I have 50/50 mbps connection coming in through the cable, not sure if that's related. I have a CAT5+ cable that should support up to 100Mpbs. Regardless this started happening randomly after the PC crashed yesterday. (Literally closed down). Maybe it shorted something somewhere and the hardware has now become faulty? How can I make sure?



Best regards










share|improve this question














I have a PC that has problems connecting to the internet via cable. The ethernet adapter is stuck in a loop of "cable unplugged" "identifying" "unknown network" and back to "cable unplugged". After random amount of times of the loop, it successfully connects to the internet. Sometimes 10min, sometimes 1 hour.
Video of it: https://vimeo.com/313365533?



I have tried so far:




  • Verified that cable and router are not the problems. Same setup works on other machine.

  • Tried uninstalling, reinstalling, updating, enabling and disabling the Realtek PCIe GBE Family Controller driver in various forms

  • Changed the "Speed and Duplex" from Auto Negation to "100MBps Full Duplex". I also tried all the other forms. But this one made the loop faster so to speak.

  • IPConfig shows only "Media Disconnected"


I have looked at similar questions and none have provided a solution for it for me. I have 50/50 mbps connection coming in through the cable, not sure if that's related. I have a CAT5+ cable that should support up to 100Mpbs. Regardless this started happening randomly after the PC crashed yesterday. (Literally closed down). Maybe it shorted something somewhere and the hardware has now become faulty? How can I make sure?



Best regards







networking ethernet drivers cable






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 25 at 12:59









student126student126

62




62




migrated from serverfault.com Jan 25 at 13:03


This question came from our site for system and network administrators.









migrated from serverfault.com Jan 25 at 13:03


This question came from our site for system and network administrators.















  • Regarding your 3rd point, disabling autonegotiation will only make things worse (unless it's changed identically on both ends of the cable). Most Ethernet devices, if they don't receive an autonegotiation signal, will use the slowest 10M/Half mode.

    – grawity
    Jan 25 at 13:29











  • Verified that cable and router are not the problems - How did you verify that? Also, have you replaced the network adapter?

    – joeqwerty
    Jan 25 at 13:38











  • I have tested the cable coming from the router on other machines and it works just fine. What's weird is that after X amounts of retries, it gets and stays connected until next reboot/hibernate. I have not replaced the adapter yet. Leaving that as a last resort. @joeqwerty

    – student126
    Jan 25 at 14:57








  • 1





    Why would you leave replacing the adapter as a last resort? You've looked at all of the obvious causes except the adapter. What are you going to do, keep chasing a ghost? Replace the adapter and see if that resolves the problem. With network problems you should always troubleshoot from the physical layer up, that means replacing the adapter. Only by doing that can you rule it out.

    – joeqwerty
    Jan 25 at 16:20



















  • Regarding your 3rd point, disabling autonegotiation will only make things worse (unless it's changed identically on both ends of the cable). Most Ethernet devices, if they don't receive an autonegotiation signal, will use the slowest 10M/Half mode.

    – grawity
    Jan 25 at 13:29











  • Verified that cable and router are not the problems - How did you verify that? Also, have you replaced the network adapter?

    – joeqwerty
    Jan 25 at 13:38











  • I have tested the cable coming from the router on other machines and it works just fine. What's weird is that after X amounts of retries, it gets and stays connected until next reboot/hibernate. I have not replaced the adapter yet. Leaving that as a last resort. @joeqwerty

    – student126
    Jan 25 at 14:57








  • 1





    Why would you leave replacing the adapter as a last resort? You've looked at all of the obvious causes except the adapter. What are you going to do, keep chasing a ghost? Replace the adapter and see if that resolves the problem. With network problems you should always troubleshoot from the physical layer up, that means replacing the adapter. Only by doing that can you rule it out.

    – joeqwerty
    Jan 25 at 16:20

















Regarding your 3rd point, disabling autonegotiation will only make things worse (unless it's changed identically on both ends of the cable). Most Ethernet devices, if they don't receive an autonegotiation signal, will use the slowest 10M/Half mode.

– grawity
Jan 25 at 13:29





Regarding your 3rd point, disabling autonegotiation will only make things worse (unless it's changed identically on both ends of the cable). Most Ethernet devices, if they don't receive an autonegotiation signal, will use the slowest 10M/Half mode.

– grawity
Jan 25 at 13:29













Verified that cable and router are not the problems - How did you verify that? Also, have you replaced the network adapter?

– joeqwerty
Jan 25 at 13:38





Verified that cable and router are not the problems - How did you verify that? Also, have you replaced the network adapter?

– joeqwerty
Jan 25 at 13:38













I have tested the cable coming from the router on other machines and it works just fine. What's weird is that after X amounts of retries, it gets and stays connected until next reboot/hibernate. I have not replaced the adapter yet. Leaving that as a last resort. @joeqwerty

– student126
Jan 25 at 14:57







I have tested the cable coming from the router on other machines and it works just fine. What's weird is that after X amounts of retries, it gets and stays connected until next reboot/hibernate. I have not replaced the adapter yet. Leaving that as a last resort. @joeqwerty

– student126
Jan 25 at 14:57






1




1





Why would you leave replacing the adapter as a last resort? You've looked at all of the obvious causes except the adapter. What are you going to do, keep chasing a ghost? Replace the adapter and see if that resolves the problem. With network problems you should always troubleshoot from the physical layer up, that means replacing the adapter. Only by doing that can you rule it out.

– joeqwerty
Jan 25 at 16:20





Why would you leave replacing the adapter as a last resort? You've looked at all of the obvious causes except the adapter. What are you going to do, keep chasing a ghost? Replace the adapter and see if that resolves the problem. With network problems you should always troubleshoot from the physical layer up, that means replacing the adapter. Only by doing that can you rule it out.

– joeqwerty
Jan 25 at 16:20










1 Answer
1






active

oldest

votes


















0














If you've ruled out a broken cable, it most likely is the NIC. Either the hardware is bad (anything from bent pins in the 8P8C jack to chip failure) or the driver is.



Assuming it's an onboard NIC, deactivate in BIOS and fit a PCIe card.




Changed the "Speed and Duplex" from Auto Negation to "100MBps Full Duplex". I also tried all the other forms. But this one made the loop faster so to speak.




You've just broken autonegotiation. Unless you set both ends' ports to the exact same settings, the other end probably autodetects the link speed but without autoneg it falls back to half duplex, creating a duplex mismatch.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1398349%2fwin-10-pc-ethernet-cable-stuck-in-unplugged-and-identifying-loop%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    If you've ruled out a broken cable, it most likely is the NIC. Either the hardware is bad (anything from bent pins in the 8P8C jack to chip failure) or the driver is.



    Assuming it's an onboard NIC, deactivate in BIOS and fit a PCIe card.




    Changed the "Speed and Duplex" from Auto Negation to "100MBps Full Duplex". I also tried all the other forms. But this one made the loop faster so to speak.




    You've just broken autonegotiation. Unless you set both ends' ports to the exact same settings, the other end probably autodetects the link speed but without autoneg it falls back to half duplex, creating a duplex mismatch.






    share|improve this answer




























      0














      If you've ruled out a broken cable, it most likely is the NIC. Either the hardware is bad (anything from bent pins in the 8P8C jack to chip failure) or the driver is.



      Assuming it's an onboard NIC, deactivate in BIOS and fit a PCIe card.




      Changed the "Speed and Duplex" from Auto Negation to "100MBps Full Duplex". I also tried all the other forms. But this one made the loop faster so to speak.




      You've just broken autonegotiation. Unless you set both ends' ports to the exact same settings, the other end probably autodetects the link speed but without autoneg it falls back to half duplex, creating a duplex mismatch.






      share|improve this answer


























        0












        0








        0







        If you've ruled out a broken cable, it most likely is the NIC. Either the hardware is bad (anything from bent pins in the 8P8C jack to chip failure) or the driver is.



        Assuming it's an onboard NIC, deactivate in BIOS and fit a PCIe card.




        Changed the "Speed and Duplex" from Auto Negation to "100MBps Full Duplex". I also tried all the other forms. But this one made the loop faster so to speak.




        You've just broken autonegotiation. Unless you set both ends' ports to the exact same settings, the other end probably autodetects the link speed but without autoneg it falls back to half duplex, creating a duplex mismatch.






        share|improve this answer













        If you've ruled out a broken cable, it most likely is the NIC. Either the hardware is bad (anything from bent pins in the 8P8C jack to chip failure) or the driver is.



        Assuming it's an onboard NIC, deactivate in BIOS and fit a PCIe card.




        Changed the "Speed and Duplex" from Auto Negation to "100MBps Full Duplex". I also tried all the other forms. But this one made the loop faster so to speak.




        You've just broken autonegotiation. Unless you set both ends' ports to the exact same settings, the other end probably autodetects the link speed but without autoneg it falls back to half duplex, creating a duplex mismatch.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 3 at 20:55









        Zac67Zac67

        69019




        69019






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1398349%2fwin-10-pc-ethernet-cable-stuck-in-unplugged-and-identifying-loop%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Probability when a professor distributes a quiz and homework assignment to a class of n students.

            Aardman Animations

            Are they similar matrix