[Info-vax] OpenVMS TCP/IP Services NTP using symmetric key authentication

[RobertsonEricW]

The TCPIP$NTP.CONF configuration option authspeed appears to not be required for NTP version 4.2.0. Technically authspeed is not actually a timeout. It is simply the expected amount of elapsed time that it takes to authenticate the reply from the server. This time is then added to the time in the response when setting the system clock in an effort to account for the delay involved in authenticating the NTP servers response message containing the reference time. This option is not required for NTP v4.2.0 because this version of NTP autocalculates it and takes it into account as part of the execution of the NTPD process.

On Wednesday, March 25, 2015 at 5:11:25 PM UTC-4, RobertsonEricW wrote:
> Craig,
> Thanks. I tried the following with the same result:
> $ NTPDATE "-k" SYS$SPECIFIC:[TCPIP$NTP]NTP.KEYS "-a" 75331 "ntp-a.boulder.nist.gov" "ntp-b.nist.gov"
> Looking for host ntp-a.boulder.nist.gov
> host found : ntp-a.boulder.nist.gov
> Looking for host ntp-b.nist.gov
> host found : host-24-56-178-141.beyondbb.com
> 25 Mar 17:07:06 NTPDATE[1206]: no server suitable for synchronization found