This is really messed up, XP problem, can't get to Internet..

**Shinobi** · 02-02-06, 10:35 PM

Well.. this one has got ol' Shinobi stumped pretty bad.

Can not connect out to internet on Windows XP home..

Checked the following.
No known viruses or spyware. Checked with 3 anti virus program (two online)
Can boot into Linux on the same computer and get out to internet that way, so it isn't both nic cards / cable / router.
Can get a i.p.address from router via DHCP.
Can bounce off of Proxy Server, on my LAN, then go out to the internet that way for internet browsing..
Can not ping or tracert from command line, (unable to resolve ECT.. )
There is not an internal firewall running, xp or 3rd party.
Tried the ipconfig /flushdns command, and release / renew
Tried a static i.p.
Can connect to Remote desktop to Windows 2003 server.
Any ideas other then backing up and re-installing?
Thanks

Shinobi

**cyberskye** · 02-03-06, 06:39 PM

If you can hit local hosts, but can't resolve public names from the command line something is probably whacky with DNS.

Point your browser to http://216.109.112.135 - it's a yahoo error page - can at least test whether its network or service layer issue

***YeOldeStonecat*** · 02-03-06, 07:01 PM

http://www.snapfiles.com/get/winsockxpfix.html

**cyberskye** · 02-03-06, 07:23 PM

Originally Posted by YeOldeStonecat

http://www.snapfiles.com/get/winsockxpfix.html

I thought that winsock issues went away with W98...

**Pinkhead** · 02-03-06, 07:25 PM

Originally Posted by YeOldeStonecat

http://www.snapfiles.com/get/winsockxpfix.html

Did you have this problem after installing windows xp? Did it start suddenly? If you have just installed windows, you may of not installed internet services.

**Shinobi** · 02-04-06, 12:39 AM

Well, before all of you posted, I decided to do a clean install of XP again.. I had all my files backed-up at any rate, so this was not to0 bad.. I haven't had to re-install this computer for a few years now..

Everything is back to status, norminal. Thank You

I think Yosc was right on the money with the WinSock Fix..
I was thinking that I might have to re-install the TCP/IP protocol..
Here Cyberskye:

Recover from Network Corruption in Windows XP
In Windows networking, corruption of the WinSock installation can cause network connections to fail on computers running Windows XP (and other Windows operating systems). This corruption sometimes occurs when you uninstall software applications that rely on WinSock. These applications include adware / spyware systems, software firewalls, and other Internet-aware programs.
To fix WinSock corruption problems, follow either of the two methods described below.

Fix WinSock2 Corruption - Microsoft
For Windows XP and Windows 2003 Server systems, Microsoft recommends following a specific manual procedure to recover from WinSock network issues caused by corruption. The procedure varies depending on whether you have Windows XP Service Pack 2 (SP2) installed.
With XP SP2, the 'netsh' administrative command-line program can repair WinSock.

For older Windows XP installations without XP SP2 installed, the procedure requires two steps:

modifying the related Windows Registry keys
re-installing the TCP/IP protocol

Thanks for all of the suggestions.. you too PinkHead.

Shinobi

***YeOldeStonecat*** · 02-04-06, 08:50 AM

Originally Posted by cyberskye

I thought that winsock issues went away with W98...

Actually got to be more of a pain in the butt to repair it in XP. No they didn't go away, malware can hose the TCP stack/winsock pretty well. Prior to WinXP, it was easy enough to repair....remove the TCP protocol...reboot...add the TCP protocol...all set (reboot again if Win9X of course). Or back in Win9X, could often "heal" it just fine by installing the DUN 1.4 upgrade.

But in WinXP...you cannot uninstall TCP using the traditional method, since it's supposedly so integrated with the OS. There's the "netsh int ip reset" command line method....I used to use that until these utilities such as I linked above came out. There are quite a few different utilities...but that specific one there has worked great for me....I've used it probably over a 100 times, and greater than 50% of the time, if I have no internet connectivity/problems pulling an IP from DHCP/name resolution issues, etc...when I'm working on a malware infested machine....this tool works. It does a more complete job than the manual command line "netsh" method...seems to do a few more things.

It's a permant tool on my USB thumb drive back of tricks that I carry with me.

**Shinobi** · 02-04-06, 09:38 PM

Originally Posted by YeOldeStonecat

Actually got to be more of a pain in the butt to repair it in XP. No they didn't go away, malware can hose the TCP stack/winsock pretty well. Prior to WinXP, it was easy enough to repair....remove the TCP protocol...reboot...add the TCP protocol...all set (reboot again if Win9X of course). Or back in Win9X, could often "heal" it just fine by installing the DUN 1.4 upgrade.

But in WinXP...you cannot uninstall TCP using the traditional method, since it's supposedly so integrated with the OS. There's the "netsh int ip reset" command line method....I used to use that until these utilities such as I linked above came out. There are quite a few different utilities...but that specific one there has worked great for me....I've used it probably over a 100 times, and greater than 50% of the time, if I have no internet connectivity/problems pulling an IP from DHCP/name resolution issues, etc...when I'm working on a malware infested machine....this tool works. It does a more complete job than the manual command line "netsh" method...seems to do a few more things.

It's a permant tool on my USB thumb drive back of tricks that I carry with me.

Good idea about putting it on a usb thumb drive. I'll put that in my happy bag of tricks too

Speaking of 'happy', I remember back in Windows 98 days..
that Happy99.EXE virus that would screw up the Winsock...