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 3 of 4)   Prev   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 ...

I have changed this registry setting to the maximum - this seems to have helped. Thanks to everyone who assisted me with this problem and of course, to you jack republic for giving a solution (I think :-) ).

Jennifer

Collapse -

Time difference between client & server

by CG IT In reply to Time difference between c ...

Windows & .NET magazine volume 8 # 11 page 73 has a nice article on Windows Time Service including Keberos's requirement for accurate time in ticket generation [not more than 5 minutes apart from client to DC]. Note Windows NT 4.0 & Windows 9X don'tautomatically sync up with a DC. one must do this manually. " You can put the command net time \\>computer name> /set /yes in a batch file and place a shortcut to the batch file in the startup folder to sync time every time the computer starts up" {quoted verbatum from Windows & .NET magazine].

Collapse -

Time difference between client & server

by CG IT In reply to Time difference between c ...

There is this interesting editorial in Windows & .NET magazine in the "Ask Dr. Bob" column about upgrading RAID 1 configuration Very similar to a question someone posted here on Technet about not to long ago about upgrading 2 9GB HDD's on RAID 1 with 2 18 GB HDD's. Try grabbing a copy of the Windows mag with the Time service article.

Collapse -

Time difference between client & server

by CG IT In reply to Time difference between c ...

Seems that if a question is asked here, chances are Windows & .Net mag just might have an article on it.

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

I'm not sure how relevant this will be, but I had exactly the same problem.
Certain users could not log in, as the system said their time was not synchronized. Even after running the command prompt and synching the time, it wouldn't log on.
What it actually turned out to be was that the only computers in affected were the users from our Accounts department. They were turning the DATE back on their machines to enter all the transactions for month A into our accounts system whilst actually being in the next month.
This was confusing at first, because when you sync the time, it does exactly that, it doesn't do the date as well, and normally windows is not too strict on the actual time, but will only give you a couple of days difference indate.

May be worth checking out.

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

run regedit
search time
change key datetimesetting.1

do y use a quotation on the hdd's or a time-out setting in the policy
change that

should work

INT

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

Have you considered investigating your domain controllers? Are you sure all AD data is being replicted properly? Are all clients and servers in the same site? What is the physical makeup of your network infrastructure.

Try using repadmin to seeif everything is running smoothly. Also netdiag will alert you on any connectivity issues.

Try replicating your domain in a small test lab using some spare desktop machines.

It sounds to me that you will need to reinstall Active Directory, sorry.

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

Related Discussions

Related Forums