From: Russell3 on 26 Oct 2006 16:46 Hello Chace "chace zhang" wrote: > Hi, > > Thank you for your update. > > At present, Crina is not in the office, I will work with you on this issue. > > First, please confirm does this issue occur on SBS Server or on clients? > The problem is only on the SBS Server. Only its System event log has W32Time 29 26/10/2006 6:07 p.m. 1 The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 960 minutes. NtpClient has no source of accurate time. > Based on my experience, Since SBS Server is the root domain, you should > configure the PDC operations master(SBS Server) to gather the time from an > external source. I am trying to do this as you suggest. > > Windows-based computers use the following hierarchy by default: > > - All client desktop computers nominate the authenticating domain > controller as their in-bound time partner. > > - All member servers follow the same process as client desktop computers. > > - Domain controllers may nominate the primary domain controller (PDC) > operations master (root of the forest) as their in-bound time partner but > may use a parent domain controller based on stratum numbering. > > - All PDC operations masters follow the hierarchy of domains in the > selection of their in-bound time partner. > > Following this hierarchy, the SBS Server (PDC operations maste)r at the > root of the forest becomes authoritative for the organization. Please > review the following article for more related informaton: > > 216734 How to Configure an Authoritative Time Server in Windows 2000 > http://support.microsoft.com/?id=216734 > > You may try the steps below to synchronize an internal time source with an > external time source on SBS Server. > > 1. Open a Command Prompt. > > 2. Type the following, where PeerList is a comma - separated list of DNS > names or Internet protocol (IP) addresses for the desired time sources: > > w32tm /config /manualpeerlist:<time source>,0x8 /syncfromflags:MANUAL > > For example: w32tm /config /manualpeerlist: ntp.cs.mu.OZ.AU,0x8 > /syncfromflags:MANUAL > > w32tm /config /update > > > 4. Check the Event Log. If the computer cannot reach the servers, the > procedure fails and an entry is written to the Event Log. > > The most common use of this procedure is to synchronize the internal > network's authoritative time source with a very precise external time > source. > > In many cases, it may not be necessary to have all servers times > synchronized with an external source, as long as they are synchronized with > the same internal source. > > There are several SNTP time servers run by the New Zealand time that are > satisfactory for this function, for example: > Melbourne Australia: The University of Melbourne > 128.250.36.2: ntp.cs.mu.OZ.AU > > > Hamilton, New Zealand: The University of Waikato > truechimer.waikato.ac.nz; truechimer1.waikato.ac.nz; > truechimer2.waikato.ac.nz; truechimer3.waikato.ac.nz > > The NTP uses port 123 so this port must be opened on a firewall or router > to ensure proper communication with the NTP server. > > I have included the following article for your reference: > > 262680 A List of the Simple Network Time Protocol Time Servers That Are > http://support.microsoft.com/?id=262680 > > > > > The "net time /query" query the registry key in > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters > > > If you have any questions, please feel free to let me know. > > > Best Regards, > > Chace Zhang (MSFT) > > Microsoft CSS Online Newsgroup Support > > Get Secure! - www.microsoft.com/security > > Thanks Chance. You have taken the approach in sugsting that the problem lies in the SBS Server not being able to contact an external time source that is distant, for example in the USA. I think this is not the problem as I have used Atomic Clock Sync v2.7.0.3 with several time sources and all work. What I have not done is ensure the response times are low enought to work with W32Time in SBS 2003. So I will try your suggestion now of using a closer time source, say one in Australia or New Zealand. I will then report back to you here for common benefit. Thanks, Russell
From: Russell3 on 26 Oct 2006 18:49 Hello Chance I tried your suggestions and still the same error. What I have not verified is that port 123 is open. I thought it was as an alternate Time Program Atomic Clock, was working OK. However I do not know it uses port 123. I am not a specialist in networks ... can you advice how I can test if port 123 is open for use? Thanks Russell "chace zhang" wrote: > Hi, > > Thank you for your update. > > At present, Crina is not in the office, I will work with you on this issue. > > First, please confirm does this issue occur on SBS Server or on clients? > > Based on my experience, Since SBS Server is the root domain, you should > configure the PDC operations master(SBS Server) to gather the time from an > external source. > > Windows-based computers use the following hierarchy by default: > > - All client desktop computers nominate the authenticating domain > controller as their in-bound time partner. > > - All member servers follow the same process as client desktop computers. > > - Domain controllers may nominate the primary domain controller (PDC) > operations master (root of the forest) as their in-bound time partner but > may use a parent domain controller based on stratum numbering. > > - All PDC operations masters follow the hierarchy of domains in the > selection of their in-bound time partner. > > Following this hierarchy, the SBS Server (PDC operations maste)r at the > root of the forest becomes authoritative for the organization. Please > review the following article for more related informaton: > > 216734 How to Configure an Authoritative Time Server in Windows 2000 > http://support.microsoft.com/?id=216734 > > You may try the steps below to synchronize an internal time source with an > external time source on SBS Server. > > 1. Open a Command Prompt. > > 2. Type the following, where PeerList is a comma - separated list of DNS > names or Internet protocol (IP) addresses for the desired time sources: > > w32tm /config /manualpeerlist:<time source>,0x8 /syncfromflags:MANUAL > > For example: w32tm /config /manualpeerlist: ntp.cs.mu.OZ.AU,0x8 > /syncfromflags:MANUAL > > w32tm /config /update > > > 4. Check the Event Log. If the computer cannot reach the servers, the > procedure fails and an entry is written to the Event Log. > > The most common use of this procedure is to synchronize the internal > network's authoritative time source with a very precise external time > source. > > In many cases, it may not be necessary to have all servers times > synchronized with an external source, as long as they are synchronized with > the same internal source. > > There are several SNTP time servers run by the New Zealand time that are > satisfactory for this function, for example: > Melbourne Australia: The University of Melbourne > 128.250.36.2: ntp.cs.mu.OZ.AU > > > Hamilton, New Zealand: The University of Waikato > truechimer.waikato.ac.nz; truechimer1.waikato.ac.nz; > truechimer2.waikato.ac.nz; truechimer3.waikato.ac.nz > > The NTP uses port 123 so this port must be opened on a firewall or router > to ensure proper communication with the NTP server. > > I have included the following article for your reference: > > 262680 A List of the Simple Network Time Protocol Time Servers That Are > http://support.microsoft.com/?id=262680 > > > > > The "net time /query" query the registry key in > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters > > > If you have any questions, please feel free to let me know. > > > Best Regards, > > Chace Zhang (MSFT) > > Microsoft CSS Online Newsgroup Support > > Get Secure! - www.microsoft.com/security > > ===================================================== > This newsgroup only focuses on SBS technical issues. If you have issues > regarding other Microsoft products, you'd better post in the corresponding > newsgroups so that they can be resolved in an efficient and timely manner. > You can locate the newsgroup here: > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx > > When opening a new thread via the web interface, we recommend you check the > "Notify me of replies" box to receive e-mail notifications when there are > any updates in your thread. When responding to posts via your newsreader, > please "Reply to Group" so that others may learn and benefit from your > issue. > > Microsoft engineers can only focus on one issue per thread. Although we > provide other information for your reference, we recommend you post > different incidents in different threads to keep the thread clean. In doing > so, it will ensure your issues are resolved in a timely manner. > > For urgent issues, you may want to contact Microsoft CSS directly. Please > check http://support.microsoft.com for regional support phone numbers. > > Any input or comments in this thread are highly appreciated. > > ===================================================== > > This posting is provided "AS IS" with no warranties, and confers no rights. > > > -------------------- > | Thread-Topic: w32time Event ID 29 > | thread-index: Acb3tYV49adkpH1wTfCHkvdzVeT94w== > | X-WBNR-Posting-Host: 207.46.199.61 > | From: =?Utf-8?B?UnVzc2VsbDM=?= <Russell3(a)discussions.microsoft.com> > | References: <93730183-3302-4EBE-84AF-E908F5FFD484(a)microsoft.com> > <Nbuyyen9GHA.1472(a)TK2MSFTNGXA01.phx.gbl> > <28C42DFB-3915-452F-9864-438701077F35(a)microsoft.com> > <iTYR21z9GHA.6064(a)TK2MSFTNGXA01.phx.gbl> > | Subject: RE: w32time Event ID 29 > | Date: Tue, 24 Oct 2006 14:44:02 -0700 > | Lines: 314 > | Message-ID: <80B9CF13-9A5B-404A-8890-6EF755CFE8DB(a)microsoft.com> > | MIME-Version: 1.0 > | Content-Type: text/plain; > | charset="Utf-8" > | Content-Transfer-Encoding: 7bit > | X-Newsreader: Microsoft CDO for Windows 2000 > | Content-Class: urn:content-classes:message > | Importance: normal > | Priority: normal > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830 > | Newsgroups: microsoft.public.windows.server.sbs > | Path: TK2MSFTNGXA01.phx.gbl > | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:307678 > | NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250 > | X-Tomcat-NG: microsoft.public.windows.server.sbs > | > | Hello Crina > | I tried other time sources - no change. > |
From: Russell3 on 26 Oct 2006 23:12 Hello #3 Chance I have a log file from the w32time logging service. Can I send it to you for a quick review. under 100kb. failure show quickly. Russell "chace zhang" wrote: > Hi, > > Thank you for your update. >
From: Russell3 on 26 Oct 2006 23:38 Chance: I past a log file here. Your comments will be appreciated. Russell 148222 03:30:39.5312500s - ---------- Log File Opened ----------------- 148222 03:30:39.5312500s - Entered W32TmServiceMain 148222 03:30:39.5312500s - CurSpc:15625000ns BaseSpc:15625000ns SyncToCmos:Yes 148222 03:30:39.5312500s - PerfFreq:3579545c/s 148222 03:30:39.5312500s - Time zone OK. 148222 03:30:39.5312500s - ReadConfig: Found provider 'NtpClient': 148222 03:30:39.5312500s - ReadConfig: 'Enabled'=0x00000001 148222 03:30:39.5312500s - ReadConfig: 'DllName'='C:\WINDOWS\system32\w32time.dll' 148222 03:30:39.5312500s - ReadConfig: 'InputProvider'=0x00000001 148222 03:30:39.5312500s - ReadConfig: Found provider 'NtpServer': 148222 03:30:39.5312500s - ReadConfig: 'Enabled'=0x00000001 148222 03:30:39.5312500s - ReadConfig: 'DllName'='C:\WINDOWS\system32\w32time.dll' 148222 03:30:39.5312500s - ReadConfig: 'InputProvider'=0x00000000 148222 03:30:39.5312500s - ReadConfig (policy): Found provider 'NtpClient': 148222 03:30:39.5312500s - ReadConfig (policy): 'Enabled'=0x00000001 148222 03:30:39.5312500s - ReadConfig: 'PhaseCorrectRate'=0x00000007 148222 03:30:39.5312500s - ReadConfig: 'UpdateInterval'=0x00000064 148222 03:30:39.5312500s - ReadConfig: 'FrequencyCorrectRate'=0x00000004 148222 03:30:39.5312500s - ReadConfig: 'PollAdjustFactor'=0x00000005 148222 03:30:39.5312500s - ReadConfig: 'LargePhaseOffset'=0x02FAF080 148222 03:30:39.5312500s - ReadConfig: 'SpikeWatchPeriod'=0x00000384 148222 03:30:39.5312500s - ReadConfig: 'HoldPeriod'=0x00000005 148222 03:30:39.5312500s - ReadConfig: 'MinPollInterval'=0x00000006 148222 03:30:39.5312500s - ReadConfig: 'MaxPollInterval'=0x0000000A 148222 03:30:39.5312500s - ReadConfig: 'AnnounceFlags'=0x00000005 148222 03:30:39.5312500s - ReadConfig: 'LocalClockDispersion'=0x0000000A 148222 03:30:39.5312500s - ReadConfig: 'MaxNegPhaseCorrection'=0x00000E10 148222 03:30:39.5312500s - ReadConfig: 'MaxPosPhaseCorrection'=0x00000E10 148222 03:30:39.5312500s - ReadConfig: 'EventLogFlags'=0x00000002 148222 03:30:39.5312500s - ReadConfig: 'MaxAllowedPhaseOffset'=0x0000012C 148222 03:30:39.5312500s - DomainHierarchy: LSA role change notification. Redetecting. 148222 03:30:39.5312500s - DomainHierarchy: we are now the domain root. Should be advertised as reliable 148222 03:30:39.5312500s - ClockDisciplineThread: Starting:148222 03:30:39.5312500s - LI:0 S:1 RDl:0 RDs:100000000 TSF:0x0 148222 03:30:39.5312500s - ClockDispln: we're a reliable time service with no time source: LS: 0, TN: 864000000000, WAIT: 86400000 148222 03:30:39.5312500s - Starting Providers. 148222 03:30:39.5312500s - Starting 'NtpClient', dll:'C:\WINDOWS\system32\w32time.dll' 148222 03:30:39.5312500s - NtpTimeProvOpen("NtpClient") called. 148222 03:30:39.5312500s - sysPrecision=-6, systmeClockResolution=156250 148222 03:30:39.5312500s - NtpProvider: Created 2 sockets (1 listen-only): 10.0.0.1:123, (127.0.0.1:123) 148222 03:30:39.5312500s - PeerPollingThread: waiting forever 148222 03:30:39.5312500s - ReadConfig: 'AllowNonstandardModeCombinations'=0x00000001 148222 03:30:39.5312500s - ReadConfig: 'CompatibilityFlags'=0x80000000 148222 03:30:39.5312500s - ReadConfig: 'SpecialPollInterval'=0x00000E10 148222 03:30:39.5312500s - ReadConfig: 'ResolvePeerBackoffMinutes'=0x0000000F 148222 03:30:39.5312500s - ReadConfig: 'ResolvePeerBackoffMaxTimes'=0x00000007 148222 03:30:39.5312500s - ReadConfig: 'EventLogFlags'=0x00000000 148222 03:30:39.5312500s - ReadConfig: 'LargeSampleSkew'=0x00000003 148222 03:30:39.5312500s - ReadConfig: 'ManualPeerList'='server' 148222 03:30:39.5312500s - PeerPollingThread: waiting 0.000s 148222 03:30:39.5312500s - NtpClient started. 148222 03:30:39.5312500s - Starting 'NtpServer', dll:'C:\WINDOWS\system32\w32time.dll' 148222 03:30:39.5312500s - NtpTimeProvOpen("NtpServer") called. 148222 03:30:39.5312500s - ReadConfig: 'AllowNonstandardModeCombinations'=0x00000001 148222 03:30:39.5312500s - PeerPollingThread: PeerListUpdated 148222 03:30:39.5312500s - Resolving server 148222 03:30:39.5312500s - Created reachability group: ( 148222 03:30:39.5312500s - 10.0.0.1:123, 148222 03:30:39.5312500s - ) 148222 03:30:39.5312500s - PeerPollingThread: waiting 0.000s 148222 03:30:39.5312500s - PeerPollingThread: waiting 0.000s 148222 03:30:39.5312500s - NtpServer started. 148222 03:30:39.5312500s - Successfully started 2 providers. 148222 03:30:39.5312500s - W32TmServiceMain: waiting i16.000s (64.000s) 148222 03:30:39.5312500s - PeerPollingThread: PeerListUpdated 148222 03:30:39.5312500s - Reachability: Attempting to contact peer server (ntp.m|0x0|10.0.0.1:123->10.0.0.1:123). 148222 03:30:39.5312500s - Polling peer server (ntp.m|0x0|10.0.0.1:123->10.0.0.1:123) 148222 03:30:39.5312500s - Sending packet to server (ntp.m|0x0|10.0.0.1:123->10.0.0.1:123) in Win2K detect mode, stage 1. 148222 03:30:39.5312500s - Peer poll: Max:64.0000000s Cur:00.0000000s 148222 03:30:39.5312500s - PeerPollingThread: waiting 64.000s 148222 03:30:39.5312500s - W32TmServiceMain: waiting i16.000s (64.000s) 148222 03:30:39.5312500s - ListeningThread -- DataAvailEvent set for socket 0 (10.0.0.1:123) 148222 03:30:39.5312500s - ListeningThread -- response heard from 10.0.0.1:123 148222 03:30:39.5312500s - /-- NTP Packet: 148222 03:30:39.5312500s - | LeapIndicator: 0 - no warning; VersionNumber: 3; Mode: 1 - SymmetricActive; LiVnMode: 0x19 148222 03:30:39.5312500s - | Stratum: 1 - primary reference (syncd by radio clock) 148222 03:30:39.5312500s - | Poll Interval: 15 - out of valid range; Precision: -6 - 15.625ms per tick 148222 03:30:39.5312500s - | RootDelay: 0x0000.0000s - unspecified; RootDispersion: 0x000A.0400s - 10.0156s 148222 03:30:39.5312500s - | ReferenceClockIdentifier: 0x4C4F434C - source name: "LOCL" 148222 03:30:39.5312500s - | ReferenceTimestamp: 0xC8EBFBDF88000000148222 03:30:39.5312500s - - 12806393439531250000ns - 148222 03:30:39.5312500s 148222 03:30:39.5312500s - | OriginateTimestamp: 0x0000000000000000 - unspecified 148222 03:30:39.5312500s - | ReceiveTimestamp: 0x0000000000000000 - unspecified 148222 03:30:39.5312500s - | TransmitTimestamp: 0xC8EBFBDF88000000148222 03:30:39.5312500s - - 12806393439531250000ns - 148222 03:30:39.5312500s 148222 03:30:39.5312500s - >-- Non-packet info: 148222 03:30:39.5312500s - | DestinationTimestamp: 148222 03:30
From: chace zhang on 27 Oct 2006 06:12 Hi, Thank you for your update. I have checked your w32time.log file, and I found following info "Sending packet to server (ntp.m|0x0|10.0.0.1:123->10.0.0.1:123)". It seems you didn't select the correct time source. So I suggest that you run the following commend from SBS Server:
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 Prev: IIS Problems Next: Upgrade SBS 2000 to SBS 2003 R2 has errors |