Time synchronization problem - server 2003

[pendal1]

Guys, I had a problem with a few windows 2000 pcs when I was joining them to the domain. I was getting an error "this server's clock is not synchronized with the primary domain controller's clock." This didn't happen to me on any xp machines but it happened on two 2000 machines. I did synch the DC (net time /setsntp:ip address) with the root and the problem cleared on one of the machines but it did not clear on the second machine. I also tried synching the time on the workstations with the domain controller in the building but no change. Any ideas would be greatly appreciated. Additionally, we have mutliple domain controllers. I'm still a newbe so is there an easy way to determine what the root of our forest is. I think I know but I want to be sure because then I'll know where the GC is as well. Thank you very much.

 

[58sniper]

Time sync is handled by the DC that holds the PDC emulator role (by default, the first DC in the domain). Machines sync automatically with that DC. You should not manually set time sync on any other DC or workstation manually, or through a login script.

If the time sync is off by more than 5 minutes, you're going to run into problems. How far off is the 2000 machine?

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP

 

[pendal1]

58sniper - that was the strange part. The 2000 machines seemed to be in line time wise - at least within a minute and yet was getting this error. I guess my question is what do I do to resolve this problem if a pc or domain controller are not in line with the time of the PDC. Additionally, and I appreciate your help and anyones help, how can I confirm which DC is the PDC or root. Thank you very much.

 

[Cstorms]

You will need to check if the time service is functinoing.. If you cannot you will need to reregister the w32time.dll.

Verify by..
net stop w32tm

if not..
regsrv32 that dll

net start w32tm

w32tm /resync

I think thats it off the top of my head, but this is indeed in general the process you will need to follow. The resync will send a request to the PDC role holder for an update and should fix it lickity split... If you need more help please post.

Cory

 

[pendal1]

Cory or anyone, I'll definitely try to register or resynch the time with the pdc on the affected DC when I hit that building again tomorrow.
My other question is how can I verify what DC in the forest is the pdc or root.
Also when i force replication, where can I go to confirm replication has actually taken place. Thank you very much.

 

[schtek]

1. net time /querysntp (then go to that server)

2. GPO's on that server check it is acting as the time server or the server that pumps out GPO's check it is pointing to the correct server..

http://support.microsoft.com/kb/816042

"Practice makes Perfect"
CPO rt'd RN

 

[58sniper]

pendal1

from a cmd prompt on any DC, run
netdom query fsmo

and you'll see which server holders that role (and the other 4).

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP