Time on Server 2003 and Workstations Slow; Cannot manually set 1

[mt4junkie]

Hello,

The time on the company's Windows 2003 server is about 1 minute, 51 seconds slow. This time seems to be copying itself to all of the workstations in the office, so everyone is behind. Setting the clock manually on either the workstation or the server works for about five minutes, but then it automatically syncs back to the slow time.

I came across this link (

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

but I can't tell if the time is coming from the hardware or somewhere else. I am also afraid to mess with the registry until I know more. Before I call in a contractor for $200+/hour, I was wondering if anyone else has had this problem and knows how to fix it.

Note: The "Internet Time" tab is not available in the Date/Time properties.

I am rather new to Windows Server 2003 management, and I was forced into the position. Our lead IT person has separated from the company, so the work falls on me for the time being. Pardon my ignorance. I have looked on the web and this forum for the answer to this question, but can't seem to find it.

Thanks in advance,
Mike

 

[58sniper]

In a domain, time synch comes from the domain controllers holding the PDC Emulator FSMO role. Your comments lead me to believe you have a single server, so that's what's giving the time to the workstations. That server is set to syncronize with an external time source.

Drop to a command prompt and run:

net time /setsntp:tock.usno.navy.mil

that will sync time to the atomic clock maintained by the Navy.

To see what the current time is there, see

http://tycho.usno.navy.mil/cgi-bin/timer.pl

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[mt4junkie]

Hello 58sniper,

Thank you for the code.

I ran this command from a command prompt on the server, and I received response "The command completed successfully." Unfortunately, the system time did not update. I logged out and back in just to check that, but the clock remains about 2 minutes slow.

There are two servers in the server rack. I ran this command on both servers with the same result. One server functions as an Exchange server. The other for backups and other services.

Do you have any other suggestions?

Mike

 

[TechyMcSe2k]

verify the sntp setting with
net time /querysntp

 

[58sniper]

Okay - well, you're jumping the gun, as it should only be run on one - the PDC emulator. Give it time to work. It's not always going to be immediate.

Also - check your DHCP scope and see if you have a time source configured in there. That doesn't happen too often, but I've seen them configured in there.

As TechMcSe2k mentions, run the query and see what it says. Verify the current time on the server with the manual link I provided.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[mt4junkie]

Sorry to jump the gun. I confirmed that the time has not yet updated (you can download a screen shot here

https://rcpt.yousendit.com/644093592/f5c271d08bbcb74e5a9740299462e7bc).

I will wait until later today or tomorrow to see if it updates. Thank you for your assistance.

 

[TechyMcSe2k]

Star for ya!

 

[58sniper]

Thanks, Techy!

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[Roadki11]

Make sure your DC can communicate out through your firewall on ntp/sntp port 123 or it wont update either.



RoadKi11

"This apparent fear reaction is typical, rather than try to solve technical problems technically, policy solutions are often chosen." - Fred Cohen

 

[mt4junkie]

Unfortunately today the time has not updated. I think the new suggestions are past my technical know-how, so I will probably call in a contractor.

Thank you again for all your suggestions.