w32time Event ID 29
|
From: Russell3 on 27 Oct 2006 15:17 Hello Chance Only the top part of your message shows. Your advice is missing. I do not know details of what is placed in the log file, so I am unsure how to interpret the log file. I assure you I have selected a time source. In Regedit key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters is truechimer2.waikato.ac.nz ANyhow can you post the remainder of your message? "chace zhang" wrote: > 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: >
From: chace zhang on 30 Oct 2006 00:44 Hi, Thank you for your update. Sorry for the delayed response, please understand that our newsgroup is an issue based service. 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:
From: wedor on 4 Nov 2006 08:01
I had trouble with atomic clock writing a GPO settng that prevents the Windows time from working, look in that area as well. "Russell3" <Russell3(a)discussions.microsoft.com> wrote in message news:1F50F359-9ACE-4B0C-8CAF-3E80087E8036(a)microsoft.com... > 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 |