getting 169 IP in DNS

[Creative Door]

for some reason computer2, thinks its IP is a 169 ip. When i run ipconfig,
it has an ip address of 192.....when i run ping computer2, it pings the 169
ip address. This address also shows up in dns, when i delete this entry in
dns it comes back. (computer2 has dns set up on it)
when i go to computer1, which also has dns set up, it also has the same bad
record for computer2, but it also has a good record for it. The bad record
doesn't give the comptuer name, it just says (same as parent folder). When
i ping computer2 from computer1, it pings the correct IP address. I've
tried flushing dns, yet computer2 still seems to think its ip is the 169.
any ideas on how to fix this?

 

[Herb Martin]

169.254.x.y (x and y can be anything) is the Automatic IP address a DHCP
client uses when NO DHCP server provides it an address.

 

[Creative Door]

Yes, but the computer IS getting a 192 IP address
computer2 has a VALID 192 ip address, and is working just great, but when i
type in ping computer2, it pings the 169 IP address, which doesn't exist.
WHen i run ipconfig it tells me the ip address is 192.... So no computer
actually has the 169 ip address, but it seems to think it does
there are no hosts files configured to point it to a 169 ip either

 

[Ace Fekay [MVP]]

Is this the same post from earlier today/last nite about the 169 in WINS for
the same machine? If so, I replied back suggesting to manually delete this
record from WINS. If not the same poster, I apologize.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Herb Martin]

Yes, but the computer IS getting a 192 IP address

computer2 has a VALID 192 ip address, and is working just great, but when i
type in ping computer2, it pings the 169 IP address, which doesn't exist.
WHen i run ipconfig it tells me the ip address is 192.... So no computer
actually has the 169 ip address, but it seems to think it does
there are no hosts files configured to point it to a 169 ip either

As Ace says, 'check your WINS' if that applies.

Check your DNS server if that applies...?

Check your Hosts file to see if that has any bogus entries.

 

[Michael Johnston [MSFT]]

Try deleting the record from both DNS servers at the same time. It could be that the replication between the two servers is causing the record to come back.
Deleting it from both places will typically solve that problem.

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.