General discussion

Locked

WINS switched round

By RDG ·
We are a regional office running a DHCP server (NT4 , SP4) locally, but obtaining our WINS from servers in two other offices. In total there are three domains (including ours) all with working trust relationships in place.

** We've tested the trusts repeatedly and everything is fine - we access our e-mail, internet and server based applications from servers on the other two domains without problem.

We have configured our DHCP server to assign each client site A as our Primary WINS and site B as the Secondary. All clients and servers with static IP addresses are also configured this way.

The problem is that our Windows 2000 and WinXP DHCP clients keep showing that site B is the Primary WINS and A is the secondary when we test theirTCP/IP settings.

We've checked and rechecked the settings, deleted and re added the DHCP settings with no success. There are even times when a client will show the correct WINS configuration one day, but the next it is back to showing them incorrectly again.

We've wiped the cache on clients, restarted clients and server, released and renewed the IP settings without success.

Whilst the switched around WINS settings do not appear to be causing issues at present, I would like to know why it is happening and how to get the clients to show the correct settings?

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

WINS switched round

by d.walker5 In reply to WINS switched round

On your client machines do an ipconfig /all, if the node type is broadcast, try configuring the 046 Node type option to the DHCP server. Set the node to H-node. This may solve your problem.

Collapse -

WINS switched round

by RDG In reply to WINS switched round

Poster rated this answer

Collapse -

WINS switched round

by curlergirl In reply to WINS switched round

WINS resolution, according to my understanding, will always use the last successful WINS server as the primary, regardless of how you actually have your TCP/IP properties set. Once the client finds a WINS server, whether it be the primary or secondary, it will continue to use that server as the primary until it no longer responds, when it will switch again to the other (now secondary) server. I would say that probably the other machines are actually switching around also, but either (1) olderOS's don't actually display the switched properties; or (2) because your newer machines are faster, they are responding more to the speed of your communication or network traffic between the sites and therefore switching more frequently. Hope this helps!

Collapse -

WINS switched round

by RDG In reply to WINS switched round

Poster rated this answer

Collapse -

WINS switched round

by RDG In reply to WINS switched round

This question was closed by the author

Back to Networks Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums