Sincronizar la hora de un W2kServer por NTP
No siempre se puede elegir. Hay veces que toca llevar algun Windows, y ese dia llega tarde o temprano.
En el caso que te toque sincronizar la hora por NTP de un Windows 2000 Server, aqui tienes la manera de MS para hacerlo. O sea, “ponte a tocar el registro porque no nos dio la gana hacerlo facil si no esta unido a un controlador de dominio”
Historias para no dormir del dia a dia.
Configuring Windows Time service to use an external time source
Administrators can configure the Windows Time service on the PDC operations master at the root of the forest to recognize an external Simple Network Time Protocol (SNTP) time server as authoritative. For example, you can use the Microsoft time server (time.windows.com) as the external SNTP time server. To configure Windows Time service to use an external SNTP time server, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Follow these steps to change the server type to NTP:
- Locate and then click the following registry subkey:
HKEY LOCAL MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
- In the right pane, right-click TYPE, and then click Modify.
- In Edit Value, type NTP in the Value data box, and then click OK.
- Locate and then click the following registry subkey:
- Follow these steps to configure the server as a reliable time source:
- In the right pane, right-click ReliableTimeSource, and then click Modify.
- In Edit DWORD Value, type 1 in the Value data box, and then click OK.
- Follow these steps to configure the server LocalNTP to 0:
- In the right pane, right-click LocalNTP, and then click Modify.
- In Edit DWORD Value, type 0 in the Value data box, and then click OK.
- Follow these steps to specify the time sources:
- In the right pane, right-click NtpServer, and then click Modify.
- In Edit Value, type Peers in the Value data box, and then click OK.Note Peers is a placeholder for a space-delimited list of peers from which your computer obtains time stamps. Each DNS name that is listed must be unique.
- For Windows 2000 Service Pack 4 only, set the time correction setting. To do this, follow these steps:
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
- In the right pane, right-click MaxAllowedClockErrInSecs, and then click Modify.
- In Edit DWORD Value, type TimeInSeconds in the Value data box, and then click OK.Note TimeInSeconds is a placeholder for the max number of seconds difference between the local clock and the time received from the NTP server in order to be considered a valid new time.
- Locate and then click the following registry subkey:
- Follow these steps to set the poll interval:
- Locate and then click the following registry subkey:
HKEY LOCAL MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
- In the right pane, right-click Period, and then click Modify.
- In Edit DWORD Value, type 24 in the Value data box, and then click OK.
- Locate and then click the following registry subkey:
- On the File menu, click Exit to exit Registry Editor.
- At the command prompt, type the following command to restart the Windows Time service, and then press ENTER:
net stop w32time && net start w32time
- Run the following command on all the computers other than the Time Server to reset the local computer’s time against the Time Server:
w32tm -s
By default, SNTP uses User Datagram Protocol (UDP) port 123. If this port is not open to the Internet, you cannot synchronize your server to Internet SNTP servers. A computer that is configured to be a reliable time source is identified as the root of the Windows Time service. The root of the Time service is the authoritative server for the domain and typically is configured to retrieve time from an external NTP server or a hardware device. A time server can be configured as a reliable time source to optimize how time is transferred throughout the domain hierarchy. If a domain controller is configured to be a reliable time source, the Net Logon service announces that domain controller as a reliable time source when it logs on to the network. When other domain controllers look for a time source to synchronize with, they choose a reliable source first if one is available.
The HKEY LOCAL MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Period registry key controls how frequently the Windows Time service synchronizes. If a value is specified, it must be one of the special values in the following list:
- 65531, “DailySpecialSkew” - Sets synchronization to one time every 45 minutes until successful one time, then one time every day.
- 65532, “SpecialSkew” - Sets synchronization to one time every 45 minutes until successful three times, then one time every eight hours. This is the default setting.
- 65533, “Weekly” - Sets synchronization to one time every seven days.
- 65534, “Tridaily” - Sets synchronization to one time every three days.
- 65535, “BiDaily” - Sets synchronization to one time every two days.
- 0 - For NT5DS, the synchronization is one time every 45 minutes until successful three times, then one time every eight hours. For NTP, the synchronization is one time every 8 hours.
- freq - freq stands for the number of times per day you want Windows Time service to synchronize. If want to use a value other than any one of those specified earlier, you must use this option.
If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.
Comments
No comments yet.
Leave a comment