<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Hi, I guess it could be either: 1) DNS - but you have checked this using dig and firefox doesn't stall as "looking up <a class="moz-txt-link-abbreviated" href="http://www.foo.bar">www.foo.bar</a>". Also you seem to be able to connect using just the IP address. Either way, I would recommend setting your DNS servers to the OpenDNS servers - which are very reliable. They are:  208.67.222.222 and 208.67.220.220 2) IPV6. This can cause problems with some routers.  I have had this problem when using Linksys, ebuyer value and belkin - but not netgear.  If in doubt I would recommend disabling IPV6. <a class="moz-txt-link-freetext" href="http://ubuntuforums.org/archive/index.php/t-87798.html">http://ubuntuforums.org/archive/index.php/t-87798.html</a> Also, you can trying using konqueror browser - which apparently doesn't suffer this problem. Hope that helps, James Dave Briggs wrote: <blockquote cite="midf61b40710612271434m1d3254dehf04b32a72c5343fd@mail.gmail.com" type="cite"> <pre wrap="">On 12/27/06, Pat <a class="moz-txt-link-rfc2396E" href="mailto:evilcorporation@gmail.com"><evilcorporation@gmail.com></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">This guy <a class="moz-txt-link-freetext" href="http://linux.derkeiler.com/Mailing-Lists/Ubuntu/2006-05/msg01681.html">http://linux.derkeiler.com/Mailing-Lists/Ubuntu/2006-05/msg01681.html</a> seems to be having a similar problem, and he mentions a workaround (<a class="moz-txt-link-freetext" href="https://wiki.ubuntu.com/StaticDnsWithDhcp">https://wiki.ubuntu.com/StaticDnsWithDhcp</a>) which appears to involve setting static DNS entries. I'd try the static dns entries if you haven't already. </pre> </blockquote> <pre wrap=""> Tried that - did both of the things suggested at the wiki page just to be on the safe side (was that the wrong thing to do? I know nothing of networking), and still no joy. This was the output I got: dave@dave-desktop:~$ sudo invoke-rc.d networking restart * Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.eth0.pid with pid 5522 killed old client process, removed PID file Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit <a class="moz-txt-link-freetext" href="http://www.isc.org/sw/dhcp/">http://www.isc.org/sw/dhcp/</a> Listening on LPF/eth0/00:13:d3:cd:a6:fa Sending on LPF/eth0/00:13:d3:cd:a6:fa Sending on Socket/fallback DHCPRELEASE on eth0 to 192.168.1.1 port 67 There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416 Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit <a class="moz-txt-link-freetext" href="http://www.isc.org/sw/dhcp/">http://www.isc.org/sw/dhcp/</a> Listening on LPF/eth0/00:13:d3:cd:a6:fa Sending on LPF/eth0/00:13:d3:cd:a6:fa Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 DHCPOFFER from 192.168.1.1 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.1 bound to 192.168.1.2 -- renewal in 1522 seconds. There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416 Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit <a class="moz-txt-link-freetext" href="http://www.isc.org/sw/dhcp/">http://www.isc.org/sw/dhcp/</a> SIOCSIFADDR: No such device eth1: ERROR while getting interface flags: No such device eth1: ERROR while getting interface flags: No such device Bind socket to interface: No such device Failed to bring up eth1. There is already a pid file /var/run/dhclient.eth2.pid with pid 134993416 Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit <a class="moz-txt-link-freetext" href="http://www.isc.org/sw/dhcp/">http://www.isc.org/sw/dhcp/</a> SIOCSIFADDR: No such device eth2: ERROR while getting interface flags: No such device eth2: ERROR while getting interface flags: No such device Bind socket to interface: No such device Failed to bring up eth2. There is already a pid file /var/run/dhclient.ath0.pid with pid 134993416 Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit <a class="moz-txt-link-freetext" href="http://www.isc.org/sw/dhcp/">http://www.isc.org/sw/dhcp/</a> SIOCSIFADDR: No such device ath0: ERROR while getting interface flags: No such device ath0: ERROR while getting interface flags: No such device Bind socket to interface: No such device Failed to bring up ath0. There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416 Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit <a class="moz-txt-link-freetext" href="http://www.isc.org/sw/dhcp/">http://www.isc.org/sw/dhcp/</a> SIOCSIFADDR: No such device wlan0: ERROR while getting interface flags: No such device wlan0: ERROR while getting interface flags: No such device Bind socket to interface: No such device Failed to bring up wlan0. [ ok ] -- Dave Briggs </pre> </blockquote> </body> </html>