Ethernet won't connect (18.04.2)





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















I left my computer running for an hour or two, idle, and when I logged back in, the ethernet connection was stuck on "connecting." I should probably mention that I installed some tools with Katoolin, which may have messed with my network settings. What steps should I take, beyond router reset, unplugging/replugging the cable, and restarting network-manager? Thanks!










share|improve this question

























  • Have you checked to ensure the connection isn't still there? Sometimes the UI gets confused and says connecting when it's established. Run ifconfig -a to check and see if the Ethernet interface has an IP address. Also, what version of Ubuntu are you on?

    – Minty
    Feb 19 at 2:24











  • I'm on 18.04.2. Will edit the post accordingly.

    – Sean Zheng
    Feb 19 at 22:02











  • Ifconfig spits out a value for inet6 but no recognizable ipv4 address.

    – Sean Zheng
    Feb 19 at 22:10


















0















I left my computer running for an hour or two, idle, and when I logged back in, the ethernet connection was stuck on "connecting." I should probably mention that I installed some tools with Katoolin, which may have messed with my network settings. What steps should I take, beyond router reset, unplugging/replugging the cable, and restarting network-manager? Thanks!










share|improve this question

























  • Have you checked to ensure the connection isn't still there? Sometimes the UI gets confused and says connecting when it's established. Run ifconfig -a to check and see if the Ethernet interface has an IP address. Also, what version of Ubuntu are you on?

    – Minty
    Feb 19 at 2:24











  • I'm on 18.04.2. Will edit the post accordingly.

    – Sean Zheng
    Feb 19 at 22:02











  • Ifconfig spits out a value for inet6 but no recognizable ipv4 address.

    – Sean Zheng
    Feb 19 at 22:10














0












0








0








I left my computer running for an hour or two, idle, and when I logged back in, the ethernet connection was stuck on "connecting." I should probably mention that I installed some tools with Katoolin, which may have messed with my network settings. What steps should I take, beyond router reset, unplugging/replugging the cable, and restarting network-manager? Thanks!










share|improve this question
















I left my computer running for an hour or two, idle, and when I logged back in, the ethernet connection was stuck on "connecting." I should probably mention that I installed some tools with Katoolin, which may have messed with my network settings. What steps should I take, beyond router reset, unplugging/replugging the cable, and restarting network-manager? Thanks!







networking ethernet






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 19 at 22:04







Sean Zheng

















asked Feb 19 at 1:47









Sean ZhengSean Zheng

154




154













  • Have you checked to ensure the connection isn't still there? Sometimes the UI gets confused and says connecting when it's established. Run ifconfig -a to check and see if the Ethernet interface has an IP address. Also, what version of Ubuntu are you on?

    – Minty
    Feb 19 at 2:24











  • I'm on 18.04.2. Will edit the post accordingly.

    – Sean Zheng
    Feb 19 at 22:02











  • Ifconfig spits out a value for inet6 but no recognizable ipv4 address.

    – Sean Zheng
    Feb 19 at 22:10



















  • Have you checked to ensure the connection isn't still there? Sometimes the UI gets confused and says connecting when it's established. Run ifconfig -a to check and see if the Ethernet interface has an IP address. Also, what version of Ubuntu are you on?

    – Minty
    Feb 19 at 2:24











  • I'm on 18.04.2. Will edit the post accordingly.

    – Sean Zheng
    Feb 19 at 22:02











  • Ifconfig spits out a value for inet6 but no recognizable ipv4 address.

    – Sean Zheng
    Feb 19 at 22:10

















Have you checked to ensure the connection isn't still there? Sometimes the UI gets confused and says connecting when it's established. Run ifconfig -a to check and see if the Ethernet interface has an IP address. Also, what version of Ubuntu are you on?

– Minty
Feb 19 at 2:24





Have you checked to ensure the connection isn't still there? Sometimes the UI gets confused and says connecting when it's established. Run ifconfig -a to check and see if the Ethernet interface has an IP address. Also, what version of Ubuntu are you on?

– Minty
Feb 19 at 2:24













I'm on 18.04.2. Will edit the post accordingly.

– Sean Zheng
Feb 19 at 22:02





I'm on 18.04.2. Will edit the post accordingly.

– Sean Zheng
Feb 19 at 22:02













Ifconfig spits out a value for inet6 but no recognizable ipv4 address.

– Sean Zheng
Feb 19 at 22:10





Ifconfig spits out a value for inet6 but no recognizable ipv4 address.

– Sean Zheng
Feb 19 at 22:10










1 Answer
1






active

oldest

votes


















1














Apparently, the system wasn't loading the network driver, so the interface wasn't detected. sudo modprobe r8169 appears to have fixed it.






share|improve this answer
























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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%2faskubuntu.com%2fquestions%2f1119381%2fethernet-wont-connect-18-04-2%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









    1














    Apparently, the system wasn't loading the network driver, so the interface wasn't detected. sudo modprobe r8169 appears to have fixed it.






    share|improve this answer




























      1














      Apparently, the system wasn't loading the network driver, so the interface wasn't detected. sudo modprobe r8169 appears to have fixed it.






      share|improve this answer


























        1












        1








        1







        Apparently, the system wasn't loading the network driver, so the interface wasn't detected. sudo modprobe r8169 appears to have fixed it.






        share|improve this answer













        Apparently, the system wasn't loading the network driver, so the interface wasn't detected. sudo modprobe r8169 appears to have fixed it.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 14 at 22:27









        Sean ZhengSean Zheng

        154




        154






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • 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%2faskubuntu.com%2fquestions%2f1119381%2fethernet-wont-connect-18-04-2%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

            Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

            ComboBox Display Member on multiple fields

            Is it possible to collect Nectar points via Trainline?