PDA

View Full Version : "Network Timeout" at the PC-Guide

Sylvander
10-27-2008, 08:36 AM
This is happening to me a number of times every day. :(

OK with other websites.

Anyone else experiencing this?
sassie05
10-27-2008, 08:43 AM
No, not here.
Fred_Flintstone
10-27-2008, 08:53 AM
Ok from Somerset!...:cool:
jlreich
10-27-2008, 11:49 AM
No problems here either. Try running a tracert, you probably have a bad hop somewhere along the line.
FrankSG
10-27-2008, 12:00 PM
No problems here in Ohio...
Sylvander
10-27-2008, 12:01 PM
"Try running a tracert"
How is that done?
And what is it? [In simple terms :) ]

Quickly speed-read most of the following, including...
By the 1990s many Internet sites were blocking traceroute requests. (http://en.wikipedia.org/wiki/Traceroute)
mjc
10-27-2008, 12:39 PM
Simple...

Trace the route between two IP addresses.

Continue to the end of that paragraph...

Usually, however, traceroute will function up to the borders of blocked sites, revealing the path to a given site, but in many cases not the network within that site.

Yes, some of the power/functionality of the command has been restricted. But, traceroute works well enough to trace the path between your machine and the desired endpoint (in this case PC Guide), but won't provide any internal details of the Pair network hosting the site.

Type this in at a command prompt...

tracert www.pcguide.com

or

tracert 209.68.14.80
Sylvander
10-27-2008, 02:13 PM
Well, that seemed to work OK, when all's well trying to connect. :)

Should I do it again when I cannot access the PC-Guide?
mjc
10-27-2008, 03:06 PM
Yeah...do it then.
jlreich
10-27-2008, 04:00 PM
If you have a high latency hop or one that times out you will know where you are getting hung up at. Not that there is really anything you can do about it unfortunately. :p Unless you find your router (should be your first hop) is having problems.
Sylvander
10-27-2008, 05:33 PM
What's a "high latency hop"?

A "hop" that takes a long time to connect?
What qualifies as a long time?

See screenshot of timings:
.
jlreich
10-27-2008, 06:55 PM
I would say anything over 60ms is high, under 30 is good. You have several near or over 100ms. Looks like there are some line problems somewhere along your route.

Here is mine for comparison.

http://i37.tinypic.com/2i9qiwl.jpg
Sylvander
10-28-2008, 04:23 AM
Hnn...
Times are good at Edinburgh [Edin]...
London = ldn?

Times begin to increase at New York = nyk?

Then:
.
Sylvander
10-28-2008, 05:27 AM
OK, got "Network Timeout" at 7.33 a.m. and just now able to get through once again at 8.25 a.m.

Here are screenshots taken at 7.33

Can these kind of millisecond delays really prevent me from getting through?
.
jlreich
10-28-2008, 09:49 AM
Can these kind of millisecond delays really prevent me from getting through?
.
No they shouldn't prevent you from getting through. But they do indicate a slowdown along the way here. Keep in mind that tracert doesn't require near the same amount of data you are requesting when you want to get to a web page, so perhaps the slowdowns become timeouts when requesting the actual web page.
Sylvander
10-28-2008, 10:38 AM
"perhaps the slowdowns become timeouts when requesting the actual web page"
Is this caused by congestion at those nodes on the web?
And if so, why aren't they just rerouted around the congested nodes?
[I thought the web was specifically designed to achieve this kind of thing]
Because ALL the alternative routes are even worse?

By-the-way, this only began happening just recently.