Synchronize clocks with server computer

390 pts.
Tags:
Clock Synchronization
Date and Time
Network Time Synchronization
Windows Server 2003
Windows XP
Hi, I have a network setup using Windows 2003 Server with about 10 computers. I synchronize all the clocks to the server computer. Most of the computers are showing the correct time but 3 of them are exactly 1 hour behind. I ran net time in the command prompt on the ones that aren't set correct and it shows: Current time at \2-DC is 3/16/2009 5:45AM Local time <GMT-5:00> at \2-DC is 3/16/2009 6:45AM I ran the net time on the computers that show the correct time and it shows: Current time at \2-DC is 3/16/09 6:45AM My question is why is it showing the local time on the computers that don't work. Also, I'm located in time zone GMT-6:00, I'm thinking that this may be why the clocks are wrong, does anyone know how to change the time zone using the command prompt? Thanks for any assistance, Dustin

Answer Wiki

Thanks. We'll let you know when a new response is added.

If you wait another week or so, when the old daylight saving time used to be, the clocks should change at that time.
If the clocks that are behind by one hour are running Win 2000 than that BIOS is the problem. You can always set the time zone to a different one where you would gave the correct time.
You can do a search for a program called TZEDIT.exe (time Zone Edit). This seems to correct the problem in most cases.

****************
If the machines are win 2000, download <a href=”http://www.microsoft.com/downloads/details.aspx?FamilyID=bff59fcf-3148-40b8-a286-fe7274f6e4d8&displaylang=en”>timezone</a> from MS, run it with the following switch: /s 02:0:2:03 02:0:1:11
This should reset the DST information
******************

You can follow MS KB 914387 on manually modifying the Time Zone information. The easiest of the methods is to export teh Time Zone keys from a fully up to date Windows XP / Vista system and import the Time Zone keys on other systems. This is one of the described methods.

Additionally, you can download the TZEDIT utility and create a script to update systems.

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

******************

Discuss This Question: 6  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • RoadDust
    Hi Carlosdl, I've checked the date and time properties in control panel and they are set to the correct time zone. I even went into the registry and checked there and everything is correct. I even tried doing the following in the command prompt to resync the computer to the server: c:>net time /setsntp:2-dc.dc.local c:>net stop w32time c:?net start w32time c:>w32tm /resync I get messages that says it successful but they are still an hour behind. Dustin
    390 pointsBadges:
    report
  • carlosdl
    So the server is at GMT-05:00 and these machines are at GMT-06:00 ? Do the PCs that show the correct time have the same timezone that the problematic ones ?
    69,225 pointsBadges:
    report
  • RoadDust
    The server and the client computers are located in the same building in GMT- 6:00. I've used the net time on the server computer and it shows the correct time and it's set to the correct time zone.
    390 pointsBadges:
    report
  • carlosdl
    That's a little strange to me, since this was the output you got from the computer with wrong time. Current time at \2-DC is 3/16/2009 5:45AM Local time <GMT-5:00> at \2-DC is 3/16/2009 6:45AM I'm running out of ideas. Let's hope someone else can provide help.
    69,225 pointsBadges:
    report
  • Dwiebesick
    Are your problem workstations domain members? If so, then you can run this command: "net time /setsntp" What this command actually does is clear the NTPserver value value and set the Type in the registry to NT5DS if it is already set to Type=NTP. In essence, this tells the service on your workstations to participate in the domain hierarchy (Type=NT5DS) for time synchronization instead of using the NTP method to synch to the NTPServer value. Let us know, and I have to agree with Carlosdl that the information your initially provided and highlited by Carlosdl clearly indicated a time zone issue. The time zone NAME maybe the same (or not) it is the value in the registery that matters in this regard. The post regarding TZEDIT.exe is a little misleading but just might be what you need IF someone has previously changed the time zone values. This is unlikely, but posible. This is the area where I would do more troubleshooting as Carlosdl clearly identified an anomaly.
    2,235 pointsBadges:
    report
  • RoadDust
    Thanks Dwiebesick for your suggestion. I tried that but still didn't fix the issue. I think it might be on time.windows.com (which I found out that the server computer is sync to) because I have a stand alone computer at my house that I tried to sync with time.windows.com and it was an hour behind, I had to change the time zone to eastern standard to get it to display the correct time. I'm thinking that time.windows.com didn't update their daylight savings time, so I'm going to do what carlos suggested and wait a week and see if it changes. Dustin
    390 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following