---
title: "Checking status of NTP in Pathfinder Core PRO"
slug: "checking-status-of-ntp-in-pathfinder-core-pro"
updated: 2024-12-30T10:37:55Z
published: 2024-12-30T10:37:55Z
canonical: "docs.telosalliance.com/checking-status-of-ntp-in-pathfinder-core-pro"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.telosalliance.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Checking status of NTP in Pathfinder Core PRO

## Scope

Checking the status of NTP in Pathfinder Core PRO requires SSH using the root credentials. Root credentials are **not** general user knowledge and should not be shared. If you need assistance with this, please contact support.

## Instructions

The queries shown below are based on the default Time configuration in Pathfinder.

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/1964535f-4ecd-4bab-98dd-a809e07cf354-image.png?sv=2026-02-06&spr=https&st=2026-11-07T03%3A34%3A19Z&se=2026-11-07T04%3A34%3A19Z&sr=c&sp=r&sig=s7sAi3Fcy3f0C%2F%2BdoTznDheO04NhQrf%2Bj2cN7GO3g0E%3D)

Using PuTTy or other terminal program make an SSH connection to Pathfinder Core PRO (standard SSH port 22 is used)

There are two commands that are helpful

```plaintext
# ntpq -c rv
```

A leap code 0 (leap_none shown by the arrow) is the normal synchronized state. A leap code 3 (leap_alarm) means never sync'd. If this is the case, check DNS or other network route to the NTP server.

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/f3757acc-cbd7-42ee-8baf-3324986b925c-image.png?sv=2026-02-06&spr=https&st=2026-11-07T03%3A34%3A19Z&se=2026-11-07T04%3A34%3A19Z&sr=c&sp=r&sig=s7sAi3Fcy3f0C%2F%2BdoTznDheO04NhQrf%2Bj2cN7GO3g0E%3D)

```plaintext
# nptq -pn
OR
# ntpq -p
```

Returns some health stats of the servers listed in your config.

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/e21b4c67-0ca8-4dcd-a805-b901964efe9b-image.png?sv=2026-02-06&spr=https&st=2026-11-07T03%3A34%3A19Z&se=2026-11-07T04%3A34%3A19Z&sr=c&sp=r&sig=s7sAi3Fcy3f0C%2F%2BdoTznDheO04NhQrf%2Bj2cN7GO3g0E%3D)

## Testing your NTP using a Windows computer

To verify your NTP server you can use the w32tm service in Windows.

Open a command prompt and send the command;

```plaintext
C:\Users\Administrator>w32tm /monitor /computers:192.168.2.82
```

where 192.168.2.82 is the ip address of your NTP server (names may also be used).

If your NTP server is working, you will see something similar to this.

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/cabd2bd7-dce9-4e3f-a167-f7f427e62cdf-image.png?sv=2026-02-06&spr=https&st=2026-11-07T03%3A34%3A19Z&se=2026-11-07T04%3A34%3A19Z&sr=c&sp=r&sig=s7sAi3Fcy3f0C%2F%2BdoTznDheO04NhQrf%2Bj2cN7GO3g0E%3D)

If your response is

```plaintext
NTP: error WSAECONNRESET - no server listening on NTP port
```

then your NTP server is not working.

## Let us know how we can help

If you have further questions on this topic or have ideas about improving this document, please [contact us](https://www.telosalliance.com/support-request).