In a situation like this, it helps to narrow down the problem as much as possible. I suspect that the problem that you are having is with name resolution.
But it always helps to check the simple things first. I would suggest that you try to ping an external IP address to ensure that you are not having connectivity issues. Such as 129.33.51.123 (which is an address that host a Genereal Motors website that responds to pings.
Assuming that this works then we can move onto name resultion. One way to test this would be to see if you can resolve names. By going to the command line and attempt to ping a major site by its name, i.e.
ping cnn.com
If name resolution is working, the following line should make refrence both the name and its resolved IP address, such as:
PING cnn.com (64.236.16.116): 56 data bytes
You can repeat this with a handful of sites and the response should be similar. If you are getting what appears to be valid IP address back, then name resolution is likely not the problem.
If we get to this point without a likely lead, then we may be dealing a config issue with your browser. Let us know how these test work out and we can attempt to drill down more from here.
Good Luck,
|