Yes I am "pinging" the name!
We do not have a LMHOST file on any of the servers (or HOST).
The WINS database seems totally fine as all PC other than BDC's or
PDC's can resolve PING BDC1 to the correct ip address.
I did find an article from Microsoft about setting Primary and
Secondary Wins servers the same on all Wins servers (some bug with the
order in which the WINS service starts)although that fixed some
problems with network neighborhood browsing, it did not fix this one
with the PING results.
The result it does give is registered in our ISP's DNS database but is
not actually operational so I cannot see how it would register with our
> Are you pinging using the name or the IP address?
> If you are pinging using the name check you LMHOSTS file. It may have
> an entry for "BDC1" that is incorrect. Or check your WINS server, it
> may have a wrong entry. Make sure that no other computer has the name
> BDC1. If there is an other computer with that name WINS will only
> register one computer, even though you can ping both IP address only
> the one registered with WINS will give a response if you try to ping
> with the name.
> Matt Meyer
> > Hello,
> > I am trying to fix this strange problem with our NT servers.
> > Just for background, we have two offices connected over an ISDN
> > All external traffic gets routed through our main office. We have a
> > Wins, DHCP and Mail server in each site.
> > When I ping BDC1 from any other server in our domain I get an
> > which looks like it has come from a DNS entry and not our WINS
> > database, ie FQDN with wrong IP address.
> > If I ping BDC1 from a workstation or win9x PC it returns the correct
> > address.
> > If I ping BDC1 from itself it returns the correct address.
> > Has anyone seen this before?
> > AndyR
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Sent via Deja.com http://www.deja.com/
Before you buy.