Tru64 4.0F system NTP client won't synch to the server

[irt_1]

I have a Tru64 4.0F system (DS20) and have one NTP server (v. 3 run on Solaris) All the HP/UX, Linux and Windows server can synch the time flawlessly to this server.

But for this Tru64 everytime i wanted to ntpdate to this server, always gave this error:
tru64#>ntpdate -v ntpsvr
21 Mar 09:49:51 ntpdate[28619]: ntpdate version=3.4x
21 Mar 09:49:55 ntpdate[28619]: no server suitable for synchronization found

The ntpserver does not have any authentication and the Tru64 can ping to this server.

Anyone have any idea why it can not synch?

Regards,

Iwan Tamimi

[Arch_Muthiah]

Iwan,

It is a NTP version issue with Solaris;
Solaris uses an older version of ntpd, we need "xntpd".

We need NTP version 4, which mainly adds better authentication between NTP servers.

But no supported version 4 on solaris, but there is a unsupported version, you can find from http://www.ntp.org/ and (unsupported) binary packages are at http://sunfreeware.com/ mentioned above.

NTP versions details on Solaris are:

Version 3. For Solaris 8, xntp 3-5.93e (that is NTP protocol version 3, xntp software version 5.93e).

For Solaris 2.6 and 7, it was xntp 3-4y. For Solaris 2.5.1, it was xntp 3-2 (multicasting was not supported) and NTP was available only for Sun Enterprise 10000 systems with package SUNWxntp.

To find the NTP version and Solaris patch level for NTP on your system, type the following (you don't need to be root):

strings /usr/lib/inet/xntpd |grep 'xntpd '
what /usr/lib/inet/xntpd

Archunan

[Ivan Ferreira]

Try using the -b option of the ntpdate command:

ntpdate -bv ntpsvr

I had this error and the -b option was the key.

[irt_1]

Thank you guys for the response.

For the SUN server I don't have the authority to change it. I tried the ntpdate -b ntpsvr also got the same error:
24 Mar 11:26:25 ntpdate[29311]: no server suitable for synchronization found

I tried with other tru65 5.0 F to this ntpsvr, it worked fine. I still don't understand what went wrong.

Regards,

Iwan

[irt_1]

I think I know why. On the NTP server I think that is a config file that say from which sub-net that can connect to this NTP. So even though I can ping even telnet but the NTP was closed for my subnet (and this server using unusual sub-net for our server)

After the admin open it for me the sync run flawlessly.

Thank you anyway,

[Al Licause]

I just worked a case on a linux system in which ntp would not update.....time server showed unreachable despite the fact that tcpdump showed successful polls and responses from the server.

Turned out they had a fudge line referencing the local clock which is a default for a linux configuration, but they removed the line that declares the local clock a server.

So make sure if you have any fudge declarations, you also have a corresponding server line.