I don't have that box with me right now, need to check as soon as I get that
box. but I would like to give you little more details perhaps it will help
you.
I updated the system at home, where I have a wireless internet router
(modem+wireless router). when the system was updated my resolv.conf file was
renamed to resolv.conf.old (and this file had all my nameservers in it.).
The new resolv.conf file had only one nameserver 192.168.1.1 which is my
wireless router's ip.

I took the same laptop to my office and tried to connect and you already
know couldn't get the proper network setup. In my office I couldn't get the
nameservers updated in resolv.conf file (which are obviously different from
192.168.1.1). I could very well see the nameserver information in the
network manager gui and all were correct.

So the new bug summary is correct it should be a problem in updating the
information in resolv.conf. It retrived the correct information related to
my network so there seems no problem there.

All the network stuff was working for me earlier so idealy I should have all
the required packages installed. If anything got removed during the update
then I am not sure. I will let you know about the package (resolvconf) as
soon I get the same box.

Regards,
Rajeev

On Sat, Sep 13, 2008 at 7:28 AM, Alexander Sack <[EMAIL PROTECTED]> wrote:

> do you have the resolvconf package installed?
>
> ** Changed in: network-manager (Ubuntu)
>   Importance: Undecided => Medium
>       Status: New => Incomplete
>
> ** Summary changed:
>
> - Not able to connect to network
> + resolv.conf, nameservers not properly updated (Was: Not able to connect
> to network)
>
> --
> resolv.conf, nameservers not properly updated (Was: Not able to connect to
> network)
> https://bugs.launchpad.net/bugs/269340
> You received this bug notification because you are a direct subscriber
> of the bug.
>

-- 
resolv.conf, nameservers not properly updated (Was: Not able to connect to 
network)
https://bugs.launchpad.net/bugs/269340
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to