Having an odd internet issue...

[Drunken Irishman]

Maybe someone can help me out.

It seems sites don't load fast at all. I type the URL into the browser bar and hit enter and nothing happens. It just sits there.

Yet once I finally DO get on a website, like DU, it runs smoothly. I have no problem opening threads and reading them and replying to posts. But initially getting to any website seems impossible.

Does anyone know WTF this could mean?

Thanks for your help.

[Orsino]

1. DNS trouble?

If you're using Internet Exploder, the bottom of your blank page might say, "Cannot find server or DNS error." That doesn't actually tell us much, so try traceroutes from your Windoze command prompt...something like: tracert www.yahoo.com

This'll take a minute, but if you get an "unable to resolve target host name" sort of error, that's a clear indication of a DNS failure. If your system can resolve the Yahoo name to an IP address, look at the times on the last hop, which should have a device name including "yahoo.com" (I think). Times of 100 milliseconds and greater could indicate a latency problem along the path you're taking.

[HopeHoops]

2. Generally, that's a traffic jam.

If you use a huge ISP (like Verizon), they're the ones firing things off in all directions to route your traffic and probably not the problem. Don't bitch at a smaller ISP unless you get consistently slow performance on ALL sites. They're dependent on the larger ISP they buy bandwidth from. If it is consistently slow for all sites until you get a connection, then it is most likely your ISP being short on capacity.

Once the "are you out there" packet takes off, you are at the mercy of whatever path it takes. If it ends up going through a routing station in Po-Dunk, SC, it could get jammed up by insufficient bandwidth.

There are sites out there that will give you a visual trace of how your packet traveled to get to its destination. Sometimes it is a "bend over backwards and lick your butt" situation. A packet might take off from NYC, hit FL, bounce out of KY, make a stop in UT, and finally make its way back to MD via GA. It isn't a "what's closest physically" sort of thing.

[Drunken Irishman]

3. I figured it out, guys.

Thanks for trying to help.

It was the CPU Usage. Somehow it was at 100%. I don't know why, but a quick restart fixed it.

Must have not restarted my computer for a while and it got clunked. Or whatever.