internet access problem in 12.04

16,389

Solution 1

This problem has arised for me after using Cisco AnyConnect VPN Client. For some reason the file contained information of the network I was VPN'ing into. I simply removed the file and everything worked for me.

Solution 2

May not work for everyone, but I solved this in 12.04 by going to "Edit Connections"(right click on your internet connection logo) and unticking the "Require IPv4 for this connection to complete" box. Instant result!

Solution 3

This has to do with the switch to resolvconf for /etc/resolv.conf management, as described here.

I solved the problem by inserting dns-nameserver and dns-search options into /etc/network/interfaces. I obtained the values required from /etc/resolvconf/resolv.conf.d/original.

I don't know if this is the "best" or "proper" solution, but it resolved (!) the issue for me. I also don't know why this was necessary.

Share:
16,389
Poorya
Author by

Poorya

Updated on September 18, 2022

Comments

  • Poorya
    Poorya over 1 year

    Yesterday, I have upgraded Ubuntu from 11.10 to 12.04 LTS and everything was ok (there was no error)

    After restart, my "Auto Ethernet" connection established, also my VPN connection established.
    And some pages loaded on firefox
    -- I had a proxy app on my Ubuntu 11.10 (A java app) and after first restart, in 12.04 proxy connection was Ok and I was able to reach any web via firefox with proxy. after switching to chromium with no proxy, there is an error. (also, I have no Internet access any where, in any other application without proxy!)

    So, I found that I can access web pages and services using IP Addresses but DNS not working. Because of my VPN server, I have to set METHOD to Automatic, so I can not use other DNS servers.

    what is wrong with my Ubuntu? how can I fix it?
    Thanks.

    • clicky
      clicky about 12 years
      Experiencing the same problem. DNS look-ups are not working after upgrading from 11.10 to 12.04.
    • jdthood
      jdthood over 11 years
      It isn't really possible to debug this without a lot more information about the affected machine. I suggest you open a bug report against resolvconf (using apport-bug) so that we can approach the problem more systematically.