10 replies
If you'd just like to stop the errors you can do the following:
At a command prompt enter
C:\>net time /setsntp:time-b.nist.gov
then
C:\>net stop w32time
then
C:\>net start w32time
see http://www.boulder.nist.gov/timefreq/service/time-servers.html for a list of public time servers.
(SNTP) uses UDP port 123, so you need to ensure that proxy servers or firewalls don?t block this port.
To synchronize all client computers use a batch file that runs when they log on to the network. It is saved in WINNT\System32\Repl\Import\Scripts of your DC as logon.bat and has just two lines:
Echo Off
net time \\servername /set /yes
where "servername" is the name of your Win2K machine. For their systems to update their time at logon you need to add this file name to their user profile. Go to User Manager on the PDC, select a user, select Properties, click on the Profile button, type in logon.bat in the Logon Script Name box. Next time they log on their computer time is updated.
by sleyba
Poster rated this answer.
by sleyba
by timwalsh
Susan,
When disabling services, problems usually arise because other services have a dependency on the disabled service in order to operate correctly. No other sevices depend on the w32time service.
You are correct that Kerberos uses a time stamp as part of the authentication process. However, Win2K only uses Kerberos when authenticating to an AD domain. NT4 doesn't use Kerberos for authentication.
I have only had to connect Win2K computers to NT4 domains on a couple of occasions and have not experienced any ill effects by disabling the Windows Time service.
by sleyba
Poster rated this answer.
by sleyba
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending