General discussion

Locked

XP Home Errors

By Michael34 ·
Hello,

Resently we removed some spyware from a clients computer and now everytime they go to connect to the internet they get APIPA (169.x.x.x). I have checked somethings but when I do a renew and release in Dos it says some error then that it attempted to connect to something that was not a socket. I disabled all the firewalls and anti-virus and still nothing. The client uses Broad Band through a cable modem so I'm stumped. The PC is about 2 years old so everything should be alright. Other than it getting APIPA it works great. Any help on how I can fix this????

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by willcomp In reply to XP Home Errors

You need to repair Windows Socket layers. Easiest way is to download and run WinsockFix.exe. See link below.

http://www.tacktech.com/display.cfm?ttid=257

Dalton

Collapse -

by Info-Safety, LLC In reply to XP Home Errors

Reset your TCP/IP stack with the following command:
netsh int ip reset resetlog.txt

Good luck.

Craig Herberg

Collapse -

by AFIT Mng In reply to XP Home Errors

I alos had this problem and got it fixed with a Win Sock reset.

Collapse -

by Lizzy In reply to XP Home Errors

You can look at the MS KB article for more detailed information regarding the WINSOCK corruption. You can find it here:

http://support.microsoft.com/?kbid=811259

169.x.x.x is a "bad" address assigned by Windows when it cannot connect.

Related Discussions

Related Forums