When I start my computer with an ethernet cable plugged-in, I have no problem getting an IP Address. However, if I drop the connection and re-connect; or if I wait until after I've started the machine to plug in the ethernet cable an IP address reverts to 169.254... (I suppose because it fails to reach the DHCP). Since it works fine at start-up; I am inclined to believe that some other application is "blocking" the DHCP; but I don't know how to have just the minimum processes start so I can add one at a time until I find out what's blocking it. Or am I missing it altogether? scott

i can only help with 'how to perform a clean boot' =( check here

How is your network setup? Is this a cable modem, dsl modem? Need more info on the network. Also, why are you disconnecting? Why are you unplugging the Cat5 from the NIC? KTTD

When you boot your os looks for a connection, it has a NIC but can't find a DHCP server because it's unplugged, so it assigns the 169.254.xx.xx IP to the adapter. If you want to connect that way you can go to your command prompt and run ipconfig /release then ipconfig /renew to initiate getting an IP from the DHCP server. It would just be easier to leave your network card plugged in.

hello if you drop connection and cant bring it back up with out rebooting it might be fire wall related. disable xp,s when this happens and see if it connects. and if you have a commercial 3rd part-ty fire wall check to see if its blocking it from connecting if so set it to allow to access the internet. if you cant figure out how to set your 3rd party fire wall just temporarily disable it dose internet connect?