Prev: 2000 to 2003 migration
Next: problems creating users in Active directory
From: Keli on 1 Jun 2007 04:43
Hello,

iIn my test network I have one domain controller and it's time server (PDC).
After some time (about 1 year) time server's clock begin to late few
minutes, so I need sync with interent time server.

Our router is sync with time server on the Internet and I tried to sync PDC
with router.

Registry key before modification on PDC was:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
"LocalNTP"=dword:00000000
"Period"="SpecialSkew"
"type"="NTP"
"ntpserver"="dcServer"

After my modification, (KB216734) registry key content is :

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
"LocalNTP"=dword:00000001
"Period"="SpecialSkew"
"type"="NTP"
"ntpserver"="10.1.1.1 "
"Adj"=dword:0002625d
"msSkewPerDay"="-1479,0000"



But on server I have errors:

Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 11
Date: 1.6.2007
Time: 4:38:43
User: N/A
Computer: DC_Server
Description:
The NTP server didn't respond
Data:
0000: 49 27 00 00 I'..


Where I did go wrong ????

In Registry there is no keys:

ReliableTimeSource, MaxAllowedClockErrInSecs

So I couldn' make changes for them, …


thanks for your time,

Keli
From: Ace Fekay [MVP] on 2 Jun 2007 09:18
In news:37719071-07B0-4A29-84BD-B2B42750EF2E(a)microsoft.com,
Keli <Keli(a)discussions.microsoft.com> typed:
> Hello,
>
> iIn my test network I have one domain controller and it's time server
> (PDC). After some time (about 1 year) time server's clock begin to
> late few minutes, so I need sync with interent time server.
>
> Our router is sync with time server on the Internet and I tried to
> sync PDC with router.
>
> Registry key before modification on PDC was:
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
> "LocalNTP"=dword:00000000
> "Period"="SpecialSkew"
> "type"="NTP"
> "ntpserver"="dcServer"
>
> After my modification, (KB216734) registry key content is :
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
> "LocalNTP"=dword:00000001
> "Period"="SpecialSkew"
> "type"="NTP"
> "ntpserver"="10.1.1.1 "
> "Adj"=dword:0002625d
> "msSkewPerDay"="-1479,0000"
>
>
>
> But on server I have errors:
>
> Event Type: Warning
> Event Source: w32time
> Event Category: None
> Event ID: 11
> Date: 1.6.2007
> Time: 4:38:43
> User: N/A
> Computer: DC_Server
> Description:
> The NTP server didn't respond
> Data:
> 0000: 49 27 00 00 I'..
>
>
> Where I did go wrong ????
>
> In Registry there is no keys:
>
> ReliableTimeSource, MaxAllowedClockErrInSecs
>
> So I couldn' make changes for them, .
>
>
> thanks for your time,
>
> Keli

By default, all Windows machines in a domain will automatically look for the
PDC Emulator as their time source. Even though time.windows.com shows as the
setting inthe reg, it goes gby the type=NT5DS (which means NT5 Directory
Services) which is essentially your PDC Emulator. If you changed it to NTP,
it maynot work because in reality the PDC Emulator is really not a NTP time
server.

I would leave all the windows machines alone as far as the reg. If you
already did this on all your test machines, you can create a logon script to
force the workstations to look at the PDC Emultor. Add this section in the
script or set a call for it in the main logon script:

======================
@echo off

rem Batch File Edit Date: 11/26/2006

set DOMAIN=YourDomainNetBIOSName
set TIMESVR=ServerNetBIOSName

echo *************************************************
echo.
echo WELCOME TO THE %DOMAIN% DOMAIN
echo.
echo *************************************************
echo Setting local clock
net time \\%TIMESVR% /set /y

> End
=======================


As for the PDC Emulator, run these commands to set it to an external source
(assuming it is Win2003). 192.5.41.41. is one of the US Navy time sources.

net stop w32time
net time /setsntp:192.5.41.41
net start w32time



For Win2000:

net stop w32time
net time /setsntp:192.5.41.41
w32tm -once
net start w32time


--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations

Having difficulty reading or finding responses to your post?
Instead of the website you're using, try using OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. Anonymous access. It's free - no username or password
required nor do you need a Newsgroup Usenet account with your ISP. It
connects directly to the Microsoft Public Newsgroups. OEx allows you
o easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject. It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

"Quitting smoking is easy. I've done it a thousand times." - Mark Twain


From: Keli on 4 Jun 2007 04:05
Ace thank you for reply,

I didn't make changes to machines in domain, so registry entry for them is
NT5DS.

I did changes on my domain controllre, PDC. I am just trying to sync PDC,
Win 2000 Advenced Server, with remote time server (my router).



Actually I did what you wrote

