On Thu, 9 Sep 1999 02:12:35 -0700, Ole Juul wrote:
> Gregor J Jones wrote:
>> Works fine here in a dos machine here. I have ntime
>> pointed to ns.bu.edu, which is the university timeserver
> Hmm, interesting. I get a timed out message everytime on
> that one. But it was really helpful to know that the
> program works. This is one step closer.
Probably that machine is a local machine, so it's only
accessible from within bu.edu network; or the route just
too far from your ISP. Interesting part though, "ns"
usually stands for "Name Server" (a.k.a DNS server).
>> But, you really want a timeserver nearby, to avoid
>> transmission delays.
In the other post, Howard E. also said that he get
correct time server response from his ISP's name server.
A coincident? I don't think so... <g> Perhaps it's an
usual practice to put time server function in the same
machine with name server? (usually name server oficially
named ns, ns1, ns2, ns<x>, or just listed as IP number).
But again, this might not true for all ISPs... Well,
worth a try I guess... :)
--Eko
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
