Frequently Asked Questions
--------------------------

Q. Running SNTPCLNT behind a firewall, the NLM does not see any time servers

A. When you have a firewall, you must enable traffic on port 123/UDP for
   incomming/outgoing traffic. (The datagramsize is 48Bytes)
    
Q. When I try to load sntpcln4.nlm, I get some errors like:
    unable to find symbol: __get_timezone

A. You must install the new CLIB as recommended by Novell
   Currently they are contained in LIBUPC, but previous versions will do too.


Q. Why have you written two NLM's ?

A. On 3.x servers we only have an interface to set the local clock to a given
   time/date, without possibility to get/set times in the sub-second range.
   So the time calculation/modification is a bit tricky on 3.x servers.
   
   4.x servers on the other hand handle timesynchronisation between each other
   They have a very good interface to correct/query the current time, so we get a 
   much greater accurancy.
   
   For NDS operation it is very important to use the new time-correction API,
   since replication of NDS-changes is based on timestamps.


Q. Is summertime handled correctly ?

A. On 4.x servers the OS handles all local time and summer time handling.
   SNTPCLN4.NLM just works fine together with it.
   
   On 3.x servers, the OS does not handle summer time. So sntpcln3.nlm can handle
   it for you. Just set the corresponding entries in the sntpclnt.cfg file.
   

Q. If my NTP server handles summer time correctly, will I still have to configure
   sntpcln3.nlm via the cfg file ?
   
A. Yes, since all times transmitted from NTP servers are UTC times, the NTP client
   must convert it back into local time. And summer time is always a function
   of the local time.


