Time issues
From: Oscar (anonymous_at_discussions.microsoft.com)
Date: 08/13/04
- Next message: Kevin: "Can I use SQL & Exchange on the same box?"
- Previous message: rmorris_at_brewhaus.com: "Re: Networking Issue"
- Next in thread: Dave Nickason [SBS MVP]: "Re: Time issues"
- Reply: Dave Nickason [SBS MVP]: "Re: Time issues"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 13 Aug 2004 10:16:24 -0700
I recently joint a second AD DC to our domain.
now every morning when I try to login to both DC's the
original DC logs in fine, but the new one gives me an
error message saying that "there is a time diferece
between the client and the server" In order to temporary
resolve this issue I turn off that server and wait a few
minutes, turn it back on and login.
Befor the new DC came into play, the only DC we had was
running Tardis 2000 a time synchronization program. all
the clients look to this server for time using a second
add-on program that works with Tardis.
In order to resolve the time issue between the two DC's I
tried running Tardis on both DC, first making one the
main time server, then the other with out success (made
one server look to the other for time, then reversed)
Then I tried eliminating Tardis from the new DC and ran
the following command at cmd, "net time /setsntp:time-
b.nist.gov. and again no sucsess.
The weird thing about this is that the issue appears to
be mainly in the morning, as if something at night causes
the issue, becasue once I shut down the new DC in the
morning for a few minutes and then login, I can logout or
restart it and wait three, four hours then log back in
and works fine.
tia,
Oscar
- Next message: Kevin: "Can I use SQL & Exchange on the same box?"
- Previous message: rmorris_at_brewhaus.com: "Re: Networking Issue"
- Next in thread: Dave Nickason [SBS MVP]: "Re: Time issues"
- Reply: Dave Nickason [SBS MVP]: "Re: Time issues"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
