> You don't say which version of Solaris, but the config files should
be the same.
> However, NTP is *NOT* designed to be tested like that. It does *NOT*
expect that
> the clock will be pulled hither and thither, but only to follow small
changes.
> If you start jerking the clock about the results are at best
unpredictable.
>
> > Can someone provide what the basic ntp.conf file should look like
for
> > Solaris1 ..
>
> server 127.127.1.0
> fudge 127.127.1.0 stratum 10
> driftfile /etc/inet/ntp.driftfile
>
> > .. and for the other Solaris machines (Solaris2, 3, and 4)?
>
> server Solaris1
> driftfile /etc/inet/ntp.driftfile
>
> If you want to add "restrict" statements you can do that later.
>
> The startup (whether using /etc/init.d/xntpd on earlier versions or
smf on 10)
> should run ntpdate automatically, so you don't have to, and on the
clients the
> ntp daemon itself will not be started start until ntpdate completes,
which
> requires the server has locally synchronized so that ntpdate on the
client can
> get the time from it, which takes about 5 or 6 minutes. Use "ps -ef |
grep ntp"
> to check what is running on each system, and "ntpq -p" (see "man
ntpq" under the
> "peers" entry for the detail) to check things are working, and trust
the output.

John,

Thanks.

All machines are Solaris 9 SPARC.

I tried exactly those config files you described above, but if I:

- Start xntpd on Solaris1, then
- Run: ntpdate solaris1 from one of the other Solaris systems

I am getting an error:

"No suitable server for synchronization found"

All machines are on the same network, and there are no firewalls, so I
don't know what the problem is.

Thanks,
Jim