Hi SInce I have my Suse 10.0 I sometimes adjust the time using the command line: ntpdate -u time.uni-freiburg.de ; hwclock --systohc This works. After reading a thread here this morning I configured NTP in Yast, so that this could be done automatically. But my var/log/messages says: Oct 2 10:08:09 venus ntpd[6614]: ntpd 4.2.0a@1.1191-r Fri Sep 9 17:17:17 UTC 2005 (1) Oct 2 10:08:09 venus ntpd[6614]: precision = 1.000 usec Oct 2 10:08:09 venus ntpd[6614]: Listening on interface wildcard, 0.0.0.0#123 Oct 2 10:08:09 venus ntpd[6614]: Listening on interface wildcard, ::#123 Oct 2 10:08:09 venus ntpd[6614]: Listening on interface lo, 127.0.0.1#123 Oct 2 10:08:09 venus ntpd[6614]: Listening on interface eth0, 192.168.2.2#123 Oct 2 10:08:09 venus ntpd[6614]: kernel time sync status 0040 the only thing I found after googling for status 0040 was, that I should check that the firewall allows port 123 (UDP) in both directions. But can it really be the firewall? Why does it work perfectly from command line then? Output of xntpdc is: ntpdc> peer remote local st poll reach delay offset disp ======================================================================= =LOCAL(0) 127.0.0.1 10 64 377 0.00000 0.000000 0.03087 *swisstime.ee.et 192.168.2.2 2 1024 377 0.02505 0.009517 0.11856 ntpdc> (I must confess that I have not the slightest idea what these messages want to tell me, and I havn't found out in xntp_doc...) Can someone help me understanding a bit more? Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com Madagascar special: http://www.sanic.ch