Discussion Locked

Win2k & NT 4.0 WINS Interoperability

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

I am wanting to move my WINS service to Win2k and away from NT. Currently my primary and secondary WINS servers are running on NT... I have my root AD server as well as a Win2k member server running WINS as well. I set up replication between the 4 servers, but receive an Event ID 4243 when the NT servers try to send a push notification to the Win2k servers. It looks like the two types of WINS servers aren't liking each other... just curious if anyone has had any luck running WINS in this fashion.

TIA,

7 replies

by keval

Never tried to move WINS away from NT. 2000 family was designed to use DNS as a naming service rather than WINS. Check to see if you have all patches relating to legacy support in 2000???

by bobby gillette

WINS is alive and well in Win2k (you still need it if you want to use SMS for example). DNS interoperability is fine, no problems whatsoever.

by a.grogan

Hi,

I run a similar configuration - but instead of the Winnt 4.0 Partners "pushing" - I have the Windows 2000 WINS server "Pull" and this works fine.

by saihib

To fix this problem:

1. Disable the Replicate On Address Change check box in WINS Manager / Configuration.

AND / OR

2. Increase the DHCP lease renewal interval in
DHCP Manager / network address of scope / Scope / Properties / Lease Duration / Limited To.

This discussion is closed to new replies.