TCP/IP problem, maybe winsock, can't connect to cable internet

[bankboysb]

This machine is unable to connect to the cable internet system because of what appears to be some missing files that control the TCP/IP stack. Symantec A/V generates an error (when it tries to update) saying tcp/ip is not installed. The NIC configuration appears to be normal, with tcp/ip enabled. I don't see any reason for concern over the NIC's config. Every time I use IPCONFIG to check, the NIC has reverted to 169.254.x.x (windows internal ip)

I had a cable system tech tell me it was a winsock problem. He had me delete the winsock and winsock2 registry entries. He said they would rebuild, but it didn't work completely. The winsock2 values came back but not winsock. I have tried copying a working registry subsection into the failed machine with no luck.

Could be I haven't rebuilt the stack correctly? What is the correct method for rebuilding tcp/ip?

Tried doing a repair install of XP but that didn't work. Don't want to re-install this machine from scratch due to many applications already in place.

The cable modem goes to a router. The pc is connected to router. Other machines can connect to internet via the router, but not this one.

Any ideas out there?

 

[linney]

You can try here.

http://windowsxp.mvps.org/winsock.htm

 

[edfair]

How about ripping out all the network stuff and let the machine reinstall it?

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[bcastner]

This could be as easily malware on your system, as some issue with the native Winsock or TCP/IP services. Please see this FAQ to test/clean possible issues: faq608-4650

Persistent issues with connecting to the Internet, but being unable to resolve any address, is the consequence of one or both of these issues:

. A Winsock Service stack corruption - frequently due to malware, or poorly written installation programs for legitimate programs; and/or,

. TCP/IP Service issues.

Start with Repairing your Winsock Service:

. if NOT using Service Pack 2, see faq779-4625 and use the "WinsockFix" utility discussed there;

. if you are using Service Pack 2 for XP:

Start, Run, CMD

netsh winsock reset catalog

(Wait for the prompt telling you a reboot is necessary. Reboot).


If a Winsock Service repair did not help, Repair the TCP/IP Service:

1. Right-click the network connection, and then click Properties.
2. Click Install.
3. Click Protocol, and then click Add.
4. Click Have Disk.
5. Type C:\Windows\inf, and then click OK.
6. On the list of available protocols, click Internet Protocol (TCP/IP), and then click OK.
7. Restart the computer.

 

[bankboysb]

Thanks, you guys, esp. linney for the links. I'll have to try a coupla things and get back with ya!

 

[bankboysb]

Hello! I have tried all the above solutions. bcastner's solution (from Microsoft) did not work. The Winsock2 got rebuilt but not Winsock.

On the other hand the link that Linney provided yielded two pieces of freeware that did solve the problem and restored IP connectivity. Hooray!

However, once reconnected it became evident that the reason for this failure was the application of Service Pack 2 when there was abundant spyware still running. The *NASTY* toolbar that was downloaded sprung back to life and tried to take over the communications once again. The decision was made to surgically remove the problem by reformatting/reinstalling XP.

Thanks for the assistance!