Windows Thread, Irritating " The current time on this computer and the current time' error in Technical; Randomly, different machines in the school are getting the typical " The current time on this computer and the current ...
3rd September 2010, 09:25 AM #1
Irritating " The current time on this computer and the current time' error
Randomly, different machines in the school are getting the typical " The current time on this computer and the current time on the network are different" error when users attempt logging on.
The problem is, the time does not differ between the machines by more than half a minute.
Could someone give me some help to explain why this is happening, and what might fix it?
The only 'way around' we've found is to drop the computer from domain, and rejoin - but I don't want to do this with 300 computers, if they all start doing it.
IDG Tech News
3rd September 2010, 10:12 AM #2
Any errors from the time service in the event log?
as part of the machine start up script (shouldn't be necessary but it might just give it a kick)
3rd September 2010, 03:24 PM #3
Appears the fix is:
Log in local to the machine, open Command Prompt and run
net use \\server /user:username
net time \\server /set
Rejoin the domain
What a faff!!
3rd September 2010, 03:27 PM #4
It was always the case that back in teh NT 4.0 days your logon script would always contain a Net Time command. Saved a lot of faffing back then, still relevant now it appears.
3rd September 2010, 04:58 PM #5
I get this on the machines that have dodgy batteries on their motherboards (only 2 fortunately). The solution is never to turn them off at the wall - or if they do get turned off at the wall, then reset the clock by going into the bios setup on boot. I can usually get it close enough.
7th September 2010, 03:25 PM #6
you can set the time difference in Group policy if your PCs are already really close. The default is 5 minutes though, so someone must have fiddled.
7th September 2010, 03:28 PM #7
No-one has fiddled - the clocks match perfectly on the machines. ie. The server has 15:26:30 and the client has 15:26:30 yet the client still complains...
7th September 2010, 03:34 PM #8
The relative time is important because the default lifetime of a kerberos ticket is five minutes; more variation than this and tickets are invalid even as they are issued.
7th September 2010, 03:42 PM #9
Are the timezones all correct on the machines, a 12 hour offset for a differing timezone could easily cause this and may be easy to miss.
7th September 2010, 03:45 PM #10
Yup. All the machines are as they should be. The time is correct, timezone also. Nothing has changed on them - ie. many are exactly the same as they were at the end of last term, when they worked properly...
Originally Posted by SYNACK
7th September 2010, 10:49 PM #11
I still enter that as part of logon scripts to pull them back into line and it still works even to this day (well actually not tested on W7 yet....)
Originally Posted by Dos_Box
16th September 2010, 11:54 AM #12
Ok, found out what caused this! My domain still referenced a server that I had removed from being a DC. So, whilst it wasn't a DC, it still tried to get some info from it somehow - and that server's time was out by 9 minutes.
I've now manually removed all the settings in as described in the 'manually remove a DC' instructions on the MS Knowledgebase, and fixed the time and all is well again. Stupid thing!
By burgemaster in forum Windows 7
Last Post: 20th July 2010, 11:36 AM
By AmyJ121 in forum Windows 7
Last Post: 10th June 2010, 02:04 PM
By kerlj001 in forum MIS Systems
Last Post: 15th December 2008, 03:41 PM
By rocknrollstar in forum Windows
Last Post: 19th July 2008, 09:09 AM
Last Post: 31st January 2008, 12:17 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)