naqayya
asked on
w32time error in Event Log
I have a Windows 2000 Server. I keep getting the following error in my Event Viewer (System Log):
This Machine is a PDC of the domain at the root of the forest. Configure to sync from External time source using the net command, 'net time /setsntp:<server name>'.
Source: w32time
Event ID: 62
After more errors like this I get the following warning:
Because of repeated network problems, the time service has not been able to find a domain controller to synchronize with for a long time. To reduce network traffic, the time service will wait 960 minutes before trying again. No synchronization will take place during this interval, even if network connectivity is restored. Accumulated time errors may cause certain network operations to fail. To tell the time service that network connectivity has been restored and that it should resynchronize, execute "w32tm /s" from the command line.
Source: w32time
Event ID: 64
Can you tell me what the problem is and how to solve it? Thanks.
This Machine is a PDC of the domain at the root of the forest. Configure to sync from External time source using the net command, 'net time /setsntp:<server name>'.
Source: w32time
Event ID: 62
After more errors like this I get the following warning:
Because of repeated network problems, the time service has not been able to find a domain controller to synchronize with for a long time. To reduce network traffic, the time service will wait 960 minutes before trying again. No synchronization will take place during this interval, even if network connectivity is restored. Accumulated time errors may cause certain network operations to fail. To tell the time service that network connectivity has been restored and that it should resynchronize, execute "w32tm /s" from the command line.
Source: w32time
Event ID: 64
Can you tell me what the problem is and how to solve it? Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
From another post by Tom to a similar problem in another forum.
Registry Entries for the W32Time Service (Q223184) This Q article gives you all the registry entries and what each of them mean. From what I read, your should mark your registry entry that your's is a reliable time source and should not seek an external time source.
Also, I put atomic clock sync on a company's W2K server which keeps all computers in the domain set to the correct time since as domain members they must sync their time with the server. Go to http://www.worldtimeserver.com/ to download the free atomic clock program. I haven't noticed the problem in the event log since I did that.
Registry Entries for the W32Time Service (Q223184) This Q article gives you all the registry entries and what each of them mean. From what I read, your should mark your registry entry that your's is a reliable time source and should not seek an external time source.
Also, I put atomic clock sync on a company's W2K server which keeps all computers in the domain set to the correct time since as domain members they must sync their time with the server. Go to http://www.worldtimeserver.com/ to download the free atomic clock program. I haven't noticed the problem in the event log since I did that.
The reason you are getting this message is that this DC is at the top of your forest - it is the PDC Emulator in the forest root domain. All DCs' in the forest, except the PDC Emulator in the Forest root, take their time from other servers:
1. Member servers and XP or higher clients take their time from the DC that logged them on.
2. DCs take their time from the PDC emulator in their own domain.
3. PDC emulators in chlild domains get time from their parent's PDC Emulator.
4. The PDC emulator in the root of any tree that is not the forest root, takes it time from the forest root's PDC Emulator.
5. The PDC emulator in the forest root takes it's time from something else.
You have options on step 5. Personally, I manually check the time on the server every month or so (or if I see any funnies on time). You could also use the net time command - although we don't since we block the DCs from accessing the internet.
HTH
Thomas
1. Member servers and XP or higher clients take their time from the DC that logged them on.
2. DCs take their time from the PDC emulator in their own domain.
3. PDC emulators in chlild domains get time from their parent's PDC Emulator.
4. The PDC emulator in the root of any tree that is not the forest root, takes it time from the forest root's PDC Emulator.
5. The PDC emulator in the forest root takes it's time from something else.
You have options on step 5. Personally, I manually check the time on the server every month or so (or if I see any funnies on time). You could also use the net time command - although we don't since we block the DCs from accessing the internet.
HTH
Thomas
The reason you are getting this message is that this DC is at the top of your forest - it is the PDC Emulator in the forest root domain. All DCs' in the forest, except the PDC Emulator in the Forest root, take their time from other servers:
1. Member servers and XP or higher clients take their time from the DC that logged them on.
2. DCs take their time from the PDC emulator in their own domain.
3. PDC emulators in chlild domains get time from their parent's PDC Emulator.
4. The PDC emulator in the root of any tree that is not the forest root, takes it time from the forest root's PDC Emulator.
5. The PDC emulator in the forest root takes it's time from something else.
You have options on step 5. Personally, I manually check the time on the server every month or so (or if I see any funnies on time). You could also use the net time command - although we don't since we block the DCs from accessing the internet.
HTH
Thomas
1. Member servers and XP or higher clients take their time from the DC that logged them on.
2. DCs take their time from the PDC emulator in their own domain.
3. PDC emulators in chlild domains get time from their parent's PDC Emulator.
4. The PDC emulator in the root of any tree that is not the forest root, takes it time from the forest root's PDC Emulator.
5. The PDC emulator in the forest root takes it's time from something else.
You have options on step 5. Personally, I manually check the time on the server every month or so (or if I see any funnies on time). You could also use the net time command - although we don't since we block the DCs from accessing the internet.
HTH
Thomas
ASKER
Thanks everyone and in particular Stoner79.
By the way, Stoner79, is there a way to check and make sure that all workstations in my domain are taking the time from my Server?
Thanks.
By the way, Stoner79, is there a way to check and make sure that all workstations in my domain are taking the time from my Server?
Thanks.
Not sure without going around them and checking.
You could put a command in the login script for users when they log on and that would get the time then.
You could put a command in the login script for users when they log on and that would get the time then.
ASKER
Thanks Stoner79.
net time /SETSNTP:ntp.nasa.gov