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 1 of 4)   01 | 02 | 03 | 04   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Time difference between client & server

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

Point value changed by question poster.

Collapse -

Time difference between client & server

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

Time Difference Exists Between the Client and the Server Q297234

http://tinyurl.com/2drx

Verify that the Windows Time Service is running on the clients and the servers. The clients should get their time updated when they boot up and the machine's contact a domain controller for machine account authentication.


How to Configure an Authoritative Time Server in Windows 2000 Q216734

http://tinyurl.com/2ds0

Collapse -

Time difference between client & server

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

I've done this and it didn't help. I have read every knowledge base article and white paper on this issue and I can't figure out why it continues to happen. All of a sudden we got this error for no reason - everything had been working fine and then all of sudden.... any other ideas you have please let me know. Thanks for responding.

Collapse -

Time difference between client & server

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

You might also want to view MSKB Q321290

I ran into this problem when one Win2000 machine would not increment correctly (the longer the computer was used, the greater the time would lag -- but it would only lag in Windows. When I went to a command prompt to see what the system time was, it'd be correct).

After editing the registry key from the above Q article, all the time problems went away.

---
See if your client computer's system time (BIOS) matches the Windows time. If the WIndows time is off, edit the registry key or remove it entirely. Then test and see if that makes any difference.

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 maxwell edison In reply to Time difference between c ...

Windows 2000 and XP have a built-in time synchronization service called Windows Time or W32Time. Unlike previous versions of Windows or NT, Windows 2000 requires that the machine clocks within a domain be roughly synchronized. The identification tokens generated by the Kerberos 5 authentication method have a built-in expiration. If the machine clocks are not synchronized, a client could generate an identification token that appears, to a server, to have expired by the time it was generated. This is what you may be experiencing. Microsoft addressed this problem by including the Windows Time service with Windows 2000, but Windows Time (W32Time) was never intended to be an enterprise time solution. It is "good enough" for Kerberos on Windows 2000, but does not attempt to address timing needs beyond that (see The Windows Time Service, Microsoft, April 2001).

http://www.microsoft.com/WINDOWS2000/techinfo/howitworks/security/wintimeserv.asp

REMOVE SPACES from the pasted URL.

(A link to download/view the entire article is on the upper right of that Web page.)

The Windows 2000 Windows Time (W32Time) service only works on Windows 2000 and XP machines. For a pure-Microsoft solution, you can use a combination of batch files andlogon scripts for WfWG and Win9x machines, and TimeServ or W32Time for NT4 for NT machines. (Do not confuse the W32Time for NT4 with the W32Time that ships with Windows 2000. The original W32Time for NT4 works like TimeServ. The new one for Windows 2000 has additional features.)

(continued...)

Collapse -

Time difference between client & server

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

However, there are significant drawbacks to using a pure-Microsoft solution. First, the NET TIME command-line tool, required for WfWG, Win95, Win98, and ME, does not meet the requirements for a modern time solution. Second, while the new Windows Time service for Windows 2000/XP addresses some of NET TIME's problems, it has problems of its own (see entire article - link provided below).

Domain Time II is much more robust and easier to manage than the native W32Time Time Service, and it is designed to replace it seamlessly. It also has special features to co-exist with the service when necessary. Read more.

----------

The preceding is only an excerpt from the article, "Overview of Windows Time Service" found at the following link:

http://www.greyware.com/software/domaintime/product/w32time.asp

REMOVE SPACES from the pasted URL.

It's a very thorough and descriptive article with several additional links to related information.

Collapse -

Time difference between client & server

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

I've actually been using the Domain Time II trial product and we still have issues with clients not being able to log into the domain. There is no rhyme or reason to it..... It's not the same client every time or the same subnet - I can't pinpoint the problem. If you have any additional ideas please let me know. Thanks for your input.

Collapse -

Time difference between client & server

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

I have had this problem, by me it was gone after I ran NET TIME /CONFIG command on the PDC (FSMO/DC in Windows 2K lingo)

Collapse -

Time difference between client & server

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

Poster rated this answer

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

Related Forums