Net set time sets time one hour off.

Here's a puzzlement.  I have a batch file that runs on the secondary servers every 6 hours and on every workstation at user logon.  Same batch file.  Simple little thing, just a net time set etc.

Here's whats' odd.  The secondary servers get the right time when the job runs on them (either on schedule or just by running the batch job) but the workstation get a time that is an hour off.  For example, if the server time is 11:15 and I run the job on a secondary server, the server time is set to 11:15, but if I run it on the workstation, the time on the workstation is set to 10:15.  I've tried it with the DST autoadjust box checked and unchecked - no difference.

Anyone know what is going on?  The workstations are Win2K SP4 and the server is Win 2003.

Ronald HicksConsultantAsked:
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.

SteveGTRCommented:
Daylight saving bug? Have you applied the latest patches?
0
rindiCommented:
If you're in a time zone that is one hour off from UTC, then also check your BIOS. In some BIOS's you can define whether the system time is UTC or your time zone. Also make sure the PC's are set to the correct TZ.

Also, if your PC's logon to a windoze domain, they get their time from the DC's, and then a batch file that sets the time would be reset to what the DC sends out.
0
Ronald HicksConsultantAuthor Commented:
I've got all the lates updates; whatever comes down from Windows Update and Microsoft Update anyway.  Yes, my PCs and DCs are in and set to the same time zone.  Still, all the PCs get set by the batch file to an hur off.  If I don't run the net time set as part of logon script or as stand alone batch file nothing happens at logon.  What did you mean, rindi, by saying that the PCs get their time from the DC.  Do you mean that this happens automatically simply as part of being a windows 2003 network?  That doesn't seem to happen.  If I change the time on a PC to something wildly diffrerent from the DC and logoff and logon without the net set command, the time stays at the wildly different one I had set on the PC.  I'm now just waiting to see if this goes away when the "real" date for changing to Daylight Saving time comes, but I'm dubious since it didn't matter whether I had "automatically adjust for DST" checked or not.  Does is matter that my cleints are Windows 2000 (SP4) and not XP or Vista?

--ron
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

Brian PringleSystems Analyst II, SCM, ERPCommented:
Go to any computer in the domain and issue the following command at a command prompt.

net time

What computer is listed as being the time server?  Note that name and then issue the following command on each affected computer, as well as the computer that is listed as the time server.  Replace %%timeservername%% with the name of the server provided by the last command.

net time /setsntp:%%timeservername%%

Then, go to the Time Server and manually set the correct time.  The other servers should now synchronize with the correct time on that server every time your script runs.
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
Brian PringleSystems Analyst II, SCM, ERPCommented:
As an answer to your questions...

1. The time in a Windows domain is automatically set by the first DC in the domain, unless you manually change that.

2. Logging off and back on won't make the workstation verify the time on the Time Server.  You would have to either reboot the computer or restart the "Windows Time" service.

3. It does not matter which OS is installed on the workstations, as long as you have all the DST patches installed.
0
Ronald HicksConsultantAuthor Commented:
Thanks btpringle.  I'll try that.  Maybe tomorrow unless events of Holy Week overtake me. ( I work at a church.)  I'll go ahead and closet this out and up the points.

Many thanks, Ron Hicks, St. Alban's Episcopal Church, Washington DC
0
Brian PringleSystems Analyst II, SCM, ERPCommented:
No problem!  Please let me know if there is anything else that we can do for you.
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 Batch

From novice to tech pro — start learning today.