I am trying to get a handle on how the Windows time service actually does what it does. From what I can gather by reading Technet posts and hands on experience, the time service is Ok, not the best way to synchronize time but it does work. Here is what I am faced with and why it is a bit confusing.
In my environment, I have a Windows AD domain, the primary DC gets it time from the internet. The subordinate DCs, which are located across various remote offices, get their time from the primary DC. The client PCs get their time from the subordinate DCs. (A fairly straight forward setup)
What has me baffled is this, I set the client PCs to look at the subordinate DC via a registry setting. (HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\NtpServer XXX.XXX.XXX.XXX, 0x1)
Most of the client PCs will return the correct server name when I run the "Net Time" command as well as the correct IP address when I run "Net Time /querysntp" command.
These systems all run Embedded Windows XP
A fair amount of the client PCs will NOT return the correct server host name when I run the "Net Time" command but they all will return the correct IP address when I run the "Net Time /querysntp" command. The ones that do not report the correct server will report another client PCs host name on the same network segment, NOT their own host name.
I can't find a good reason why this issue occurs.
So my question is this, is this normal behavior for this service and if not how should I go about getting all the client PCs to act in a similar manner and return the correct server name as well as the correct IP?
Thank you in advance....