+ Post New Thread
Results 1 to 12 of 12
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 ...
  1. #1

    localzuk's Avatar
    Join Date
    Dec 2006
    Location
    Minehead
    Posts
    18,381
    Thank Post
    525
    Thanked 2,615 Times in 2,021 Posts
    Blog Entries
    24
    Rep Power
    891

    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.

  2. #2

    Join Date
    Aug 2005
    Location
    London
    Posts
    3,158
    Thank Post
    116
    Thanked 529 Times in 452 Posts
    Blog Entries
    2
    Rep Power
    124
    Any errors from the time service in the event log?

    Add

    w32tm /resync

    as part of the machine start up script (shouldn't be necessary but it might just give it a kick)

  3. #3

    localzuk's Avatar
    Join Date
    Dec 2006
    Location
    Minehead
    Posts
    18,381
    Thank Post
    525
    Thanked 2,615 Times in 2,021 Posts
    Blog Entries
    24
    Rep Power
    891
    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
    Restart

    What a faff!!

  4. #4

    Dos_Box's Avatar
    Join Date
    Jun 2005
    Location
    Preston, Lancashire
    Posts
    9,370
    Thank Post
    684
    Thanked 2,276 Times in 1,051 Posts
    Blog Entries
    23
    Rep Power
    674
    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.

  5. #5

    elsiegee40's Avatar
    Join Date
    Jan 2007
    Location
    Kent
    Posts
    10,084
    Thank Post
    1,901
    Thanked 2,379 Times in 1,749 Posts
    Rep Power
    833
    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.

  6. #6

    Join Date
    Jan 2008
    Location
    South West
    Posts
    1,838
    Thank Post
    219
    Thanked 271 Times in 219 Posts
    Rep Power
    69
    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.

  7. #7

    localzuk's Avatar
    Join Date
    Dec 2006
    Location
    Minehead
    Posts
    18,381
    Thank Post
    525
    Thanked 2,615 Times in 2,021 Posts
    Blog Entries
    24
    Rep Power
    891
    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...

  8. #8

    powdarrmonkey's Avatar
    Join Date
    Feb 2008
    Location
    Alcester, Warwickshire
    Posts
    4,867
    Thank Post
    412
    Thanked 778 Times in 651 Posts
    Rep Power
    182
    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.

  9. #9

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,270
    Thank Post
    884
    Thanked 2,747 Times in 2,321 Posts
    Blog Entries
    11
    Rep Power
    785
    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.

  10. #10

    localzuk's Avatar
    Join Date
    Dec 2006
    Location
    Minehead
    Posts
    18,381
    Thank Post
    525
    Thanked 2,615 Times in 2,021 Posts
    Blog Entries
    24
    Rep Power
    891
    Quote Originally Posted by SYNACK View Post
    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.
    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...

  11. #11

    john's Avatar
    Join Date
    Sep 2005
    Location
    London
    Posts
    10,432
    Thank Post
    1,534
    Thanked 1,066 Times in 931 Posts
    Rep Power
    305
    Quote Originally Posted by Dos_Box View Post
    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.
    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....)

  12. #12

    localzuk's Avatar
    Join Date
    Dec 2006
    Location
    Minehead
    Posts
    18,381
    Thank Post
    525
    Thanked 2,615 Times in 2,021 Posts
    Blog Entries
    24
    Rep Power
    891
    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!



SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 1
    Last Post: 20th July 2010, 12:36 PM
  2. Replies: 3
    Last Post: 10th June 2010, 03:04 PM
  3. Replies: 8
    Last Post: 15th December 2008, 04:41 PM
  4. Keeping a computer on ALL the time
    By rocknrollstar in forum Windows
    Replies: 14
    Last Post: 19th July 2008, 10:09 AM
  5. Replies: 7
    Last Post: 31st January 2008, 01:17 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •