Discussion Locked

WINS registration for DHCP clients

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have 2 subnets connect vs T1. Each subnet has its own DHCP server also acting as WINS and DNS server.

Each DHCP server is configure with only one scope that assign WINS and DNS server in the same subnet.

for some reason, some clients at subnetA would get their IP address for local DHCP server but register their name in remote WINS server at subnetB. and some clients don't

why is this happening? and how to make sure clients register WINS using local WINS server?

Appreciate the help!

2 replies

by beermonster

Hi,
I'm going to make one or two assumptions about your setup here. Frankly, if your site A machines have no knowledge of the wins server at site B then there is no way that they would register at it. So, possible scenarios are - you actually give out BOTH wins servers via the scope as primary and secondary addresses, with the local as primary (or maybe someone has added that config directly onto the tcpip properties of the problem machines). In that case, if for any reason the first serverwas unavailable the second would be used to register at. Perhaps you have wins replication between the wins servers (otherwise how would a machine in site A resolve to a machine in site B if it needed to). In this case, the site A client may be failing to register with the local wins server at all and what you are seeing on the site B wins is an older replicated record. Hope one of these ideas helps....

by shanghai sam

I believe your problem is a misunderstanding about the way in which WINS works. WINS is meant to resolve NetBIOS names to IP addresses for an entire network; it cannot be configured to only provide name resolution for a single subnet. In other words, a WINS server in subnet A will resolve names for nodes located in subnet B. What is needed is for you to set up your two WINS servers as a primary and secondary in a push-pull configuration. Then configure each of your DHCP servers to assign the IP address of both WINS servers to their respective clients.

Be aware that improperly configured WINS servers can cause network nightmares.

For a great Microsoft article with links, go to
support.microsoft.com
and search for article Q185786

This discussion is closed to new replies.