Re: Time Sync Issue - Win2003 Domain
- From: "[c]" <no@xxxxxxxxx>
- Date: Sat, 5 May 2007 23:12:38 -0400
Paul thanks a lot for the extremely helpful reply! After running the
diagnostics using your interface everything checked out okay. Seems there is
another problem now that i will be posting with more information but i
wanted to thank you for taking the time to post such in a thorough indepth
reply.
"Paul Bergson [MVP-DS]" <pbergson@xxxxxxxxxxxxxxxxx> wrote in message
news:egFSk1kjHHA.1244@xxxxxxxxxxxxxxxxxxxxxxx
By default all clients should be using their authenticating DC as their
time service, not the PDCe. You really don't want to start configuring
time, let Windows figure out where it gets its time from. The dc's should
be using the PDCe as their time service. So first off I would validate
that the clients that are improperly getting their time are in fact doing
this. From a client you suspect is incorrectly configured, bring up a
commend prompt and time in
set logonserver
This should list the current dc this client authenticated too.
If this is incorrect then Sites and Services need to be defined for this
subnet
I'm sure you must have already followed the documents on configuring an
authoritative time server, but if not
http://support.microsoft.com/kb/816042
Have you run any diagnostics against your domain to verify that there are
no rep errors, etc...
If you don't have the tools installed, install them from your server
install disk.
d:\support\tools\setup.exe
Run dcdiag, netdiag and repadmin in verbose mode.
-> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
**Note: Using the /E switch in dcdiag will run diagnostics against ALL
dc's in the forest. If you have significant numbers of DC's this test
could generate significant detail and take a long time. You also want to
take into account slow links to dc's will also add to the testing time.
If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests
without having to learn all the switch options. The details will be
output in notepad text files that pop up automagically.
The script is located in the download section on my website at
http://www.pbbergs.com
Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)
When complete search for fail, error and warning messages.
You can turn on debugging for the Time Service, but alas I haven't ever
played with this. I believe though, this will then log errors in the
event log
http://support.microsoft.com/kb/816043/en-us
Have you checked your GPO's to make sure that something isn't being set to
point the clients to the remote dc?
Computer configuration/Administrative Templates /System/Windows Time
service/Time Providers
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no
rights.
"IT_Guru" <corey@xxxxxxxx> wrote in message
news:OVjhuhkjHHA.4896@xxxxxxxxxxxxxxxxxxxxxxx
I have a problem where a remote site domain controller is being used by
all clients as the preferred time sync server. I have never configured
this. I have always left the defaults for the time services so in other
words the DC in our Corporate office holding the master roles (PDC
Emulator) SHOULD be the preferred time server for all domain clients. Even
clients and servers in my corporate office are pointing to this remote dc
as their preferred time server and I dont know why they have chosen it,
since I have never configured any time services on it.
If I stop the time service on this server, after about 20 minutes or
maybe with domain replication the clients will start pointing back to the
corporate PDC. I have the corporate PDC set to sync with
time.microsoft.com, even the remote dc in question has been configured to
point to the PDC but afte running any of the commands like w32tm /resync
and then restart time service on this remote DC it keeps pointing to
itself, it will never update to point to the PDC.
Any ideas?...this is frustrating as hell and causing us some severe
problems as we are in multiple time zones!
Is it okay to disable the time service on remote DC's if you want the
clients syncing with the PDC of the domain?
Im trying to at least get all clients back on the same ground...I just
cant understand how the heck my servers and clients in the head office
are looking to this remote DC as their time server, DHCP even specifies
the PDC as the time server for clients.
Your help is appreciated!
.
- References:
- Time Sync Issue - Win2003 Domain
- From: IT_Guru
- Re: Time Sync Issue - Win2003 Domain
- From: Paul Bergson [MVP-DS]
- Time Sync Issue - Win2003 Domain
- Prev by Date: Re: Event question
- Next by Date: Deployment GPO for Office 2007 Professional Plus
- Previous by thread: Re: Time Sync Issue - Win2003 Domain
- Next by thread: Re: Time Sync Issue - Win2003 Domain
- Index(es):
Relevant Pages
|
