I have a program (WorldTime) which is running on my W98 PC as a network time
server....
(I'm setting this up as an emergency method to set the time/date on the DU
system if we lose
our internet connection for what ever reason). I'm currently on 3.2c, which
is why this is
even an issue since I can't directly use the date command (y2k issue) or
rather can't use the
date command on one shot. Once we upgrade to a higher release, this won't be
an issue
since we will be able to use the date command manually.
If I run rdate -v I get:
# rdate -v
alpha.slackinc.com: Tue Feb 27 17:21:29 2001
10.10.200.3: Tue Feb 27 17:21:33 2001
Network time is Tue Feb 27 17:21:31 2001
If I run ntp 10.10.200.3 I get:
# ntp 10.10.200.3
recvfrom: Connection refused
# ntp x.x.x.x
x.x.x.x: delay:0.026866 offset:-1.176303 Tue Feb 27 17:22:25 2001
#
I did the second one to the x.x.x.x (a known working ntp server) to see if
the ntp command worked.
What/why would ntp get a refusal, but the rdate gets a response?
Thanks
George
George Gallen
Senior Programmer/Analyst
Accounting/Data Division
ggallen_at_slackinc.com
ph:856.848.1000 Ext 220
SLACK Incorporated - An innovative information, education and management
company
http://www.slackinc.com
Received on Tue Feb 27 2001 - 22:29:56 NZDT