General discussion

Locked

Time difference between client & server

By jet1415 ·
I have a windows 2000 domain with AD running - 3 domain controllers and have never set up any time solution on the servers. Whenever a client reboots, when it comes back up and tries to login to my W2K domain, the user gets an error that there is atime difference between the client and server and you can not be logged into the domain. I have read every possible white paper and knowledge base article on this and can not figure out why it keeps happening. When the client gets the error one ofour sysadmins has to go to their desk and log into a local admin account and run the w32tm cmd to force the workstation to sync up it's time. Once we run the command we can shut down the system and reboot it and they can login fine. Once they reboot again they will get the error again. I would like to know if anyone has had this problem before and if so how did you pinpoint it and/or solve it? Thanks.

This conversation is currently closed to new comments.

32 total posts (Page 2 of 4)   Prev   01 | 02 | 03 | 04   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Time difference between client & server

by Greybeard770 In reply to Time difference between c ...

With Windows2000 you don't need third party time management. We have one server that synchronizes with the US Naval Observatory and everybody else gets their time from that server. Articles Q232255, Q224799, Q216734 give you information about setting up a domain controller. I find it nice to let the time sync process make an entry to the system log when it happens. Use the command:
net time /setsntp:192.5.41.209
instead of the DNS name for the USNO server.

If this problem is only happening on one client, it could be the CMOS battery getting weak. I have seen clocks run a little fast when that happens.

Collapse -

Time difference between client & server

by jet1415 In reply to Time difference between c ...

Been there, tried that - it's not happening on only one client - it's happened on at least every client in the domain at least once if not more than once. Thanks for your input - any other ideas, please let me know.

Collapse -

Time difference between client & server

by maxwell edison In reply to Time difference between c ...

Microsoft Knowledge Base Article - Q120944

"Using NET TIME for all Workstations and Servers"

SUMMARY:
In a network with different network client software, different workgroups, and different domains, maintaining a logon script that issues a NET TIME command can become complex. This article offers a simple solution to keep the time for all clients in the network synchronized.

MORE INFORMATION:
The solution to keeping all workstations' time synchronized with a particular server can besolved by either running a logon script for each workstation or by having each workstation run a batch file on their own after logging on to the network.

For example, assume you have a server named TIMESRV that has a reliable system clock. An example batch file that would run either from the workstation, or get called from or be part of a logon script, would look like this:

NET TIME \\TIMESRV /SET /YES

Using just a server name instead of the /DOMAIN or /WORKGROUP parameter avoids the complexity of maintaining different logon scripts or batch files for the different types of network client software. Please keep in mind that if all of your workstations are running the same type of network client software, you may choose instead to use the /DOMAIN or /WORKGROUP parameter. But, in a network with a variety of network client software, it might be easiest to use the "\\computername" (without quotation marks) parameter.

NOTE: NET TIME is enabled by default on all Windows NT workstations and servers.

LINK:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;q120944&

Collapse -

Time difference between client & server

by maxwell edison In reply to Time difference between c ...

For a Microsoft Windows XP version of this article, see:

Microsoft Knowledge Base Article - Q314090

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314090

How to Configure an Authoritative Time Server in Windows 2000:

MicrosoftKnowledge Base Article - Q216734

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q216734

HOW TO: Synchronize the Time Using the Windows Time Service:

Microsoft Knowledge Base Article - Q307897

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q307897

REMOVE SPACES from the pasted URLs

Collapse -

Time difference between client & server

by jet1415 In reply to Time difference between c ...

Poster rated this answer

Collapse -

Time difference between client & server

by ctmoore1998 In reply to Time difference between c ...

You could create a login script for your workstations with the this cmd
NET TIME \\SERVER /set /y
This will set the client workstation to the login server. You should set up a time server for the 3 domain controller's or put this same cmd in the admin login script and use just one of the domain servers as a time server.

Collapse -

Time difference between client & server

by jet1415 In reply to Time difference between c ...

Poster rated this answer

Collapse -

Time difference between client & server

by Alpha-Male In reply to Time difference between c ...

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q232386&

SYMPTOMS


When you attempt to log on to the network, you may receive the following error message:

The system cannot log you on due to the following error:
There is a time difference between the Client and Server.
Please try again or consult your system administrator.
CAUSE
This behavior can occur if the time or date is not synchronized between your computer and the domain to which you are attempting to log on. If the client computer's time or date is not synchronized with the authenticating domain controller, Kerberos validation does not succeed. This occurs because of the variation in the time stamps between the AS_Req and AS_reply between the client and server. Because Kerberos is the only form of logon authentication between two Windows 2000-based computers, the logon does not succeed.
RESOLUTION
To resolve this issue, log on to your computer locally using an account with administrative privileges and set the time and date to match the time and date on the domain controller that validates your logon. Below is list of steps that can be used to synchronize the time.


Click Start, Run
Type in CMD and click OK
At the command prompt type something similar to the following:NET TIME /DOMAIN:name /SET


Where "name" is the domain name being used by the computer. If you are not certain what the domain name should be replace name with "%userdomain%" without the quotes.

Here is anothergood resource for issues like this:

http://www.labmice.net/Windows2000/timesynch.htm

Good luck, hope this helps!

Collapse -

Time difference between client & server

by jet1415 In reply to Time difference between c ...

Poster rated this answer

Collapse -

Time difference between client & server

by jack republic In reply to Time difference between c ...

You can also modify the domain group policy under
windows settings/security settings/kerberos policy
Maximum tolerance for computer clock synchronization (the default value is 5 minuts)
you can increase it up to 9999 minuts.

Back to Windows Forum
32 total posts (Page 2 of 4)   Prev   01 | 02 | 03 | 04   Next

Related Discussions

Related Forums