I have a W2K DC called SVGLOBAL with an IP_ADDR of 130.nnn.nnn.123. When I
look in WINS for this server it is reported has a different ip-addr
(169.254.209.151). If I ping the server via the name I get a response from
the correct address 130.
Any ideas? There isn't anything stupid like reserved names or such??

Does the server have another network card that is set for DHCP with no DHCP
server available? 169.254.x.x is Microsoft's APIPA automatic addressing.
It's not likely it registered itself on a WINS server if that was the only
IP address it had and the WINS server was on the 130.x.x.x subnet. Best
guess is that SVGLOBAL has 2 IP addresses. What does ipconfig /all say?

....kurt

"Trying Hard" <TryingHard@discussions.microsoft.com> wrote in message
news:FA969478-F8B1-474E-807E-308340F1DC93@microsoft.com...
>I have a W2K DC called SVGLOBAL with an IP_ADDR of 130.nnn.nnn.123. When I
> look in WINS for this server it is reported has a different ip-addr
> (169.254.209.151). If I ping the server via the name I get a response from
> the correct address 130.
> Any ideas? There isn't anything stupid like reserved names or such??

Yes there are two network cards. The second is setup for DHCP but not
physically connected. I will disable that card and see if it makes any change.

Thanks

"Kurt" wrote:

> Does the server have another network card that is set for DHCP with no DHCP
> server available? 169.254.x.x is Microsoft's APIPA automatic addressing.
> It's not likely it registered itself on a WINS server if that was the only
> IP address it had and the WINS server was on the 130.x.x.x subnet. Best
> guess is that SVGLOBAL has 2 IP addresses. What does ipconfig /all say?
>
> ....kurt
>
> "Trying Hard" <TryingHard@discussions.microsoft.com> wrote in message
> news:FA969478-F8B1-474E-807E-308340F1DC93@microsoft.com...
> >I have a W2K DC called SVGLOBAL with an IP_ADDR of 130.nnn.nnn.123. When I
> > look in WINS for this server it is reported has a different ip-addr
> > (169.254.209.151). If I ping the server via the name I get a response from
> > the correct address 130.
> > Any ideas? There isn't anything stupid like reserved names or such??
>
>
>

169.254 is self assigned if it is attempting to get a dhcp address and one
can't be assigned.
From a command prompt do an ipconfig /all and see what is reported. If you
have two nic cards installed (Sounds like you do) disable one, you only want
a single nic for a dc.

The ip address you are entering is a reverse lookup, so look at the reverse
domain when you are looking for address assignments. Also if you do disable
the second nic, do an ipconfig /flushdns from a command prompt to make sure
you don't keep any stale info on your machine.

--
Paul Bergson
MCT, MCSE, MCSA, Security+, BS CSi
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Trying Hard" <TryingHard@discussions.microsoft.com> wrote in message
news:FA969478-F8B1-474E-807E-308340F1DC93@microsoft.com...
>I have a W2K DC called SVGLOBAL with an IP_ADDR of 130.nnn.nnn.123. When I
> look in WINS for this server it is reported has a different ip-addr
> (169.254.209.151). If I ping the server via the name I get a response from
> the correct address 130.
> Any ideas? There isn't anything stupid like reserved names or such??

Thank you both for your response. This did help to resolver this problem. I
don't really understand why a NIC that is not connected should cause the
problem. However, disabling the NIC and flushing the cache fixed it all.

Thank again.

"Paul Bergson" wrote:

> 169.254 is self assigned if it is attempting to get a dhcp address and one
> can't be assigned.
> From a command prompt do an ipconfig /all and see what is reported. If you
> have two nic cards installed (Sounds like you do) disable one, you only want
> a single nic for a dc.
>
> The ip address you are entering is a reverse lookup, so look at the reverse
> domain when you are looking for address assignments. Also if you do disable
> the second nic, do an ipconfig /flushdns from a command prompt to make sure
> you don't keep any stale info on your machine.
>
> --
> Paul Bergson
> MCT, MCSE, MCSA, Security+, BS CSi
> 2003, 2000 (Early Achiever), NT
>
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Trying Hard" <TryingHard@discussions.microsoft.com> wrote in message
> news:FA969478-F8B1-474E-807E-308340F1DC93@microsoft.com...
> >I have a W2K DC called SVGLOBAL with an IP_ADDR of 130.nnn.nnn.123. When I
> > look in WINS for this server it is reported has a different ip-addr
> > (169.254.209.151). If I ping the server via the name I get a response from
> > the correct address 130.
> > Any ideas? There isn't anything stupid like reserved names or such??
>
>
>