"Problems" with ElkRP / M1XEP and time server

CORT

Active Member
Has anyone else noticed that to get the time server function of the M1XEP to work you have to enter a true IP address for the time server and not the URL? I didn't figure this out until I put an email address for error messages and enabled the option to email on time update errors in ElkRP. While ElkRP confirmed time updates with the test button, I received emails that there was a bad URL/IP address for the time server. I am not sure why ElkRP confirmed a successful time update when the M1XEP emailed me that there was a failure. The email was correct though. Changing the time server URL to its IP address solved the problem.

To get the IP address for the time server, go to the Windows command prompt and ping the URL of the time server that you choose from the ntp.org page, i.e. "ping ntp2.stsn.net". This returns the IP address.
 
Make sure the Primary and Secondary DNS Server address in ELKRP's M1XEP setup is set properly or URL addresses will not be translated.
 
Back
Top