We help IT Professionals succeed at work.

The windows time service was not available .... concerns

jeffg_91911
jeffg_91911 asked
on
Medium Priority
732 Views
Last Modified: 2008-03-10
I have a windows 2000 server, and once a day the remote serve goes offline.
I noticed that in the Event Window, I see the following...

"the windows Time service was not able to find a Domain Controller.  A time and date update was not possible".
Would this cause the server to go off line?  What does this error mean?  How can I correct the problem?

Thanks

- Jeff
Comment
Watch Question

Gareth GudgerSolution Architect
CERTIFIED EXPERT
Most Valuable Expert 2014
Top Expert 2014

Commented:
All members of a domain elect a domain controller as the authorative time server.

This error could occur if you recently took that server offline or you are specifying the "net time" command somewhere for a server that is not present/reachable.

As far as crashing...i dont know. I would doubt it but time is key in a domain.

Author

Commented:
The Server does not crash, it goes offline.  Are you saying that the you doubt that this problem is causing the server to go offline?  I don't purposely take the domain offline, for some reason it goes offline by itself.  
Gareth GudgerSolution Architect
CERTIFIED EXPERT
Most Valuable Expert 2014
Top Expert 2014

Commented:
Well Kerberos authentication requires the time service to keep all clients and servers on a common time. Not sure why. Does the domain go offline right as this service fails?

Any event IDs?

Author

Commented:
I ran the net time command and it is using one of the other servers for the time.  I believe what is happening is that Server "A" goes offline and then it can't get the time from Server "B" and loggs it into the event log?  Any thoughts?
Thanks
-Jeff
Top Expert 2004
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
Good questions Deb;
Not sure if I can answer all of them.
To get the server back online, I re-boot.
The connection type is TCP/IP (if that answers your question?)
Yes it is a dc.



One test would be to replace the NIC?  Any thoughts on that?

Thanks

- Jeff
Top Expert 2004

Commented:
Sorry Jeff,

I meant could it be the connection to the remote was going down for some reason ie is it adsl, leased line etc or indeed flaky nic, although if a reboot works then I would have thought it may something else - but am not a hardware guru (don't like getting under the bonnet/hood much if I can help it a ;-), so it may well be worth swapping out the nic if only to rule it out as potentially it will save you stacks of time if indeed, it is only the nic. (But if you're there you may as well check the event logs first, check if connectivity has been lost to other pc's, servers or devices on the remote's local lan (if it is a lan?)

Connectivity is crucial though and the event logs should give further clues. When the remote server goes down can you still ping it by ip and name and also is there a firewall between both sites? (just in case icmp is blocked etc)

Also does it go down at a specific time or roughly similar time intervals?

I know lots of questions, but I think we need more clues to go on here

Deb :))
Top Expert 2004

Commented:
what kind of connection between your server and the remote server?
 physically how are they connected?

Author

Commented:
It's not  aremote server.  Just two Domain Controllers, connected on a LAN through tcp/ip with CAT 5, hubs, router, etc.
I'll swap the NIC card for a test.

Thanks

- Jeff
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.