Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, September 2, 2009 11:06 AM
hi
i am a beginner to the window administration. i am windows running server 2008 as domain controller. i added 7 xp machine to the domain controller. After adding the clients to the domain, the system time of the client domain not synch with the domain controller. i gave all the clients admin previledge and i enable the public file sharing. now no user can access the shared file from each other. when they try to access from the run by typing the //system name the following error is showed. \systemname is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. This server's clock is not synchronized with the primary domain controller's clock. Please guide me to solve the issue.
All replies (9)
Tuesday, September 8, 2009 8:33 AM âś…Answered | 3 votes
Hi,
Please run the command w32tm /resync on the client computers and check if the system time can be synchronized.
More information:
How to synchronize the time with the Windows Time service in Windows XP
http://support.microsoft.com/kb/307897
How to configure an authoritative time server in Windows Server
http://support.microsoft.com/kb/816042
Hope it helps.
This posting is provided "AS IS" with no warranties, and confers no rights.
Monday, November 19, 2012 11:35 PM
Hi,
Joson Zhou is right, But i have also found all other time sync. related troubleshooting at
http://networkingstudy.net/forums/index.php/topic,894
Thanks
Tuesday, December 18, 2012 11:34 AM
After running the w32tm /resync its showing access denied on the client (Win7) system.
Monday, May 13, 2013 8:35 AM | 1 vote
Use the command in elevated mode
Monday, October 21, 2013 1:43 AM | 2 votes
Dear all,
What worked for me is the command;
net time \DC /set
where DC is the name of the domain controller (including full domain name).
Success.
Leendert
Sunday, December 22, 2013 8:43 PM
I had all sorts of problems. Could not get exchange server to send and receive, veeam back up was not working, Outlook would not connect to exchange, could not RDP to any machine on the network. I applied KB 816042 on the DC and all problems are gone.
Friday, July 18, 2014 4:46 PM
You da man!
Thursday, June 11, 2015 1:15 PM
THANKS!!!!! YOU ARE A LIFE SAVER! Entered the command and poof! Worked like a charm!
Thursday, June 11, 2020 7:48 AM
Works for me. Thanks!