website found waiting for reply

[acebaxter]

So New Year's eve my computer works fine. New Years day and it's very wierd! (no, it wasn't drinking, at least to my knowledge)

I can go to about half the sites I want with no problem. The other half just sit there saying "website found waiting for reply" until it times out. For instance I can get to pprune, but not yahoo. I can get to ALPA but not climbto350, and so on and so on. The only other clue I have is that I can google anything, but if I click on a link it times out. If I click on "cached page" it will load just fine.

I've been playing with this the entire day. Both wireless and cat 5 hookup, no difference. Windows firewall is off. Turned Mcafee off and it made no difference. Tried the windows repair stuff. It finds no problems and still no luck. Re-loaded winsock. Deleted Skype as suggested on a few pages. Reset IE7 back to factory defaults. Checked the auto configure box and never dial a phone box. Basically I've tried everything this dumb pilot can figure to do.:ugh:

Any experts out there?

[frostbite]

Try an alternative browser such as Firefox or Opera seems the obvious answer to me.

[Gertrude the Wombat]

Yeah, I had that today, seems to be back to normal now.

Not using NTL as your ISP by any chance?

(This is clearly a problem with the ISP, not your PC. Anyone telling you that the problem is with IE is simply an anti-Microsoft religious nutter with nothing helpful to contribute.)

[acebaxter]

I tried to get to the Mozilla site but all I saw was "website found waiting for reply" so that's out.

I am using RipWave, also known as Irish Broadband. I thought I'd give them a call tomorrow, I doubt they would be open today.

[Keef]

OK, I'm the anti-Microsoft religious nutter, but it sounds to me like your problem is with your ISP. Typically this happens when they have a glitch with their DNS setup, or they configure a new server and it takes a while to sort itself out.

Try this link: http://69.63.133.132/

if that takes you to climbto350 and http://www.climbto350.com doesn't, that diagnosis is correct.

[Mac the Knife]

A number of key cables were damaged in the recent China Sea earthquake. The internet can re-route around the breaks, but the rest of the net comes under pressure.

"An earthquake registering 7.1 on the Richter scale hit the Southern portion of Taiwan, crippling Internet and phone service in Asia. Approximately 18 telecommunications cables are undersea serving the Pacific Rim region, according to Verizon, and the company said it could take weeks to repair them all.

Cable & Wireless, a UK-based company which also has communications cables in the region, said it lost connections between Japan, Hong Kong and Singapore. Traffic to Japan and Singapore was rerouted through Australia, while China handled data and voice for Japan and Hong Kong.

Verizon said it is using the SEA-ME-WE-4 cable to redirect traffic to India and that customers may be impacted for weeks.

"This underscores the need for additional redundancy in the area," spokesperson Gil Broyles said. Verizon said several cables were damaged, resulting in slower Internet service traffic is rerouted.

Damage to individual undersea cables creates considerably more service disruption than land-based cable because they carry proportionally more traffic and handle multiple regions, said Verizon. This is in contrast to land-based pipes that use multiple paths and suffer more localized disruptions. Verizon said it will take more than a week to get a repair ship into the area. "

So unless it was caused by Gates' flatulence, MS isn't to blame :}

[acebaxter]

That didn't work for climbto350. Same result.

I didn't know about the earthquake. You must have access to the internet. I'm more than a bit jealous over that!

I'm starting to think it could be the "year 2007" bug that we all worried about 7 years ago. Better late than never.

[Keef]

If http://69.63.133.132/ didn't work, then your ISP or the routing thereafter is damaged. I'll go with Mac's diagnosis.

It's certainly not IE on your machine.

Try http://213.161.73.143/forums/forumdisplay.php?f=46 and see if that works, and brings you near here. If it does, that's conclusive (in my book, anyway).

[acebaxter]

http://69.63.133.132/ times out.
http://213.161.73.143/forums/forumdisplay.php?f=46 ] works just fine.

Go figure. I better stick to driving airplanes.

[acebaxter]

Like magic it started working today! Thanks for all your input.