[SunHELP] NTP Problems

Hello gurus,

My company just bought me a Sun Blade 150 and I'm configuring NTP under
Solaris 8. I copied the /etc/inet/ntp.client file to /etc/inet/ntp.conf and
added the following information:

# Time server that this client is synching to.
server 172.17.5.202 prefer
# Drift file is necessary, touch the file.
driftfile /etc/inet/ntp.drift

When I go to start the ntp daemon, via "/etc/rc2.d/S74xntpd start", I get
the following messages in my syslog:

Jan 23 14:17:14 ruth ntpdate[22285]: [ID 398266 daemon.notice] waiting 30
seconds before trying again
Jan 23 14:17:44 ruth ntpdate[22285]: [ID 398266 daemon.notice] waiting 60
seconds before trying again
Jan 23 14:18:10 ruth xntpd[22320]: [ID 702911 daemon.notice] xntpd 3-5.93e
Mon Sep 20 15:47:11 PDT 1999 (1)
Jan 23 14:18:11 ruth xntpd[22320]: [ID 301315 daemon.notice] tickadj = 5,
tick = 10000, tvu_maxslew = 495, est. hz = 100
Jan 23 14:18:11 ruth xntpd[22320]: [ID 798731 daemon.notice] using kernel
phase-lock loop 0041

Stopped and restarted the process:

Jan 23 14:19:17 ruth xntpd[22320]: [ID 866926 daemon.notice] xntpd exiting
on signal 15
Jan 23 14:19:35 ruth ntpdate[22380]: [ID 398266 daemon.notice] waiting 30
seconds before trying again
Jan 23 14:20:05 ruth ntpdate[22380]: [ID 398266 daemon.notice] waiting 60
seconds before trying again
Jan 23 14:21:05 ruth ntpdate[22380]: [ID 398266 daemon.notice] waiting 120
seconds before trying again
Jan 23 14:23:05 ruth ntpdate[22380]: [ID 398266 daemon.notice] waiting 240
seconds before trying again
Jan 23 14:27:05 ruth ntpdate[22380]: [ID 398266 daemon.notice] waiting 300
seconds before trying again

On the ntp server side I see the following:

# snoop |grep -i ntp
ruth --> eck	NTP client	(Thu Jan 23 14:23:05 2003)
eck --> ruth	NTP server	(Thu Jan 23 14:26:32 2003)
ruth --> eck	NTP client	(Thu Jan 23 14:23:05 2003)
eck --> ruth	NTP server	(Thu Jan 23 14:26:32 2003)
ruth --> eck	NTP client	(Thu Jan 23 14:23:05 2003)
eck --> ruth	NTP server	(Thu Jan 23 14:26:32 2003)

So the way I'm looking at all this is the NTP server sees the request, but
the NTP client for some reason is not seeing the response. Has anyone had
this problem before and more importantly does anyone know how to fix the
problem?

TIA.

Matthew Simoncini
Accenture / Boston Scientific