[Bug 46822] Re: Network interface ureliable in Dapper release-candidate

[Christian Convey]

I came home and tried thi on my home computer.  Similar scenario: an x86
computer running Breezy and using DHCP.  When I upgraded to the Dapper
release candidate (the one announced 25 May 2006), the network didn't
work.

The network card is (according to Windows' hardware manager): "CNet
PRO200WL PCI Fast Ethernet Adapter."

If I recall correctly, I was able to acquire an IP# from DHCP, but I was
unable to bring up any website.  The webbrower (or ping, etc.) seemed to
block indefinitely on the DNS request when I accessed a site by name.  I
didn't try accessing any remote host by IP# rather than DNS name, so I
can't be certain that the problem is anything but a DNS problem.

Also, I did ifdown + ifup after I realized I had the problem.  When I
did this, I was unable to acquire a DHCP lease.  So acquiring the lease
was apparently more successful during the boot process than when I did
it manually.  (I know it worked during the boot process because my
computer had the expected IP address.)

Note that when I rebooted the computer into Windows, all of my
networking functionality was just fine.  So the DNS problem almost
certainly wasn't a server-side issue.

In this case, my network card is

-- 
Network interface ureliable in Dapper release-candidate
https://launchpad.net/bugs/46822