Limited or No Connection (XP)

Status
Not open for further replies.
Problem Solved

Problem Solved! I used the Microsoft Knowledgebase link and Charles@pcfix's recommendation. I replaced the seemingly defected Winsock registry keys with a similar machine's good keys.

Thanks! :p
 
You could tell by your second picture that the establishment between your host and DHCP server was dead..only cause you got a bogus IP address of 169.254.x.x which is APIPA doing its job...basically rather than throwing all kinds of DCHP server not found errors it labled it with the automated private IP address, which is reserved.

Both methods you went with are good cures to that problem. Also I agree that MACs=The Devil, Appletalk protocol is a bastard! :(
 
Also for future reference to make sure that the NIC wasnt the problem a simple loop back test would have told you. If you PING'd 127.0.0.1 and recieved a request time out error you knew that your card was dead, but if it worked could also be eliminated as a cause of the problem.
 
Status
Not open for further replies.
Back
Top Bottom