Check if NTP server is accessible
Neat devices require access to an NTP server, with time.neat.no being the default unless specified otherwise. For Cisco Meraki setups utilizing DHCP Option 42 for NTP, refer to NTP Issue with Cisco Meraki Network
When troubleshooting NTP server connectivity, please try the following steps:
During Installation (OOB) check Network settings to display the NTP server field for the device.
- Symptom: time.neat.no is highlighted in orange
- Connect a laptop to the same subnet as the Neat device to confirm if time.neat.no can reached. For example, if you want to check if the subnet allows connections to time.neat.no NTP server you can do the following:
- On Macbooks, you can open TERMINAL and type: sntp -d time.neat.no
- On Windows, you can open a command prompt as Administrator and type: w32tm /stripchart /computer:time.neat.no /dataonly /samples:5If you have a different NTP server you are using (e.g. something that Option 42 has provided), then replace the ‘time.neat.no’ in the above commands with either the FQDN or IP address of that NTP server.
- Connect a laptop to the same subnet as the Neat device to confirm if time.neat.no can reached. For example, if you want to check if the subnet allows connections to time.neat.no NTP server you can do the following:
- Symptom: NTP server is missing
- Check that the DHCP Option 42 is correctly configured with a valid NTP server. For Cisco Meraki see NTP Issue with Cisco Meraki Network
Finally, Factory reset and connect the devices to a mobile hotspot (typically a fairly open network) to confirm whether the device can default to time.neat.no.