Re: time synch problem
- From: tnt <tnt@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 27 Oct 2008 14:13:01 -0700
John,
Would restore Windows Time service to default settings
on dcs (non pdc) be advisable?
I ran it on the test environment. It clears out the ntpserver field on the
registry. I noticed that when I do --> net time \\dc with non-pdc
/querysntp, the result show no sntp server.
Command:
net stop w32time
Type the following command and then press ENTER:
w32tm /unregister
Type the following command and then press ENTER:
w32tm /register
Type the following command and then press ENTER:
net start w32time
Just a thought.
Tnt
"John Policelli [MVP - DS]" wrote:
Run the following commands, in this order, on the non-PDC DCs:.
1) w32tm /config /syncfromflags:domhier /update
2) net stop w32time
3) net start w32time
You can also check the following registry key on each DC:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
The Type should be set to NT5DS in order for them to receive their time from
AD, and effectively the PDC. The PDC's type should be set to NTP.
--
John Policelli
Blog: http://johnpolicelli.wordpress.com
This posting is provided "AS IS" with no warranties and confers no rights!
Always test before proceeding.
"tnt" wrote:
John & Meinoff,
Thanks for the response.
John I have reviewed the link before posting.
On all 3 DCs now, they have links to external ntp server on the registry
(two of which point to pool.ntp.org and one time.windows.com)
registery
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
NtpServer (value data)
How do I make sure dc1 & dc3 don't use the external time server anymore?
Does running the above clears it off since dc1 used to be my pdc as the
article states"
http://technet.microsoft.com/en-us/library/cc738042.aspx
w32tm /config /syncfromflags:domhier /reliable:no /update
Type the following command and then press ENTER:
net stop w32time
Type the following command and then press ENTER:
net start w32time
"Meinolf Weber" wrote:
Hello tnt,
John mentioned all needed steps and so try it and please post the result,
if it is working now. With this command you should get the actual time server:
w32tm /dumpreg /subkey:\parameters
Should look similar like this,a the end you see the actual time server:
Value Name Value Type Value Data
------------------------------------------------------------
ServiceDll REG_EXPAND_SZ %systemroot%\system32\w32time.dll
ServiceMain REG_SZ SvchostEntry_W32Time
ServiceDllUnloadOnStop REG_DWORD 1
Type REG_SZ NTP
NtpServer REG_SZ ptbtime1.ptb.de,0x9
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Meinolf,
Thanks for your response as this is important issue.
When I did "netdom query fsmo", it points the fsmo roles to dc2.
Here is my plan, please verify:
----------------------------------------------------- on dc1, which
used to be the pdc emulator, I will do (to set it not reliable)
w32tm /config /syncfromflags:domhier /reliable:no /update
Type the following command and then press ENTER:
net stop w32time
Type the following command and then press ENTER:
net start w32time
------------------------------------------------------- On dc2, I will
do this.
w32tm /config /manualpeerlist:pool.ntp.org /syncfromflags:manual
/reliable:yes /update
With this command above, is it the same as below?
http://support.microsoft.com/kb/324801
I tried this on our test environment with no internet connection.
I am still seeing the pool.ntp.org in the registery
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameter
s NtpServer (value data). I guess its okay?
Also, is there a command to really tell me about the server that has
the "reliable" time source instead of assuming its the PDC? I know
setting w32tm /configure /reliable:yes/no, but what about its status?
"Meinolf Weber" wrote:
Hello tnt,
In a domain the PDCEmulator is the authoritative time server, find
out with "netdom query fsmo" from the command line without the
quotes. The PDCEmulator should be configured to use an external time
source or a hardware clock.
External time source:
w32tm /config /manualpeerlist:peers /syncfromflags:manual
/reliable:yes /update
With "peers" you can set the time source, either DNS name
(time.windows.com) or an ip address from a reliable time source.
Here you can find some of them:
http://www.pool.ntp.org/
Hardware clock, choose "Configuring the Windows Time service to use
an internal
hardware clock":
http://support.microsoft.com/kb/816042
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Hello,
We have 3 domain controllers.
From doing the following command, we get the sntp values.
net time \\server /querysntp
dc1 = pool.ntp.org
dc2 = pool.ntp.org
dc3 = time.windows.com,0x1
Both dc2 & dc3 have the same time. The time is ahead about 1.5 min
to the world It looks like dc2 tries to adjust the time of dc3.
dc1 has the correct time to the world.
What do I need to do to fix this? Suggestions?
TIA,
tnt
- Follow-Ups:
- Re: time synch problem
- From: John Policelli [MVP - DS]
- Re: time synch problem
- References:
- time synch problem
- From: tnt
- Re: time synch problem
- From: Meinolf Weber
- Re: time synch problem
- From: tnt
- Re: time synch problem
- From: Meinolf Weber
- Re: time synch problem
- From: tnt
- Re: time synch problem
- From: John Policelli [MVP - DS]
- time synch problem
- Prev by Date: Re: ADAM Hell
- Next by Date: Re: Prevent changes to Administrator password
- Previous by thread: Re: time synch problem
- Next by thread: Re: time synch problem
- Index(es):
Relevant Pages
|
