I found that this has been happening a great deal on the
net in general these last few weeks. Sometimes it's almost
instantaneous and other times it's very very slow. At
times like this you can use tracert to determine if there
is a bottle neck in your route.Simple go>start\run and
type in cmd and then in the command line window type in:
tracert
www.microsoft.com or any other URL that you want
to trace the route to. Be sure to leave a space after
tracert . You will see the hop time in ms (miliseconds-1
milisecond=1 thousands of a sec.) and the larger the
number the longer it took to clear that server. Remember,
most URL's are never a direct route and must go through
many hops to get to the specified location. Tracing, and
make note of, where the slowdown occurs, will help you to
identify route problems. If it is a constant slow down, at
the same hop, then you can contact your IP and see if they
could help or at least check to see if this is a known
problem with that server.TTFN