Weird PC Web Browsing Issue

[edtsui]

Ok this one has stumped me for a few hours now and I'm pretty much at a loss as to what to do. The problem is that this PC cannot view any websites at all. I'm not sure how or what is seemingly blocking port 80 requests. It's a WinXP Pro machine. I always get a DNS error/page not responding error whenever I try to load any site whatsoever

Here are some of the things I've tried:

1) Neither IE or Firefox can pull a site up
2) Pings and nslookups show that addresses are being resolved just fine
3) Local Intranet sites don't come up
4) Firewall apps/services on the machine have been disabled
**5) If I F8 on startup and boot into Safe Mode with Networking Support, everything works fine
6) I tried bypassing our own DNS servers with a free proxy server off a free proxy site and that works albeit slowly. It wasn't a port 80 proxy server however.
7) FTP, Telnet, VPN, etc, etc client software all works
8) http requests to localhost fail as well
9) I've dug through the startup apps and services and even disabled all of them via msconfig and still doesn't work
10) I did do a Virus/Spyware scan on this thing, but its clean as a whistle.


I'm completely at a loss here because this is the only machine on the network doing this. I might've missed a step somewhere, but I'm pretty close to just formatting this machine.

 

[SSSnail]

Checked teh hosts file?

 

[edtsui]

I was under the impression that the hosts file is still in effect in Safe Mode with Networking Support, but I double checked just to be sure and there are no abnormal entries.

 

[spidey07]

sounds like your TCP/IP stack is hosed. If you search microsoft for "repair tcp/ip stack" there are instructions on how to repair it.

 

[jlazzaro]

are you successful with port 443 (https)?

repair your stack, go to start > run >

netsh int ip reset C:\resetlog.txt

also try the LSP Fix

 

[SSSnail]

If his TCP/IP stack is hosed, he wouldn't be able to run any related commands in CMD. Is the node on DHCP or custom?

 

[jlazzaro]

Originally posted by: SSSnail
If his TCP/IP stack is hosed, he wouldn't be able to run any related commands in CMD. Is the node on DHCP or custom?

in theory yes, but it's worth a 2 second run command just to simply to eliminate it as potential issue.

 

[edtsui]

Mmkay, taking it one step at a time. It's not dhcp. We have to manually plug in IPs for testing here so all settings are user input. I'll try the various things suggested. Thanks for the help so far.

 

[spidey07]

Originally posted by: SSSnail
If his TCP/IP stack is hosed, he wouldn't be able to run any related commands in CMD. Is the node on DHCP or custom?

A big indicator of a stack problem is ping, nslookup, other things work, but certain applications don't.

 

[edtsui]

Update: 443 (https) sites do work. I was able to pull up paypal with no problems. It really seems to be isolated to 80 requests.

 

[edtsui]

I neglected this step earlier, but apparently I cannot ping the faulty machine from another machine either.

 

[jlazzaro]

i know you said all firewalls were disabled, but double check. any applications that may have a stateful firewall feature such a vpn client? the cisco client runs as a service...even if your not on vpn it will still affect your connection.

 

[edtsui]

cisco vpn client was uninstalled to see if it was a cause of the issue.

 

[edtsui]

last bump before formatting =/