Hey guys,
I am having an issue on my fileserver running Server 2008. The timeclock isn't keeping accurate time. This varies, but 1 second on the file server takes about 10-12 seconds to actually click to the next second. This is a major problem because after 5-10 minutes Kerberos security policies from the DC won't authenticate with the fileserver, kicking it off the network. Once this happens, all the Data (databases, archive psts, etc) becomes unavailable.
I've restarted the WT32 service, checked the BIOS time (which is correct and current), run Dell's diags with no errors, reset the time to sync with the DC...Nothing has worked.
Currently I have a script running in task scheduler to sync with the server, and have it scheduled to run three different times to be sure it runs. I did this because the lowest setting is every 1 minutes in task scheduler, and 1 minute on this machine takes a lot longer then an actual minute.
I've also changed the default Kerberos time-limit to 120 minutes, from the default 5. This is for short-term so that the users can continue to work while I troubleshoot.
Any thoughts? One option is to change the file server settings to update to the hardware time clock as opposed to the DC, but that involves registry changes and it isn't really a fix, but a workaround.
Also, both servers are PowerEdge 2900's.
Thanks
Tim
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I've tried this...It says the command completes successfully, but doesn't actually work.
I've also tried to redefine the source as the same server. It completes and updates the time, but doesn't fix the problem because the seconds are very slow.
I've also run multiple virii/spyware scans with different products, thinking that could be it. They've found nothing...
Any thoughts?
Thanks
Tim
Check this out.
http://blogs.techrepublic.
dariusg, I've seen that article. I've actually run those commands, but didn't get very far.
debuggerau, if you mean CMOS battery, I've run tests on it and they've passed. I can try to have dell send one out. IF not the CMOS battery, I'm not sure what you mean?
IT is odd though that the clock just doesn't keep time correctly. Even when I disable the windows time service, reboot, and start a third party clock, it still doesn't update. It's like something is holding it back from ticking.
Another thing I've noticed, the whole system seems extremely sluggish. I've run the processor tests and memory tests, but is it possible the processors are bad/misconfigured?
Thanks for the posts...
Tim
Business Accounts
Answer for Membership
by: dariusgPosted on 2009-09-22 at 11:58:24ID: 25396216
Run w32tm /resync /rediscover.