HELP - DHCP overwritten by weird IP address

  • Thread starter Thread starter Alan
  • Start date Start date
A

Alan

Over the last few weeks suddenly the NIC card on my desktop PC gets a static
IP address 169.254.164.39 with a subnet mask 255.255.0.0. Doing ipconfig in
the dos window, shows Autoconfig enabled as ON with the IP address shown
above. There is no network connectivity and the system indicates limited or
no network connectivity.

This computer is connected via a physical LAN to the home networking hub.
The network configuration is setup for DHCP and other wireless computers
connect without a problem.

A couple of weeks ago after spending a couple of hours making all sorts of
changes I was able to get this to work normally again with DHCP. Today
however it has reverted to the same static address.

Any suggestions and advice on fixing this is deeply appreciated ? Can I
disable autoconfig through some registry setting ? Could this be some virus
or other malware on my system.

Thanks in Advance,
Alan.
 
USually a 169.254.x.y address shows there is no internet activity and the
computer automatically assigns the address.


You can try a release renew:
Start | Run | cmd | press OK
type ipconfig/release
then ipconfig/renew

You can also try to reset your router
Try a different CAT 5e cable
Check your NIC card

Sometimes after the removal of spyware, it throws off the seetings for the
internet. You can also try to run this winsock fix:
http://www.majorgeeks.com/download4372.html
 
In addition to WoodyCouder's excellent comments, here is Microsoft's
explanation of what is happening:

"If a DHCP server is not reached after approximately 60 seconds or leased
configuration fails, the computer uses the setting on the Alternate
Configuration tab to determine whether to use APIPA for automatic TCP/IP
configuration or to configure TCP/IP with the alternate configuration. When
APIPA is used, Windows XP uses an address in the APIPA IP address range
(169.254.0.1 through 169.254.255.254) and the subnet mask is set to
255.255.0.0. "

You can learn all about Automatic Private Addressing (APIPA) by following
these steps:

Start | Help and Support

In the Search block, type "IP Addressing"

Click on the link, "Configure TCP/IP for automatic addressing"

Steve
 
let me know if this helps: go to the command prompt &
try to ping your address for example mine is 127.0.0.1
so for mine I would type: ping 127.0.0.1
then press enter. or you can type: ipconfig/?
this will give you a summary.

I hope this helps.
 
phillip said:
let me know if this helps: go to the command prompt &
try to ping your address for example mine is 127.0.0.1
so for mine I would type: ping 127.0.0.1
then press enter. or you can type: ipconfig/?
this will give you a summary.

I hope this helps.

No it won't help.

You can ping the localhost IP address (127.0.0.1) without even being on
a netword at all.

The OP has _already_ run ipconfig. Please learn to read. Also please
learn to quote the message you are replying to.

Steve N.
 
I am having exactly the same issue - if the NIC is left to get an IP via DHCP
it fails to get one and assigns that same address - I understand now why
thats happening but it dosn't help! The issue is why won't the vista PC get
aDHCP assigned adress when all the XP pcs can?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top