net stop w32time
net time /setsntp:192.5.41.41
net start w32time

"only" I did it manualy :), throug registry.

And as KB216734 say: ...put "type"="NTP"


?????

all weekend I have error again :( ... When I do:

C:\Documents and Settings\Administrator>w32tm -s
RPC to local server returned 0x0

and some articels say that is ok, but I am not sure ...


thanks again,

Keli


"Keli" wrote:

> Hello,
>
> iIn my test network I have one domain controller and it's time server (PDC).
> After some time (about 1 year) time server's clock begin to late few
> minutes, so I need sync with interent time server.
>
> Our router is sync with time server on the Internet and I tried to sync PDC
> with router.
>
> Registry key before modification on PDC was:
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
> "LocalNTP"=dword:00000000
> "Period"="SpecialSkew"
> "type"="NTP"
> "ntpserver"="dcServer"
>
> After my modification, (KB216734) registry key content is :
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
> "LocalNTP"=dword:00000001
> "Period"="SpecialSkew"
> "type"="NTP"
> "ntpserver"="10.1.1.1 "
> "Adj"=dword:0002625d
> "msSkewPerDay"="-1479,0000"
>
>
>
> But on server I have errors:
>
> Event Type: Warning
> Event Source: w32time
> Event Category: None
> Event ID: 11
> Date: 1.6.2007
> Time: 4:38:43
> User: N/A
> Computer: DC_Server
> Description:
> The NTP server didn't respond
> Data:
> 0000: 49 27 00 00 I'..
>
>
> Where I did go wrong ????
>
> In Registry there is no keys:
>
> ReliableTimeSource, MaxAllowedClockErrInSecs
>
> So I couldn' make changes for them, …
>
>
> thanks for your time,
>
> Keli
From: Ace Fekay [MVP] on 4 Jun 2007 07:02
In news:FBA720B7-E4CA-4FCB-AD65-B6986E140689(a)microsoft.com,
Keli <Keli(a)discussions.microsoft.com> typed:
> Ace thank you for reply,
>
> I didn't make changes to machines in domain, so registry entry for
> them is NT5DS.
>
> I did changes on my domain controllre, PDC. I am just trying to sync
> PDC, Win 2000 Advenced Server, with remote time server (my router).
>
>
>
> Actually I did what you wrote
>
> net stop w32time
> net time /setsntp:192.5.41.41
> net start w32time
>
> "only" I did it manualy :), throug registry.
>
> And as KB216734 say: ...put "type"="NTP"
>
>
> ?????
>
> all weekend I have error again :( ... When I do:
>
> C:\Documents and Settings\Administrator>w32tm -s
> RPC to local server returned 0x0
>
> and some articels say that is ok, but I am not sure ...
>
>
> thanks again,
>
> Keli
>
>


You didn't need to do this thru the reg. I gave you the easy method. Simply
running the commands I provided you will set in the reg. I would definitely
use 192.5.41.41 and not the router as your NTP source. It eliminates an
additional hop. Also, importantly enought, in order to allow inbound NTP
traffic, your firewall needs to allow UDP 123 to the PDC Emulator.

Ace


From: Keli on 4 Jun 2007 08:21
ok, I know, but I read article before your answer :)

I am cheking my network and I hope to find some solution ....


thanks Ace,


keli

"Keli" wrote:

> Hello,
>
> iIn my test network I have one domain controller and it's time server (PDC).
> After some time (about 1 year) time server's clock begin to late few
> minutes, so I need sync with interent time server.
>
> Our router is sync with time server on the Internet and I tried to sync PDC
> with router.
>
> Registry key before modification on PDC was:
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
> "LocalNTP"=dword:00000000
> "Period"="SpecialSkew"
> "type"="NTP"
> "ntpserver"="dcServer"
>
> After my modification, (KB216734) registry key content is :
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
> "LocalNTP"=dword:00000001
> "Period"="SpecialSkew"
> "type"="NTP"
> "ntpserver"="10.1.1.1 "
> "Adj"=dword:0002625d
> "msSkewPerDay"="-1479,0000"
>
>
>
> But on server I have errors:
>
> Event Type: Warning
> Event Source: w32time
> Event Category: None
> Event ID: 11
> Date: 1.6.2007
> Time: 4:38:43
> User: N/A
> Computer: DC_Server
> Description:
> The NTP server didn't respond
> Data:
> 0000: 49 27 00 00 I'..
>
>
> Where I did go wrong ????
>
> In Registry there is no keys:
>
> ReliableTimeSource, MaxAllowedClockErrInSecs
>
> So I couldn' make changes for them, …
>
>
> thanks for your time,
>
> Keli
 |  Next  |  Last
Pages: 1 2 3
Prev: 2000 to 2003 migration
Next: problems creating users in Active directory