Discussion Locked

can't release ip 169. in XP

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have an desktop Windows XP Professional that autoconfigures it's IP to 169.
The DHCP is working fine (tried two, DHCP in linksys and cable modem) with other PC's.
I can set the XP PC to a static IP (same as the router would grant) but no communication. I can ping the rounter and the DHCP sees the mac addresses of the PC.
Unless static IP is specified the autoconfig will be granted. DHCP, auto DNS and WINS are enabled.
I've tried netsh reset to reset the TCP stack and another to clear the ARP cache and they seemed to worked but had no effect on the problem.
I will be reinstalling XP in a few days if I get no further help.

9 replies

by sdschafer

The IP address is probably something like 169.254.X.X and it means that the NIC is not receiving information, wheather it be a bad NIC, bad cable, bad port on switch.

by marty

The PC has two NIC's, one wireless, the other built-in. Both have the same problem. The cable and ports work fine with other computers.
I should have included more details. I've already read everyone's easy answers from this type of problem. I've also tried to release and renew but both get a message saying the port is not a socket.

by cg it

yep as answer one said, the 169.XXX. is a default assigned IP address [when automatic discovery is selected] and no DHCP server [services] can be contacted. Bad NIC,Cable, disconnected cable are some of the causes. Replace the NIC with a known working NIC and see if the problems goes away. If not try replacing the cable with a known good one.

by marty

see comments to answer 1. I should have mentioned I've tried all the easy solutions. These types of answers are plastered all over google searches. Thanks anyway.

by quintar51

have you tried using 'ipconfig /release' and 'ipconfig /renew'?

What message shows up when you try to renew the address?

- Try connecting the cable to a different port in the router (if possible)
- Try using a different cable
- Try using a different network card

by marty

with release and renew I get "the port is not a socket" or other similar things. The only way I can get it to NOT autoconfig the IP to 169. is by assigning an IP. Of course it doesn't use DHCP then.
I've also tried to different DHCP servers (one in the rounter and one at the cable company). Same results. It always autoconfigs.
Tried different cable,
different NIC,
different port,
different DHCP's. Also the cable, NIC, port and DHCP work fine on other PC's. This Windows XP Pro is screwed up.
Ipconfig reset and clearing the arp cache did not produce error messages (they appeared to work) but did not effect the problem at all. Thanks for your suggestions. Sorry I forgot to mention I'd already tried them.

by marty

Thanks for your answer, but that topic or page no longer exists. I also tried searching for that file on the microsoft site and found nothing either. I'll just reinstall.

This discussion is closed to new replies.