SOLVED. Booting from a live CD shows the same symptoms. Running apt-get update returned: [connecting to archive.ubuntu.com (1.0.0.0)] [connecting to security.ubuntu and stalls.
Google knows lots about this, often suggesting the issue is actually with buggy dns code being returned by a router. (Jaunty was just fine with the situation, and there have been no changes to routers, this is at least in some way a Karmic issue) I have: lan (192.168.1.0) --> wrt54gl (192.168.1.1, dhcp server starting at .100, wan ip 10.1.1.3) --> dsl-502t (10.1.1.1, dhcp giving out .3 to wrt54gl) --> internet. Looking at DNS on each, the wrt was looking at the d-link for DNS first, then out to the TCL nameservers, the d-link also looking to TCL. The solution was to stop the wrt from resolving via the d-link and immediately Karmic can browse the internet and thunderbird can access email servers. Cheers, Roger > Hi, following an upgrade to Karmic last night, I have no name resolution > to the > interweb. LAN functions are fine, samba shares good, can ping other > machines, > router, gateway, and can ping paradise/TCL name servers and can ping > www.google.com by name so have a degree of name resolution. I can see > which of > my skype contacts are online. However all browsing in firefox returns > "connection has timed out" and thunderbird can't locate paradise pop or > google > imap servers. > > I still have the same resolv.conf file from before the upgrade: > #Generated by NetworkManager > nameserver 10.1.1.1 > nameserver 203.97.78.43 > nameserver 203.97.78.44 > > The network connection applet near the clock shows "Auto eth0" as active > and > lists the same name servers as per resolv.conf, and the static ip > address for > that machine. ifconfig also shows eth0 with that same ip address though > I'm not > sure where it is getting that from, certainly not via > /etc/network/interfaces > and the control module for network connections doesn't actually list any > wired > connections. Changing the network management backend to wicd doesn't > seem to > help (and doesn't show a network applet with status etc either). > > I'd be very appreciative of any pointers on how to resolve this? > > Cheers, > Roger > > >
