Shulou(Shulou.com)05/31 Report--

Domain control server w32time error how to do, I believe that many inexperienced people do not know what to do, so this paper summarizes the causes of the problem and solutions, through this article I hope you can solve this problem.

Description: W32Time reports its own status as "out of sync" and stops providing time for clients that make requests.

Error 29: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 15 minutes. NtpClient has no source of accurate time. The time service provider NtpClient is configured to obtain time from one or more time sources, but none of these sources are currently accessible. No attempt to contact the time source will be made for 15 minutes. NtpClient has no exact time source.

Note: event ID 29 may also occur on Windows XP-based computers.

Possible cause: there is a code error in Release Candidate 1 (RC1) version of Windows Server 2003. However, network congestion, overloaded CPU or overloaded network, and low accuracy of synchronous time sources all make the problem more serious. This issue has been resolved in post-RC1 versions of Windows Server 2003.

To workaround this issue, configure the following registry settings on any Windows Server 2003 RC1-based time server or domain controller to prevent specific computers from experiencing this problem:

Start the Registry Editor.

Locate and click the following registry key, and then add the following registry value: Microsoft recommends that you apply this registry setting on all Windows Server 2003 RC1-based servers hosting this time service. Note that computers that use this configuration will use unverified time.

HKEY_LOCAL_MACHINE\ System\ CurrentControlSet\ Services\ W32time\ Config\

Numeric name: MinPollInterval

Numeric type: Reg_DWord

Numerical data: 6

HKEY_LOCAL_MACHINE\ System\ CurrentControlSet\ Services\ W32time\ Config\

Numeric name: MaxPollInterval

Numeric type: Reg_DWord

Numerical data: 14

HKEY_LOCAL_MACHINE\ System\ CurrentControlSet\ Services\ W32time\ Parameters\

Numeric name: NtpServer

Numeric type: Reg_SZ

Numeric data: the root time server you are using, 0x1

HKEY_LOCAL_MACHINE\ System\ CurrentControlSet\ Services\ W32time\ Parameters\

Numeric name: Type

Numeric type: Reg_SZ

Numeric data: NTP

HKEY_LOCAL_MACHINE\ System\ CurrentControlSet\ Services\ W32time\ TimeProviders\ NtpClient\

Numeric name: SpecialPollInterval

Numeric type: Reg_DWord

Numerical data: 300

If the "root time server, 0x1" syntax of the NtpServer registry value is confusing, use the primary domain controller (PDC) of the forest root domain as the root time service.

Restart the time service. To do this, type the following command at the NT CMD prompt:

C:\ > net stop w32time & net start w32time

C:\ > w32tm / resync manual time synchronization

Add: if you want to synchronize with external time, you need to make the following adjustments:

HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\ W32Time\ TimeProviders\ NtpServer

"Enabled" Edit DWORD value type 1

HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\ W32Time\ Parameters\ Type

"Type" edit numeric data type NTP

# external time source settings

HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\ W32Time\ Parametrs\ NtpServer

"NtpServer", "numerical data" type IP or domain name to be followed by 0X1

# polling interval

HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\ W32Time\ TimeProviders\ NtpClient\

"SpecialPollInterval"Numeric data" Type the number of seconds (number) the recommended value is 900 (decimal). This value configures the time server to poll every 15 minutes.

# # configuring time Calibration Settings

HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\ W32Time\ Config\

"MaxPosPhaseCorrection"Numeric data" Type TimeInSeconds

Note: TimeInSeconds is a placeholder and should be replaced with an appropriate value, such as 1 hour (3600) or 30 minutes (1800). The value you select will vary depending on the polling interval, network condition, and external time source.

If you do not configure or use an external time source for this computer, you can choose to disable NtpClient.

Solution: stop the ntpclient service HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\ W32Time\ TimeProviders\ NtpClient

Enabled, change the value to 0, and then net stop w32time & & net start w32time

Other relevant prompts:

Event ID: 50

Source: W32time

Type: warning

The time service detected a time difference greater than 5000 milliseconds for a duration of 900s. The time difference may be caused by synchronization with inaccurate time sources or poor network conditions. The time service is no longer synchronized, nor can it provide time for other clients or update the system clock. After receiving a valid timestamp from a time service provider, the time service corrects itself. In the default domain level, when a Microsoft Windows Server 2003-based subdomain controller attempts to synchronize time, you may receive the following event message.

Event ID: 38

Source: W32time

Type: information

The time provider NtpClient cannot access, or is currently receiving invalid time data from yourpdc.forestroot.com (ntp.d | 65.53.232.135ntp.d 123-> 65.53.250.22purl 123).

Event ID: 47

Source: W32time

Type: warning

Time provider NtpClient: no valid response was received from the manually configured peer yourpdc.forestroot.com after 8 attempts to contact it. This peer will no longer be used as a time source, and NtpClient will try to discover a new peer with this DNS name.

After reading the above, do you know what to do if a w32time error occurs on the domain control server? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.