Ubuntu 16.04 LTS, internet connection doesn't work, but network still can access machine












4















Last night the machine was working fine. This morning, no internet access.



I'm working with a wired Ethernet connection.

I can ping the router, but not google.

I am able to access shared files on the machine from another computer through the wired network.



Other machines on the network can access the internet. It's only the Ubuntu box that can't get internet.



I can ping google by address but not by name.



output of lsb_release -a




No LSB modules are available.

Distributor ID: Ubuntu

Description: Ubuntu 16.04.2 LTS

Release: 16.04

Codename: xenial




nmcli dev show | grep DNS partial results:




IP4.DNS[1]: 192.168.0.1




Which is the router address.



`

more /etc/resolve results:



 # Generated by OpenVPN Client UP Script  

nameserver 10.8.0.1


ls -1 /etc/resolv.conf results:




-rw-r--r-- 1 root root 172 Feb 23 22:34 /etc/resolv.conf











share|improve this question





























    4















    Last night the machine was working fine. This morning, no internet access.



    I'm working with a wired Ethernet connection.

    I can ping the router, but not google.

    I am able to access shared files on the machine from another computer through the wired network.



    Other machines on the network can access the internet. It's only the Ubuntu box that can't get internet.



    I can ping google by address but not by name.



    output of lsb_release -a




    No LSB modules are available.

    Distributor ID: Ubuntu

    Description: Ubuntu 16.04.2 LTS

    Release: 16.04

    Codename: xenial




    nmcli dev show | grep DNS partial results:




    IP4.DNS[1]: 192.168.0.1




    Which is the router address.



    `

    more /etc/resolve results:



     # Generated by OpenVPN Client UP Script  

    nameserver 10.8.0.1


    ls -1 /etc/resolv.conf results:




    -rw-r--r-- 1 root root 172 Feb 23 22:34 /etc/resolv.conf











    share|improve this question



























      4












      4








      4








      Last night the machine was working fine. This morning, no internet access.



      I'm working with a wired Ethernet connection.

      I can ping the router, but not google.

      I am able to access shared files on the machine from another computer through the wired network.



      Other machines on the network can access the internet. It's only the Ubuntu box that can't get internet.



      I can ping google by address but not by name.



      output of lsb_release -a




      No LSB modules are available.

      Distributor ID: Ubuntu

      Description: Ubuntu 16.04.2 LTS

      Release: 16.04

      Codename: xenial




      nmcli dev show | grep DNS partial results:




      IP4.DNS[1]: 192.168.0.1




      Which is the router address.



      `

      more /etc/resolve results:



       # Generated by OpenVPN Client UP Script  

      nameserver 10.8.0.1


      ls -1 /etc/resolv.conf results:




      -rw-r--r-- 1 root root 172 Feb 23 22:34 /etc/resolv.conf











      share|improve this question
















      Last night the machine was working fine. This morning, no internet access.



      I'm working with a wired Ethernet connection.

      I can ping the router, but not google.

      I am able to access shared files on the machine from another computer through the wired network.



      Other machines on the network can access the internet. It's only the Ubuntu box that can't get internet.



      I can ping google by address but not by name.



      output of lsb_release -a




      No LSB modules are available.

      Distributor ID: Ubuntu

      Description: Ubuntu 16.04.2 LTS

      Release: 16.04

      Codename: xenial




      nmcli dev show | grep DNS partial results:




      IP4.DNS[1]: 192.168.0.1




      Which is the router address.



      `

      more /etc/resolve results:



       # Generated by OpenVPN Client UP Script  

      nameserver 10.8.0.1


      ls -1 /etc/resolv.conf results:




      -rw-r--r-- 1 root root 172 Feb 23 22:34 /etc/resolv.conf








      networking 16.04 internet






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Feb 18 at 16:06









      Elder Geek

      27.4k955130




      27.4k955130










      asked Feb 22 '17 at 19:18









      D. DieksD. Dieks

      23115




      23115






















          3 Answers
          3






          active

          oldest

          votes


















          3














          It's my understanding that /etc/resolv.conf is for public nameservers only. It appears that yours has been modified to use a private nameserver ostensibly over a VPN. If you wish your Ubuntu box to obtain Domain Name Service normally to allow internet access, I suggest that you revert back to the default /etc/resolv.conf file which contains:



          # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
          # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
          nameserver 127.0.1.1


          You can revert back to the default /etc/resolv.conf file by either restoring the original from a recent backup from before it was modified, or opening the file the link points to with the command sudo gedit /etc/resolv.conf and pasting the code from the default file above into it overwriting it's current content. You may want to save a copy of the current content beforehand as a backup somewhere you will be able to locate it if you find you need it.



          NOTE: /etc/resolv.conf is a symbolic link to the file /run/resolvconf/resolv.conf so file based operations such as editing on /etc/resolv.conf will actually be carried out on /run/resolvconf/resolv.conf



          To confirm that the link hasn't been erroneously modified run the command ls -l /etc/resolv.conf which should result in the output below.



          lrwxrwxrwx 1 root root 29 Feb 25 2016 /etc/resolv.conf -> ../run/resolvconf/resolv.conf


          the arrow indicates it's a symlink.



          For more information on resolvconf which modifies this file see the man page.






          share|improve this answer


























          • That fixed it! Thanks for all your help.

            – D. Dieks
            Feb 24 '17 at 6:35











          • When I try to create the symbolic link using ln -s /run/resolvconf/resolv.conf /etc/resolv.conf, I get: ln: failed to create symbolic link '/etc/resolv.conf': File exists

            – D. Dieks
            Feb 26 '17 at 18:03











          • OK, you've lost me now. Can you give me more detail on what I should be doing? You'll have to remove the file you created after deleting the link to recreate it makes no sense to me.

            – D. Dieks
            Feb 26 '17 at 22:56











          • I didn't delete /etc/resolv.conf. I edited it as per your directions.

            – D. Dieks
            Feb 26 '17 at 23:17






          • 1





            This answer fixed my issue too. In my case the /etc/resolv.conf does not have nameserver 127.0.1.1.

            – inullpointer
            Feb 17 at 16:42





















          2














          If you have an unmodifed /etc/resolv.conf file (and you should) you should change System Settings -> Network -> Options to be set as shown below so that your router will provide DNS services to your Ubuntu box as it does to your other systems.



          DHCP



          An alternative is to use Google public DNS service and add 8.8.8.8 and 8.8.4.4 as your DNS servers.






          share|improve this answer


























          • Switched over to settings as shown above. No change. Still can't get internet access.

            – D. Dieks
            Feb 23 '17 at 21:40











          • Please edit the output of more /etc/resolv.conf into your post Thank you for helping us help you!

            – Elder Geek
            Feb 24 '17 at 0:11



















          0














          I had a similar problem and my resolv.conf file was as shown in Elder Geek's post . I did :

          1. Changed System -> Network -> Options to Automatic(DHCP)

          2. sudo apt-get update

          3. sudo apt-get upgrade

          4. Repeat Setp 2 and 3 multiple times.



          I know this is not a very technical way of answering as it doesn't answer the root cause (or talk about it). But it worked for me. Let's see if it works for you.






          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%2f886252%2fubuntu-16-04-lts-internet-connection-doesnt-work-but-network-still-can-access%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            3 Answers
            3






            active

            oldest

            votes








            3 Answers
            3






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            3














            It's my understanding that /etc/resolv.conf is for public nameservers only. It appears that yours has been modified to use a private nameserver ostensibly over a VPN. If you wish your Ubuntu box to obtain Domain Name Service normally to allow internet access, I suggest that you revert back to the default /etc/resolv.conf file which contains:



            # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
            # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
            nameserver 127.0.1.1


            You can revert back to the default /etc/resolv.conf file by either restoring the original from a recent backup from before it was modified, or opening the file the link points to with the command sudo gedit /etc/resolv.conf and pasting the code from the default file above into it overwriting it's current content. You may want to save a copy of the current content beforehand as a backup somewhere you will be able to locate it if you find you need it.



            NOTE: /etc/resolv.conf is a symbolic link to the file /run/resolvconf/resolv.conf so file based operations such as editing on /etc/resolv.conf will actually be carried out on /run/resolvconf/resolv.conf



            To confirm that the link hasn't been erroneously modified run the command ls -l /etc/resolv.conf which should result in the output below.



            lrwxrwxrwx 1 root root 29 Feb 25 2016 /etc/resolv.conf -> ../run/resolvconf/resolv.conf


            the arrow indicates it's a symlink.



            For more information on resolvconf which modifies this file see the man page.






            share|improve this answer


























            • That fixed it! Thanks for all your help.

              – D. Dieks
              Feb 24 '17 at 6:35











            • When I try to create the symbolic link using ln -s /run/resolvconf/resolv.conf /etc/resolv.conf, I get: ln: failed to create symbolic link '/etc/resolv.conf': File exists

              – D. Dieks
              Feb 26 '17 at 18:03











            • OK, you've lost me now. Can you give me more detail on what I should be doing? You'll have to remove the file you created after deleting the link to recreate it makes no sense to me.

              – D. Dieks
              Feb 26 '17 at 22:56











            • I didn't delete /etc/resolv.conf. I edited it as per your directions.

              – D. Dieks
              Feb 26 '17 at 23:17






            • 1





              This answer fixed my issue too. In my case the /etc/resolv.conf does not have nameserver 127.0.1.1.

              – inullpointer
              Feb 17 at 16:42


















            3














            It's my understanding that /etc/resolv.conf is for public nameservers only. It appears that yours has been modified to use a private nameserver ostensibly over a VPN. If you wish your Ubuntu box to obtain Domain Name Service normally to allow internet access, I suggest that you revert back to the default /etc/resolv.conf file which contains:



            # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
            # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
            nameserver 127.0.1.1


            You can revert back to the default /etc/resolv.conf file by either restoring the original from a recent backup from before it was modified, or opening the file the link points to with the command sudo gedit /etc/resolv.conf and pasting the code from the default file above into it overwriting it's current content. You may want to save a copy of the current content beforehand as a backup somewhere you will be able to locate it if you find you need it.



            NOTE: /etc/resolv.conf is a symbolic link to the file /run/resolvconf/resolv.conf so file based operations such as editing on /etc/resolv.conf will actually be carried out on /run/resolvconf/resolv.conf



            To confirm that the link hasn't been erroneously modified run the command ls -l /etc/resolv.conf which should result in the output below.



            lrwxrwxrwx 1 root root 29 Feb 25 2016 /etc/resolv.conf -> ../run/resolvconf/resolv.conf


            the arrow indicates it's a symlink.



            For more information on resolvconf which modifies this file see the man page.






            share|improve this answer


























            • That fixed it! Thanks for all your help.

              – D. Dieks
              Feb 24 '17 at 6:35











            • When I try to create the symbolic link using ln -s /run/resolvconf/resolv.conf /etc/resolv.conf, I get: ln: failed to create symbolic link '/etc/resolv.conf': File exists

              – D. Dieks
              Feb 26 '17 at 18:03











            • OK, you've lost me now. Can you give me more detail on what I should be doing? You'll have to remove the file you created after deleting the link to recreate it makes no sense to me.

              – D. Dieks
              Feb 26 '17 at 22:56











            • I didn't delete /etc/resolv.conf. I edited it as per your directions.

              – D. Dieks
              Feb 26 '17 at 23:17






            • 1





              This answer fixed my issue too. In my case the /etc/resolv.conf does not have nameserver 127.0.1.1.

              – inullpointer
              Feb 17 at 16:42
















            3












            3








            3







            It's my understanding that /etc/resolv.conf is for public nameservers only. It appears that yours has been modified to use a private nameserver ostensibly over a VPN. If you wish your Ubuntu box to obtain Domain Name Service normally to allow internet access, I suggest that you revert back to the default /etc/resolv.conf file which contains:



            # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
            # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
            nameserver 127.0.1.1


            You can revert back to the default /etc/resolv.conf file by either restoring the original from a recent backup from before it was modified, or opening the file the link points to with the command sudo gedit /etc/resolv.conf and pasting the code from the default file above into it overwriting it's current content. You may want to save a copy of the current content beforehand as a backup somewhere you will be able to locate it if you find you need it.



            NOTE: /etc/resolv.conf is a symbolic link to the file /run/resolvconf/resolv.conf so file based operations such as editing on /etc/resolv.conf will actually be carried out on /run/resolvconf/resolv.conf



            To confirm that the link hasn't been erroneously modified run the command ls -l /etc/resolv.conf which should result in the output below.



            lrwxrwxrwx 1 root root 29 Feb 25 2016 /etc/resolv.conf -> ../run/resolvconf/resolv.conf


            the arrow indicates it's a symlink.



            For more information on resolvconf which modifies this file see the man page.






            share|improve this answer















            It's my understanding that /etc/resolv.conf is for public nameservers only. It appears that yours has been modified to use a private nameserver ostensibly over a VPN. If you wish your Ubuntu box to obtain Domain Name Service normally to allow internet access, I suggest that you revert back to the default /etc/resolv.conf file which contains:



            # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
            # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
            nameserver 127.0.1.1


            You can revert back to the default /etc/resolv.conf file by either restoring the original from a recent backup from before it was modified, or opening the file the link points to with the command sudo gedit /etc/resolv.conf and pasting the code from the default file above into it overwriting it's current content. You may want to save a copy of the current content beforehand as a backup somewhere you will be able to locate it if you find you need it.



            NOTE: /etc/resolv.conf is a symbolic link to the file /run/resolvconf/resolv.conf so file based operations such as editing on /etc/resolv.conf will actually be carried out on /run/resolvconf/resolv.conf



            To confirm that the link hasn't been erroneously modified run the command ls -l /etc/resolv.conf which should result in the output below.



            lrwxrwxrwx 1 root root 29 Feb 25 2016 /etc/resolv.conf -> ../run/resolvconf/resolv.conf


            the arrow indicates it's a symlink.



            For more information on resolvconf which modifies this file see the man page.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Feb 17 at 17:45

























            answered Feb 24 '17 at 1:22









            Elder GeekElder Geek

            27.4k955130




            27.4k955130













            • That fixed it! Thanks for all your help.

              – D. Dieks
              Feb 24 '17 at 6:35











            • When I try to create the symbolic link using ln -s /run/resolvconf/resolv.conf /etc/resolv.conf, I get: ln: failed to create symbolic link '/etc/resolv.conf': File exists

              – D. Dieks
              Feb 26 '17 at 18:03











            • OK, you've lost me now. Can you give me more detail on what I should be doing? You'll have to remove the file you created after deleting the link to recreate it makes no sense to me.

              – D. Dieks
              Feb 26 '17 at 22:56











            • I didn't delete /etc/resolv.conf. I edited it as per your directions.

              – D. Dieks
              Feb 26 '17 at 23:17






            • 1





              This answer fixed my issue too. In my case the /etc/resolv.conf does not have nameserver 127.0.1.1.

              – inullpointer
              Feb 17 at 16:42





















            • That fixed it! Thanks for all your help.

              – D. Dieks
              Feb 24 '17 at 6:35











            • When I try to create the symbolic link using ln -s /run/resolvconf/resolv.conf /etc/resolv.conf, I get: ln: failed to create symbolic link '/etc/resolv.conf': File exists

              – D. Dieks
              Feb 26 '17 at 18:03











            • OK, you've lost me now. Can you give me more detail on what I should be doing? You'll have to remove the file you created after deleting the link to recreate it makes no sense to me.

              – D. Dieks
              Feb 26 '17 at 22:56











            • I didn't delete /etc/resolv.conf. I edited it as per your directions.

              – D. Dieks
              Feb 26 '17 at 23:17






            • 1





              This answer fixed my issue too. In my case the /etc/resolv.conf does not have nameserver 127.0.1.1.

              – inullpointer
              Feb 17 at 16:42



















            That fixed it! Thanks for all your help.

            – D. Dieks
            Feb 24 '17 at 6:35





            That fixed it! Thanks for all your help.

            – D. Dieks
            Feb 24 '17 at 6:35













            When I try to create the symbolic link using ln -s /run/resolvconf/resolv.conf /etc/resolv.conf, I get: ln: failed to create symbolic link '/etc/resolv.conf': File exists

            – D. Dieks
            Feb 26 '17 at 18:03





            When I try to create the symbolic link using ln -s /run/resolvconf/resolv.conf /etc/resolv.conf, I get: ln: failed to create symbolic link '/etc/resolv.conf': File exists

            – D. Dieks
            Feb 26 '17 at 18:03













            OK, you've lost me now. Can you give me more detail on what I should be doing? You'll have to remove the file you created after deleting the link to recreate it makes no sense to me.

            – D. Dieks
            Feb 26 '17 at 22:56





            OK, you've lost me now. Can you give me more detail on what I should be doing? You'll have to remove the file you created after deleting the link to recreate it makes no sense to me.

            – D. Dieks
            Feb 26 '17 at 22:56













            I didn't delete /etc/resolv.conf. I edited it as per your directions.

            – D. Dieks
            Feb 26 '17 at 23:17





            I didn't delete /etc/resolv.conf. I edited it as per your directions.

            – D. Dieks
            Feb 26 '17 at 23:17




            1




            1





            This answer fixed my issue too. In my case the /etc/resolv.conf does not have nameserver 127.0.1.1.

            – inullpointer
            Feb 17 at 16:42







            This answer fixed my issue too. In my case the /etc/resolv.conf does not have nameserver 127.0.1.1.

            – inullpointer
            Feb 17 at 16:42















            2














            If you have an unmodifed /etc/resolv.conf file (and you should) you should change System Settings -> Network -> Options to be set as shown below so that your router will provide DNS services to your Ubuntu box as it does to your other systems.



            DHCP



            An alternative is to use Google public DNS service and add 8.8.8.8 and 8.8.4.4 as your DNS servers.






            share|improve this answer


























            • Switched over to settings as shown above. No change. Still can't get internet access.

              – D. Dieks
              Feb 23 '17 at 21:40











            • Please edit the output of more /etc/resolv.conf into your post Thank you for helping us help you!

              – Elder Geek
              Feb 24 '17 at 0:11
















            2














            If you have an unmodifed /etc/resolv.conf file (and you should) you should change System Settings -> Network -> Options to be set as shown below so that your router will provide DNS services to your Ubuntu box as it does to your other systems.



            DHCP



            An alternative is to use Google public DNS service and add 8.8.8.8 and 8.8.4.4 as your DNS servers.






            share|improve this answer


























            • Switched over to settings as shown above. No change. Still can't get internet access.

              – D. Dieks
              Feb 23 '17 at 21:40











            • Please edit the output of more /etc/resolv.conf into your post Thank you for helping us help you!

              – Elder Geek
              Feb 24 '17 at 0:11














            2












            2








            2







            If you have an unmodifed /etc/resolv.conf file (and you should) you should change System Settings -> Network -> Options to be set as shown below so that your router will provide DNS services to your Ubuntu box as it does to your other systems.



            DHCP



            An alternative is to use Google public DNS service and add 8.8.8.8 and 8.8.4.4 as your DNS servers.






            share|improve this answer















            If you have an unmodifed /etc/resolv.conf file (and you should) you should change System Settings -> Network -> Options to be set as shown below so that your router will provide DNS services to your Ubuntu box as it does to your other systems.



            DHCP



            An alternative is to use Google public DNS service and add 8.8.8.8 and 8.8.4.4 as your DNS servers.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Feb 24 '17 at 1:25

























            answered Feb 23 '17 at 20:54









            Elder GeekElder Geek

            27.4k955130




            27.4k955130













            • Switched over to settings as shown above. No change. Still can't get internet access.

              – D. Dieks
              Feb 23 '17 at 21:40











            • Please edit the output of more /etc/resolv.conf into your post Thank you for helping us help you!

              – Elder Geek
              Feb 24 '17 at 0:11



















            • Switched over to settings as shown above. No change. Still can't get internet access.

              – D. Dieks
              Feb 23 '17 at 21:40











            • Please edit the output of more /etc/resolv.conf into your post Thank you for helping us help you!

              – Elder Geek
              Feb 24 '17 at 0:11

















            Switched over to settings as shown above. No change. Still can't get internet access.

            – D. Dieks
            Feb 23 '17 at 21:40





            Switched over to settings as shown above. No change. Still can't get internet access.

            – D. Dieks
            Feb 23 '17 at 21:40













            Please edit the output of more /etc/resolv.conf into your post Thank you for helping us help you!

            – Elder Geek
            Feb 24 '17 at 0:11





            Please edit the output of more /etc/resolv.conf into your post Thank you for helping us help you!

            – Elder Geek
            Feb 24 '17 at 0:11











            0














            I had a similar problem and my resolv.conf file was as shown in Elder Geek's post . I did :

            1. Changed System -> Network -> Options to Automatic(DHCP)

            2. sudo apt-get update

            3. sudo apt-get upgrade

            4. Repeat Setp 2 and 3 multiple times.



            I know this is not a very technical way of answering as it doesn't answer the root cause (or talk about it). But it worked for me. Let's see if it works for you.






            share|improve this answer




























              0














              I had a similar problem and my resolv.conf file was as shown in Elder Geek's post . I did :

              1. Changed System -> Network -> Options to Automatic(DHCP)

              2. sudo apt-get update

              3. sudo apt-get upgrade

              4. Repeat Setp 2 and 3 multiple times.



              I know this is not a very technical way of answering as it doesn't answer the root cause (or talk about it). But it worked for me. Let's see if it works for you.






              share|improve this answer


























                0












                0








                0







                I had a similar problem and my resolv.conf file was as shown in Elder Geek's post . I did :

                1. Changed System -> Network -> Options to Automatic(DHCP)

                2. sudo apt-get update

                3. sudo apt-get upgrade

                4. Repeat Setp 2 and 3 multiple times.



                I know this is not a very technical way of answering as it doesn't answer the root cause (or talk about it). But it worked for me. Let's see if it works for you.






                share|improve this answer













                I had a similar problem and my resolv.conf file was as shown in Elder Geek's post . I did :

                1. Changed System -> Network -> Options to Automatic(DHCP)

                2. sudo apt-get update

                3. sudo apt-get upgrade

                4. Repeat Setp 2 and 3 multiple times.



                I know this is not a very technical way of answering as it doesn't answer the root cause (or talk about it). But it worked for me. Let's see if it works for you.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 25 '17 at 2:37









                EetSandhuEetSandhu

                4319




                4319






























                    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%2f886252%2fubuntu-16-04-lts-internet-connection-doesnt-work-but-network-still-can-access%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

                    How to make a Squid Proxy server?

                    第一次世界大戦

                    Touch on Surface Book