time server won't cooperate

[JBruyet]

Hey all,

I'm trying to get my new 2k3 DC to be the timeserver on my network and I don't seem to be doing something right. I've tried "configuring" my server (that does hold the PDC role) using both of the following commands (I used the second command because the first one didn't work) from the PDC:

net time /setsntp:us.pool.ntp.org

w32tm /config /manualpeerlist:us.pool.ntp.org /syncfromflags:manual /reliable:yes /update

After running each of the previous commands I get a "The command completed successfully" message, but every time I do NET TIME (still from the 2k3 server that I want to be my new time server) I get a response from my 2k domain controller that used to hold my PDC role. Am I missing something here???

Thanks,

Joe B

 

[itsp1965]

Did you move the PDC emulator FSMO role to the new domain controller? The DC with the PDC emulator role is the one that maintains time services. Sounds like the PDC emulator role wasn't moved or not moved correctly thus the result you are receiving.

 

[JBruyet]

The new server does have the PDC role. I had to seize all FSMO roles because my previous DC died a slow (but not painful, unfortunately) death.

Thanks,

Joe B

 

[PScottC]

The Net Time command is for checking time through RPC/NetBIOS. It will not show you time from an NTP source. Check your event log for w32time events. You should see successful sync events there.

To force a sync immediately use:
w32tm /resync /nowait /rediscover

That will clear your synchronization statistics and force the service to reread the settings from the registry.

Good Luck!

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers