Thanks ASBO & HP
I'm doubtful about my abilities with LINUX so I'll have to give that some thought, but I'll have a go with SpeedyFox for sure.
I can't remember when this problem first started up, but I'm on Firefox 11 now, so it might have been some time around the time
that I was on FF9.
As an afterthought, the problem occurs not only after boot up, but also do it after the Laptop has been on sleep or hibernate.
Thanks folks
Please try and give one of those Linux Live CDs a go.. They are very easy to use, and they have all the usual diagnostic tools that are missing from Windows
It sounds as if there's an "IP addressing issue"
since the connectivity fault is present on a cold boot of the laptop, or when emerging from hibernate, that probably pins it down a bit.
The most important connectivity tests can be done with Windows..
Internet name resolution (DNS) can be tested with the 'ping' tool from the Windows shell. Simply ping a site by its host name:
C:\> ping www.google.com
If
www.google.com is resolved to a dot-quad notation IP address.. (e.g. 173.194.66.147), then internet name resolution is working okay, as illustrated below.
We can see that
www.google.com resolved to 173.194.66.147... so DNS works okay on this machine..
C:\> ping www.google.com
PING www.l.google.com (173.194.66.147) 56(84) bytes of data.
64 bytes from we-in-f147.1e100.net (173.194.66.147): icmp_req=1 ttl=46 time=44.7 ms
64 bytes from we-in-f147.1e100.net (173.194.66.147): icmp_req=2 ttl=46 time=54.4 ms
64 bytes from we-in-f147.1e100.net (173.194.66.147): icmp_req=3 ttl=46 time=52.9 ms
^C
If the above test fails, then try pinging a remote computer by its IP address, rather than by its host name. That bypasses the DNS system..
$ ping 173.194.66.147
PING 173.194.66.147 (173.194.66.147) 56(84) bytes of data.
64 bytes from 173.194.66.147: icmp_req=1 ttl=46 time=45.6 ms
64 bytes from 173.194.66.147: icmp_req=2 ttl=46 time=44.7 ms
^C
And if that fails, then it's probably a routing problem..
When you turn on the laptop, it presumably gets its local IP address from the internet router (using the DHCP protocol). It could be a problem in that operation.
The 'ipconfig' tool will show whether IP address allocation (DHCP) is working properly.
cheers, a