http dead!

for the last week or so, i cannot connect to the web via dialup. well, it "connects" okay, but then just hangs there. when i run a diagnostic, it tells me "http" is dead (or unavailable or sumpin ladat), but "ftp" is fine.

it's not a browser issue -- i've tried them all, plus unrelated apps which rely on URLs (like direct loading one into getright). it simply can't see the web, no way, no how. turning off my AV or my firewall doesn't help.

worse yet, out of 20+ attempts i try per day, once or twice it gets as far as flashing me my homepage or something, and i can surf for a minute or two! nothing worse than a problem which occurs MOST of the time but not quite all.

it hasn't seemed to be happening when i connected via wifi, but since beginning this post, it's happening bigtime! if you eventually see this, rest assured it took me hours and hours to get it to "take". (EDIT: actually, it just took a reboot. but this rarely works for the dialup probs)

meanwhile, uTorrent, cute, and various AV/AM "update" routines are working just fine. but try as i may, i CANNOT get the web!!!!! (much).

what gives?!

 

What kind of a diagnostic are you doing that tells you that HTTP is not working, but FTP is?

Check to see if you can ping any computers on the internet. To do this, click on Start->Run and type in CMD. Once the black command prompt comes up, type "ping www.google.com" (without the quotations around it) and let us know what it says there.

And as a final question, how are you connecting to the internet? What type of modem are you using?

 

Some default diagnostic which popped up. "Troubleshoot this connection" - sumpin ladat.

It gave me a nice little readout, which I glaced at and saved offline. Unfortunately, I cannot READ the file (dunno why -- XML), or I'd post the entire thing. I am quite certain it said FTP ok HTTP nogo, but I am not entirely sure I caught the error code on the latter. "12027" I wanna say, but....

Windows help didn't have it, and since i coudn't GET ONLINE to look it up, I promptly forgot it.

Anyway...long and short of it is, I went thru every damn setting on this machine for the past day or two, until finally trying "system restore" today, and -- PRESTO MAGICO! -- I'm baaaaaaaaaaaaaaaaaaaaack. (knock on silicon)

Whew. That was a long 24 hours. Gotta admit, I was contemplating full-on Windows reinstall if that "restore" didn't work.

Now, before it happens again, I'd like to understand what happened. I assume it's something among those "HTTP SSL" settings, but I had everything pretty much as recommended. Plus clicking on various "restore defaults" (including a couple third-party ones like BlackAdder) didn't fix things.

I should also mention that I was fiddling with VPN last weekend (other thread), so it's my first guess as to what's messing with my HTTP. Not certain, tho, since it's not entirely chronological (Thurs VPN, Fri surfing fine, Sat more VPN, Sun surfing fine, Mon++ surfing kaput).

Still, can't think of anything *ELSE* I've done lately which could POSSIBLY have caused this. Sunday and Monday I was doing pretty much same ole same ole. No new apps or anything.

 

PS: ping seems ok, but this is now after having fixed things. so, sorry, i guess we'll never know!

:-o

 

oh-oh. i may not be out of the woods yet.

last night it happened for like 3 hours again. on dialup back home.

i was just getting ready to do ANOTHER system restore, but today it's connectting no problem, so no need just yet. but i'm back at the office (wifi), so i dunno if that's a factor. past experience is that it is NOT -- i.e., that i'm just as likely to get on back home now.

still, why i couldn't LAST night is the issue. any theories?

i cannot live in constant fear of http-interruptus!