Hi All,
Let me give an overview of our forest:
We are on a Windows 2000 mixed mode forest.
We have 2 Dc's in my parent domain and a standalone ntp server not on our domain but within our network segment which goes out to get time from Microsoft time server.
On PDC emulator we set this sntp server as our NTP server and it is well reflected on the registry and on our group policy there is a bat file which will get executed as NET TIME /SETSNTP=DC2 on all clients PC and that part works since I am getting the desired result. However, there is an error on the system log of PDC emulator with Event ID:11 which states that "The NTP server didn't respond".
I am not worried about whether this NTP server is working or not but I would like to get the NET TIME command to resolve it to DC2.
When I execute NET TIME from PDC emulator(DC2), I am getting the time of DC1 (not DC2) and the NET TIME /QUERYSNTP gives the ntp server name. The same happens if I execute from clients also except the sntp server is DC2 which is due to the bat file execution. I am little confused because I am not sure what precedes the other and also why am I getting DC1 when NET TIME command is executed.
I would like to resolve this issue by having all the clients, child DC's, member servers, standalone servers resolving to DC2 for time synchronisation. Is this scenario normal that when you execute NET TIME and NET TIME /QUERYSNTP giving you different results?
I tried ReliableTimeSource set to 1 on DC2 and restarted the Windows time service and still all the clients getting time from DC1. Also, I verified on DC1's registry if there ia any entry set for ReliableTimeSource and there is none. What am I missing here?
Any help more than welcome!!!
THANKS.
Shabu.
Software/Hardware used:
ASKED:
December 5, 2005 4:57 PM
UPDATED:
December 9, 2005 4:18 PM
Can you check your time server setting in DHCP
You may find this article useful:
Mark Minasi’s Windows Networking Tech Page
Issue #52 November 2005
http://www.minasi.com/thismonth.htm
Regards
Yes, that was informative.
Thanks.