DHCP failure to assign IP address (only 169.254) - how to fix?

[Guest]

I have 2 questions that may or may not be related.

First is that after some messing around trying to connect to a laptop, my
std network connection from my XP Pro desktop to another PC (in this case WIN
98 SE) has stopped working.
I have determined that the problem is the XP Pro machine as:-
- Allowing it to assign an IP address automatically in TCP/IP returns and
address of 169.254.x.x with subnet 255.255.0.0.
- From my reading this signifies a failure in DHCP to assign a real IP
address
- If I assign a static IP address of say 192.168.0.2 then I can search for
the other computer and see it but cannot browse it. (NOT to do with sharing
as it's fully shared....!)
- If I then revert to auto IP address, it will NOT find a 192.168 address
but again the 169.254 address.

I have tried ipconfig/release and renew but still the same. I have also
tried the Winsock fix but still the same.

So.... why is DHCP failling to do its thing properly?... and how can I force
it to play ball?

Second question... XP seems to retain memory of previous network
connections. Since I've over the last few years had a variety of network
configurations, my network adapptor is now listed as "network connection 20".
......how can I clear XP's memory of previous setups... may free up resources
to help with the problem above?

Many thanks.

 

[Robert L [MVP - Networking]]

1. 169.254.x.x: You may want to upgrade driver for the NIC or firmware for the router if you have one.

Troubleshooting ipconfig Why the ipconfig shows 0.0.0.0 ip even you have assigned a static ip Why do I get 169.254.x.x IP? An error occurred while renewing interface ...
www.chicagotech.net/troubleshootingipconfig.htm

2. network connection 20: Can you delete them? Or you may want to disable the XP automatic search.

How to disable the XP automatic search
http://www.howtonetworking.com/disc3_frm.htm



Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
I have 2 questions that may or may not be related.

First is that after some messing around trying to connect to a laptop, my
std network connection from my XP Pro desktop to another PC (in this case WIN
98 SE) has stopped working.
I have determined that the problem is the XP Pro machine as:-
- Allowing it to assign an IP address automatically in TCP/IP returns and
address of 169.254.x.x with subnet 255.255.0.0.
- From my reading this signifies a failure in DHCP to assign a real IP
address
- If I assign a static IP address of say 192.168.0.2 then I can search for
the other computer and see it but cannot browse it. (NOT to do with sharing
as it's fully shared....!)
- If I then revert to auto IP address, it will NOT find a 192.168 address
but again the 169.254 address.

I have tried ipconfig/release and renew but still the same. I have also
tried the Winsock fix but still the same.

So.... why is DHCP failling to do its thing properly?... and how can I force
it to play ball?

Second question... XP seems to retain memory of previous network
connections. Since I've over the last few years had a variety of network
configurations, my network adapptor is now listed as "network connection 20".
.....how can I clear XP's memory of previous setups... may free up resources
to help with the problem above?

Many thanks.