tcp/ip for time server

"Wallgames.com" <rpcarrollNOSPAMPLEASE@NOSPAMPLEASEwallgames.com >
wrote:

>It has been my experience that NISTIME doesn't work with all time servers.

Well that's reassuring, I was beginning to wonder whether there were
in fact two different protocols.

>Experimentation will find a suitable time server, at which point I set it
>and forget it -

I'll stay where I am then. The server is stand-alone so time isn't
that critical.

>unless it is a 3.12/3.2 Netware server which doesn't seem to
>understand DST. I adjust the load setting on those twice a year.

I think that the time adjustment on 3.12 assumed that the BIOS clock
was correct and did daylight saving relative to the BIOS. This was
simply to save effort in re-setting the BIOS clock settings twice a
year.

4.x seems to assume that whatever time it is given is UTC and does its
ajustments from there.

I may have explained my theory a bit better in an earlier posting.


TonyL


>
>"Anthony Lees" <intothebin@hotmail.com> wrote in message
>news:4a8d2d4c.10245859@support-forums.novell.com...
>>A further question on this:
>>
>> Using the server 192.43.244.18 works fine. However as the server
>> appears to be somewhere around Denver and I am UK based I thought I
>> would try my ISP's time server which I use to keep my laptop time
>> correct - 212.23.8.6. NISTIME doesn't work with this server.
>>
>> I looked up a set of servers on http://support.microsoft.com/kb/262680
>> and tried a couple of the British Isles ones (several don't work).
>>
>> Another one (Manchester University) responds with:
>>
>> MM_SERVER:load nistime -a130.88.202.49
>> Loading module NISTIME.NLM
>> Netware Server Clock Adjusting via Internet NIST Time Center
>> Version 1.00a 6 July 1998
>> (C) Copyright 1998 Vahal. All Rights Reserved
>> Server address override 130.88.202.49
>> Trying to connect to the NIST time server
>> Receiving time message...
>> TIME MESSAGE:Thu Aug 20 12:31:18 2009
>>
>> Time server reports HEALTH value not zero (1701147206), not adjusting
>> time
>> If problems persists, try different time server
>> This server time (seconds) 1250767880
>> NIST time (seconds) 2028354446
>> Time difference is -777586566
>> Time was NOT adjusted, but would be to: 134-4-11 08:47:26 LOCAL time
>>
>> My current settings for time are:
>> Time zone string: "GMT0BST"
>> DST status: ON
>> DST start: Sunday, 28 March 2010 2:00:00 am GMT
>> DST end: Sunday, 25 October 2009 2:00:00 am BST
>> Time synchronization is active.
>> Time is synchronized to the network.
>> Thursday, 20 August 2009 11:32:31 am UTC
>> Thursday, 20 August 2009 12:32:31 pm BST
>>
>> and the BST time is absolutely correct.
>>
>> Clearly I am misunderstanding something about how all this works and
>> also don't understand why the time is correct to the second when
>> getting it from so far away.
>>
>>
>>
>> --
>> TonyL
>
>