NTP Sync 10.1.6 PA-220

[CBrookes]

Hi all,

I'm getting this NTP status message.

I'm quite sure it did initially sync but then reverts to this state.

What exactly does "rejected" mean? The NTP server was reachable but has it been knocked back for some reason.

NTP state:

NTP not synched, using local clock

NTP server: xxxx

status: rejected

reachable: yes

authentication-type: none

Thanks,

Clinton

[OtakarKlier]

Hello,

Sounds like you ate using authenticated NTP? If yes, I would check with the NTP server owner to make sure you have the correct credentials.

Regards,

[CBrookes]

Not authenticated no, just a windows domain controller.

[OtakarKlier]

And on the PAN none of the authentication for NTP is configured?

[CBrookes]

Correct

[OtakarKlier]

Interesting. Does the traffic out of the management port flow back through the PAN to get to the NTP server? I'm really out of thoughts. Perhaps a support case.

[CBrookes]

I got it syncing eventually with just one host.

Then all of sudden it syncs. Syncs many times for some time. Then goes back to being rejected.

NTP state:
    NTP not synched, using local clock
    NTP server: xxx
        status: rejected
        reachable: no
        authentication-type: none

admin@xxx> show ntp

NTP state:
    NTP not synched, using local clock
    NTP server: xxx
        status: rejected
        reachable: yes
        authentication-type: none

admin@xxx> show ntp

NTP state:
    NTP not synched, using local clock
    NTP server: xxx
        status: rejected
        reachable: yes
        authentication-type: none

admin@xxx> show ntp

NTP state:
    NTP synched to xxx
    NTP server: xxx
        status: synched
        reachable: yes
        authentication-type: none

admin@xxx> show ntp

NTP state:
    NTP synched to xxx
    NTP server: xxx
        status: synched
        reachable: yes
        authentication-type: none

admin@xxx> show ntp

NTP state:
    NTP synched to xxx
    NTP server: xxx
        status: synched
        reachable: yes
        authentication-type: none

[kandaspr]

Hi Brooks,

Could you please share the fix you applied to make it as "synched". I also have same issue.

Thanks

[kandaspr]

This issue is fixed after decreasing the LocalClockDispersion value on the Windows NTP server

1. Navigate to the following Windows registry key:
   SYSTEM\CurrentControlSet\Services\W32Time\Config\LocalClockDispersion
    
2. Set the value to 0.
3. Restart the W32time service on Windows with the following command:
   net stop w32time
   net start w32time