General discussion

Locked

Windows Time Service error

By peter.berger@genexsrvcs ·
Source: w32time
Error, "The Windows Time Service was not able to find a Domain Controller. A time and date update was not possible."

The weird thing is: This machine "is" the Windows 2000 Domain Controller (PDC emaulator)!? The NTP is set to: "net time /setsntp:time.windows.com" and I can successfully nslookup time.windows.com and get a response.

So is this DC trying to contact itself for a NTP update?

When I try, "w32tm -v -once" I get technical output and it also logs this error into the Event Log, "#49 An unexpected error occured while trying to start the server. The port may already be in use".

Clients seem to be time syncing find with this server, it's just this server trying to update itself is where my problem is.
Any 411/help would be great. Thanks.

This conversation is currently closed to new comments.

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

All Comments

Collapse -

by haileyan In reply to Windows Time Service erro ...

1st Part of your question:
Try another time server for giggles. Here isa list of public time servers you can sync to:
http://support.microsoft.com/default.aspx?scid=kb;en-us;262680&Product=win2000

2nd part of your question:

CAUSE
This problem can occur on a domain controller (DC) when the default port (123) is already in use by the Time service that is running on the DC before the command is executed. The W32tm command tries to start the Time service before execution, but it does work if the service is already started.

RESOLUTION:
To resolve this problem, note that the following command switches for W32tm execute successfully:
-tz
-adj
-adjoff
-s
To successfully use the W32tm command on a DC with the other options, use one or more of the following steps:
1. Stop the Time service to execute the command, and then restart the service.
2. Change the port by using the -p switch to execute the W32tm command on a DC.

Collapse -

by haileyan In reply to

the -v command line is what is causing the error.

Collapse -

by peter.berger@genexsrvcs In reply to

Poster rated this answer.

Collapse -

This question was closed by the author

Back to Windows Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums