W32Time Service 1

[suti]

Hi together,

*First: We use a NT4 Domin whit NT4, W2K and W2K3 Server*

I have upgradet my W2k Time Server to a Windows 2003 Server.
Now it's not longer possibel to synchronsation my W2k Clients whit this NT4-Domain Member TimeServer Server.

The Registry from the Tme Server looks like this:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time]
"Description"="Maintains date and time synchronization on all clients and servers in the network. If this service is stopped, date and time synchronization will be unavailable. If this service is disabled, any services that explicitly depend on it will fail to start.

"
"DisplayName"="Windows Time"
"ErrorControl"=dword:00000001
"FailureActions"=hex:XXX
"Group"=""
"ImagePath"=hex(2):XXX
"Objectname"="LocalSystem"
"Start"=dword:00000002
"Type"=dword:00000020

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config]
"LastClockRate"=dword:0002625a
"MinClockRate"=dword:000260d4
"MaxClockRate"=dword:000263e0
"FrequencyCorrectRate"=dword:00000004
"PollAdjustFactor"=dword:00000005
"LargePhaseOffset"=dword:02faf080
"SpikeWatchPeriod"=dword:00000384
"HoldPeriod"=dword:00000005
"LocalClockDispersion"=dword:0000000a
"EventLogFlags"=dword:00000002
"PhaseCorrectRate"=dword:00000001
"MinPollInterval"=dword:0000000a
"MaxPollInterval"=dword:0000000f
"MaxNegPhaseCorrection"=dword:ffffffff
"MaxPosPhaseCorrection"=dword:ffffffff
"UpdateInterval"=dword:00007530
"AnnounceFlags"=dword:0000000a
"MaxAllowedPhaseOffset"=dword:0000012c

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
"ServiceMain"="SvchostEntry_W32Time"
"ServiceDll"=hex(2):XXX
"Type"="NoSync"
"ntpserver"="NTINVENTORY,0x1"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Security]
"Security"=hex:XXX

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient]
"Enabled"=dword:00000000
"InputProvider"=dword:00000000
"AllowNonstandardModeCombinations"=dword:00000001
"CrossSiteSyncFlags"=dword:00000002
"ResolvePeerBackoffMinutes"=dword:0000000f
"ResolvePeerBackoffMaxTimes"=dword:00000007
"CompatibilityFlags"=dword:80000000
"EventLogFlags"=dword:00000001
"LargeSampleSkew"=dword:00000003
"DllName"="C:\\WINDOWS\\system32\\w32time.dll"
"SpecialPollTimeRemaining"=hex(7):00,00
"SpecialPollInterval"=dword:00000e10

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer]
"InputProvider"=dword:00000000
"AllowNonstandardModeCombinations"=dword:00000001
"DllName"="C:\\WINDOWS\\system32\\w32time.dll"
"Enabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Enum]
"0"="Root\\LEGACY_W32TIME\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001

The Clients look so:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time]
"Description"="Stellt die Systemuhr."
"DisplayName"="Windows-Zeitgeber"
"ErrorControl"=dword:00000001
"Group"=""
"ImagePath"=hex(2):XXX
"Objectname"="LocalSystem"
"Start"=dword:00000002
"Type"=dword:00000020

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
"LocalNTP"=dword:00000000
"Period"="SpecialSkew"
"type"="NTP"
"Adj"=dword:0002625b
"msSkewPerDay"="8853.3333"
"ntpserver"="ntinventory"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Security]
"Security"=hex:XXX

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Enum]
"0"="Root\\LEGACY_W32TIME\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001

When i do net time on the Client he call me that no Timeserver is available.

Thx for Help!!!!!

Cheers
Joachim

 

[Jpoandl]

Windows 2000/2003 uses w32Time to synch time. ‘The timesrv.exe utility from the original Windows NT 4.0 Server Resource Kit doesn't support the Network Time Protocol (NTP) that Win2K systems need. Microsoft has released updates for w32time and timesrv, the tools you need to successfully set up an NT 4.0 system that operates as an official time server. However, the updates are hidden in a most unlikely spot: a folder called Y2kfix at Microsoft’s FTP site. You can download the tools and documentation from ftp.microsoft.com/reskit/y2kfix/x86. Microsoft article Q258059 contains all the information you need to create an NT 4.0 NTP server.’

Maybe add the w32Time service in your NT 4 domain:

http://www.microsoft.com/technet/prodtechnol/winntas/support/y2knt4rk.mspx

More information about the service:

http://support.microsoft.com/defaul...port/kb/articles/Q224/7/99.ASP&NoWebContent=1

How to configure Authoritative Time server:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;216734

W32Time Registry settings and thier meanings:

http://support.microsoft.com/defaul...port/kb/articles/q223/1/84.asp&NoWebContent=1

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[suti]

Hi,

Thx for your answer. But my problem is not the Timeserv.exe from Win NT (this is upgradet to w32time and works correct).
My problem is the W2K Client that can not adjust itself to my W2K3 Timeserver ("no Timeserver is available"). And when i look in our Network-environment, the Timeserver does not indicate as such one. I don't no why.

Joachim

 

[Jpoandl]

W32Time would work by default if your domain was Windows 2000 or Windows 2003. When a Windows 2000 or higher client joins a Windows 2000 or higher domain, the client will look to the PDC emulator to synch time (no manual configuration is needed.)

I believe that in your situation, the domain is actually NT 4.0. Because of this, time synch does not happen automatically. I have not seen a situation like this in my experience. But I would start by manually setting a Windows 2000 or XP client to point to the time server. This is a registry setting that must be set. Alternatively, you can use the Net Time command on the client to point to a time source.

NET TIME
[\\computername | /DOMAIN[:domainname] | /RTSDOMAIN[:domainname]] [/SET]
[\\computername] /QUERYSNTP
[\\computername] /SETSNTP[:ntp server list]

So use the /SETSNTP:yourtimeservername.

Then reboot the client.

Then do net time to see if the client synchs with your time server.

-later

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)