Net Time Command- Another servers name!

Hello!
When I type "net time" on any of my servers, they ALL say:
The current time on Server01 is (actual time).
They all reference Server01, and not themselves with the basic "net time" command.

They all reference the same server, which is part of the domain, and an AD server, but is not the NTP server that is master for the domain. This would be the PDC emulator.

All servers know the reliable time source, and can be confirmed by typing: NET TIME /QUERYSNTP

Why are they referencing:
1. the same server
2. a server that is not themselves
3. the server that is not the PDC emulator?

Hope you can help!
Best- Rick

rickgiguereAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

sstone55423Commented:
the PDC Emulator in the forest root domain  is considered the stratum 2 time source for the forest by default.  This is by design.  Because Kerberos needs time to be accurate, you want all systems in your forest to have time within 20 seconds of each other.  You point out that they are getting time from another DC though.
Other DC's in the forest and PDC Emulators in child domains use W32Time to poll the PDC Emulator in the forest root domain to keep their clocks  synchronized.  Workstations and member servers then poll domain controllers in their domains to synchronize their own clocks.
 
 
0
ChiefITCommented:
GPOs also overwride the time service flag announcements for net time.
0
rickgiguereAuthor Commented:
These are great and accurate answers.
The PDC Emulator for the domain is called "Server03" (fictitious)
There are 3 DC's, and one of these 3 are across a VPN/WAN connection.
They all participate in the same domain, with no child domains.

When I type "NET TIME" on ANY of the servers, they all answer back with:
"The current time on SERVER 01 is XX:XX:XX" They all reference SERVER 01 instead of referencing their own time.
The server they are referencing is just a regular DC server, not anything special such PDC Emulator, RID, or Infrastructure Master.
Why are they all referencing this particular server, and not showing their own time when issueing the command "NET TIME" with out any additional parameters?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

sstone55423Commented:
Well, here is the MS article on the topic.  http://support.microsoft.com/kb/816042
I was thinking, if all of the PC's are showing the same source, we should check for GPO's that set it that way.  Or, if there is no PDC Emulator, it may roll to that DC (Server01) for some reason.  (Why not any of the other DC's?)
 Can you use regedit and go to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w32time key and export to a file -- on one of the other DC's, the server01 DC, and a workstation, and we can see how the registry settings are set.  (Either manually, by default, or by policy) to see what they are configured to do.
0
ChiefITCommented:
SStone55423 has a really good point. I am still sticking with my first hunch.

I think you may have a GPO that is telling your computers where to go for time and that is overriding the announcement flags. You could check RSOP to see if you have a policy that points your clients/servers to server01.

Truth is, Either of our answers could be right.
0
oBdACommented:
"net time" is NT4 based and deprecated. You can still use it to set a time server on the PDC emulator, but that's about all it's good for in an AD domain.
"net time" will query the NetBIOS browser list for *any* DC; it knows exactly *nothing* about the time sync in an AD domain, and even less about AD sites. In other words: the output of "net time" means absolutely nothing.
In addition, "net time /setsntp:..." will do nothing useful on any domain member (except the PDC emulator), either; all domain member use the AD time sync hierarchy (DC sync with the PDC emulator, members with the authenticating DC) *by* *default* and will ignore a manually configured time server.
To find out which DC your machine is currently(!) syncing with, stop and restart the w32time service, then check the event log a bit later; there should be an event stating that the time sync was successful, and which server the machine synced with.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rickgiguereAuthor Commented:
Thank you for all of your help!
The answer from oBdA was exactly the information I could not find anywhere. Many thanks once again!
Rick
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.