Discussion Locked
0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am running a multi-site windows network with 2K and 2K3 servers. All are in a single domain with subnets connected via hardware VPN. We just opened another site in a different time zone. Whenever remote server is rebooted, and again at intervals through the day, the time setting on the server changes from central to pacific time. The fsmo server (and all the other servers) are on pacific time. Where/how do I tell this server to work in a different time zone but still play in the same domain?
6 replies
by curlergirl
Set the remote server to use a NTP server other than the FSMO server in your domain. You use the Net time command: net time /setsntp:[servername] to do this. You can select any available NTP server; a list of available public NTP servers can be found at: http://www.boulder.nist.gov/timefreq/service/its.htm
Hope this helps!
by curlergirl
PS I guess NIST actually recommends using the server's IP addy rather than the name; not sure why, but I just thought I'd mention it since I referred to the computer's name in my answer.
by a_liss
Did you setup the server in your main office and then ship it to the new location if so you may have forgotten to set the region to central time also make sure you have the use daylight savings time set correctly. Log in as admin double click the clock in the lower right corner and set the new server to central time. It will sync itself with the west coast servers and correct for time zones. Oh by the way Microsoft has all windows systems set to west coast time by default. So its easy to miss when setting up.
by bill.herde
Poster rated this answer.
by bill.herde
Thanks for the input. The issue was actually 3 fold. The region setting would drop back to PST periodically, and the net time /setsntp took care of that. There was still an issue with the workstations getting the correct time, which later blossomed into a general inability for users to authenticate to the home servers. Cause? One of the home servers had a failed DNS service, this caused AD replication to stop for servers looking to it for DNS. Thus workstations and servers had different sets of credetials and updating the time was not authorized for users on workstations.
by bill.herde
This question was closed by the author
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending
0 helpful
10 replies
Question Locked
Do You Save Useful Windows Tutorial Videos for Later
0 helpful
7 replies
0 helpful
1 reply
Question Unanswered
Is WSL still relevant in 2026?
0 helpful
0 replies
0 helpful
2 replies