Page cannot be displayed

[countymounty]

I keep getting a "Page Can not Be Displayed" message when trying to use the internet. I would say that it happens 95% of the time and all I have to do is hit the refresh button and I will be able to get to the desired page. I thought it was an IE 7 problem but I uninstalled it and get the same problem. It is almost like I am losing network connection but I don't receive any error messages from my network adapter, or my network drives that they are disconnected. Any ideas would be greatly appreciated.

THANKS!

 

[stduc]

How are you connecting to the internet?

If direct - via modem or ADSL modem does your connection have the correct DNS settings? If these are on automatic ask your ISP for the IP address's.

If via a router does the router have the DNS IP address's set? If not - again add them.

If you are accessing via a wireless connection you may have an issue in that area that is causing this behavior?

Try pinging google both as

http://www.google.com

and 66.249.93.104 - the response time should be order 50 ms and no more than 100ms and by name or by number the values should be the same.

If there is an initial reponse delay when using

http://www.google.com

then that indicates a DNS related problem.


--------------------------------------------------------------------------------
When I was single I looked for miss right. When I married her I discovered her first name was always.

 

[countymounty]

I am connecting via a router in business network environment with a T1 line. When running Windows XP Network Diagnostics and Broadcom's Diagnostic programs I get no error messages. When pinging

http://www.google.com

average seek time is 43ms, when pinging 66.249.93.104 the average seek time jumps to 150ms.

Thanks for your help.

 

[stduc]

Now, strangely enough I am occasionally experiencing the same problem today. But only on a few sites and not consistently. I'm wondering if it's a packet loss issue?

I find it very strange that you get a longer reponse time pinging Google by IP address. Here are my results for pinging Google.

ping

http://www.google.co.uk

Pinging

http://www.google.co.uk

[66.249.93.99] with 32 bytes of data:

Reply from 66.249.93.99: bytes=32 time=43ms TTL=240
Reply from 66.249.93.99: bytes=32 time=41ms TTL=240
Reply from 66.249.93.99: bytes=32 time=43ms TTL=240
Reply from 66.249.93.99: bytes=32 time=42ms TTL=240

Ping statistics for 66.249.93.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 43ms, Average = 42ms

ping 66.249.93.104

Pinging 66.249.93.104 with 32 bytes of data:

Reply from 66.249.93.104: bytes=32 time=42ms TTL=240
Reply from 66.249.93.104: bytes=32 time=42ms TTL=240
Reply from 66.249.93.104: bytes=32 time=41ms TTL=240
Reply from 66.249.93.104: bytes=32 time=41ms TTL=240

Ping statistics for 66.249.93.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 42ms, Average = 41ms


Try pinging a problem site with a big packet lots of times - i,e.

ping -l 1400 -n 50 bbc.co.uk

(ping the bbc with a 1400 byte packet 50 times)

Try a few sites and see whether and what sort of packet loss you are getting.

------------------------------------------------------------------------------------------------------------------------
When I was single I looked for miss right. It wasn't until after I married her I discovered her first name was always.

 

[countymounty]

This is the results

Pinging bbc.co.uk [212.58.224.131] with 1400 bytes of data

Negotiating IP Security.
Negotiating IP Security.
Negotiating IP Security.
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=179ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=145ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=142ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=152ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=142ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=142ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=142ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=142ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=142ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=180ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=202ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=219ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=245ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=270ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=232ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=205ms TTL=112
Request timed out.
Reply from 212.58.224.131: bytes=1400 time=178ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=157ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=154ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=149ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112
Reply from 212.58.224.131: bytes=1400 time=143ms TTL=112

Ping statistics for 212.58.224.131:
Packets: Sent = 50, Received = 46, Lost = 4 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 142ms, Maximum = 270ms, Average = 157ms

 

[stduc]

OK - not good. Can I suggest you have a word with your network people? One things for sure - it's not your PC.

Request timed out.

is suspicious and an 8% packet loss is quite poor.

Where about on the planet are you? UK? USA?

These are my results for the BBC

Ping statistics for 212.58.224.131:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 75ms, Maximum = 79ms, Average = 76ms

------------------------------------------------------------------------------------------------------------------------
When I was single I looked for miss right. It wasn't until after I married her I discovered her first name was always.