Administrators must ensure accurate time across their network by addressing NTP (Network Time Protocol) issues. You DO NOT want to see what havoc Kerberos will bring to infrastructure SSO (Single Sign-On) availability if the time is not sync’ed across the infrastructure in TOTAL ALIGNMENT — just, trust me!

Here are some things to look into when NTP is not working properly in the infrastructure:

Time discrepancies. Recognize or detect inconsistencies in timekeeping across network devices or workstations and synchronization errors across time zones.

Checking Time and Date Settings. Gaining access to date and time settings on Windows servers or clients and verifying they use NTP time servers.

Test an NTP Server Connection. For quick testing of connectivity between an NTP server and client PCs, command-line programs like “ping” or “telnet” may be used. Also be sure to verify if any firewalls block NTP (UDP port 123) traffic.

Check Service Status of NTP. Verify Windows Time (W32Time). If necessary, restart “services.msc”, the Windows Time service.

Review Time Source. Confirm which time source your system is using; for instance, whether a local server or authoritative time source are being employed.

Force Synchronization. Use PowerShell/Command Prompt with “w32tm/resync”, this command will force synchronization to your configured NTP services.

Verifying Domain Hierarchy. When working within a domain environment, be sure to verify that all domain controllers and members have their time synchronized to reliable external sources. All other members should also synchronize up with DCs.

Consider external time sources. If internal NTP servers are unreliable, configure systems so they sync up with reliable external NTP providers like pool.ntp.org for seamless clock synchronization.

Monitor Synchronization. Utilize monitoring software and logs to monitor the time synchronization between servers and devices.

Investigate Clock Drift in Virtualized Environments. Take time to investigate clock drift in virtualized environments and make adjustments as necessary.

Restart Systems or Services. After making modifications, reboot or restart services as soon as possible in order to effectively implement them.