Windows Forum

Ask something
Discussion Locked

W32time on a NT 4.0 PDC

0 helpful
1 reply

by smccall

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
in our domain,we have a NT 4.0 PDC. We are currently migrating our servers to Windows 2000. Everthng in the network seems to be working but we are receiving messages in the event logs on the 2000 servers concerening "time services" We have followed the directions in article 258059 that we found on Microsoft's site but this did not seem to help? Can some one direct me to a fix to this problem?

1 reply

by joseph moore

You can ignore the w32time errors on your servers. Here is the deal.
Once you have all Win2K servers (including upgrading your current NT4 PDC to being the Win2K AD Domain Controller), all client machines (workstations and member servers) must have their system clocks within 15 mintues of each other. Active Directory (technically the Kerberos key exchanging authentication) requires clients to be very similar on the time for the keys to be accepted. If you have a member server that is 2 hours off from the DC, then this server will not log in.
But, since you are currently running an NT4 PDC, then you do not have this problem. YOur servers will log in just fine.

ONce you upgrade the NT4 PDC to Win2K, you should then set up this whole time mess.
Personally, I set the w32time service on my Win2k servers ( I also still have an NT4 PDC) to Manual, so the service does not start!!!

Once you are upgraded, read Technet article 216734:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;216734
(please remove any spaces)

hope this helps

This discussion is closed to new replies.