If your device can successfully execute the Allxon RMM (INB) service but cannot connect to Allxon SwiftDR (OOB), this situation is often due to the current network environment being unable to establish a proper connection with the NTP protocol. Please utilize the testing tool provided by Allxon to verify the functionality of the NTP communication protocol.
Requirement :
> Support OS : Windows
> Application Name : ntpclientWin32.exe*
* Please contact Allxon for the testing application
Execute "ntpclientWin32.exe", then check the results as below.
- NTP Protocol connected :
C:\Work\Source\ntpclientWin32\Debug>ntpclientWin32.exe
Configuration:
-c probe_count 1
-d (debug) 1
-g goodness 0
-h hostname time.google.com
-i interval 5
-l live 0
-p local_port 0
-s set_clock 0
Listening...
Sending ...
packet of length 48 received
Source: INET Port 123 host 216.239.35.8
LI=0 VN=3 Mode=4 Stratum=1 Poll=4 Precision=-20
Delay=0.0 Dispersion=76.3 Refid=71.79.79.71
Reference 3882241243.0227714925
Originate 3882241243.4276486040
Receive 3882241243.0227714926
Transmit 3882241243.0227714928
Our recv 3882241244.0034329673
Total elapsed: 12296.00
Server stall: 0.00
Slop: 12296.00
Skew: -948825.99
Frequency: 0
day second elapsed stall skew dispersion freq
44933 30044.007 12296.0 0.0 -948826.0 76.3 0 - NTP Protocol blocked :
C:\Work\Source\ntpclientWin32\Debug>ntpclientWin32.exe
Configuration:
-c probe_count 1
-d (debug) 1
-g goodness 0
-h hostname time.google.com
-i interval 5
-l live 0
-p local_port 0
-s set_clock 0
Listening...
Sending ...
read timeout
Note :
For further assistance, kindly reach out to the designated person in charge of your Management Information System (MIS).