Stueyb

Basically, as im doing a network tune up, im trying to rid the event logs of w32tm errors

So rather than hav e 100 clients hit time.windows.com im implementing an NTP time server on an old Dell 2450 server.

I tried installing one on a a FreeBSD 6.10 machine and installed ntpd from ports.

However I cant get it to work.

Looking at the ntpd.log I get

time# more < ntpd.log

19 Oct 19:49:05 ntpd[1240]: logging to file /ntpd.log
19 Oct 19:49:05 ntpd[1240]: ntpd 4.2.0-a Sun May 7 03:20:45 UTC 2006 (1)
19 Oct 19:49:05 ntpd[1240]: precision = 2.794 usec
19 Oct 19:49:05 ntpd[1240]: bind() fd 3, family 2, port 123, addr 0.0.0.0, in_cl
assd=0 flags=8 fails: Address already in use
19 Oct 19:49:05 ntpd[1240]: bind() fd 3, family 28, port 123, addr ::, in6_is_ad
dr_multicast=0 flags=0 fails: Address already in use
19 Oct 19:49:05 ntpd[1240]: bind() fd 3, family 28, port 123, addr fe80:2::206:5
bff:fe04:46f6, in6_is_addr_multicast=0 flags=0 fails: Address already in use
19 Oct 19:49:05 ntpd[1240]: bind() fd 3, family 2, port 123, addr 10.0.0.2, in_c
lassd=0 flags=8 fails: Address already in use
19 Oct 19:49:05 ntpd[1240]: bind() fd 3, family 28, port 123, addr ::1, in6_is_a
ddr_multicast=0 flags=0 fails: Address already in use
19 Oct 19:49:05 ntpd[1240]: bind() fd 3, family 28, port 123, addr fe80:4::1, in
6_is_addr_multicast=0 flags=0 fails: Address already in use
19 Oct 19:49:05 ntpd[1240]: bind() fd 3, family 2, port 123, addr 127.0.0.1, in_
classd=0 flags=0 fails: Address already in use
19 Oct 19:49:05 ntpd[1240]: kernel time sync status 2040
19 Oct 19:49:06 ntpd[1240]: sendto(130.159.196.118): Bad file descriptor
19 Oct 19:49:10 ntpd[1194]: sendto(130.159.196.118): Bad file descriptor
19 Oct 19:50:12 ntpd[1240]: sendto(130.159.196.118): Bad file descriptor
19 Oct 19:50:15 ntpd[1194]: sendto(130.159.196.118): Bad file descriptor
19 Oct 19:51:17 ntpd[1240]: sendto(130.159.196.118): Bad file descriptor
19 Oct 19:51:19 ntpd[1194]: sendto(130.159.196.118): Bad file descriptor
19 Oct 19:52:21 ntpd[1240]: sendto(130.159.196.118): Bad file descriptor
19 Oct 19:52:23 ntpd[1194]: sendto(130.159.196.118): Bad file descriptor
19 Oct 19:52:52 ntpd[1194]: ntpd exiting on signal 15
19 Oct 19:53:01 ntpd[1240]: ntpd exiting on signal 15
time#

Any ideas where im going wrong ?

rich101

mmmm maybe the easiest option is to use a DC as the time reference server
and have that one host do the NTP sync.

If your workstations are in the domain they should automatically look to the DC for time, but do check as it is YEARS since I did this.

rich

Stueyb

Hi

My problem is that I am running a mixed mode domain, with an NT4 PDC with W2k and W2K3 member servers

This means, that even by MS' own admission it will not be able to sync w2K and above clients using the NT4 PDC and BDCs

David_Wallis

no, but you could change who has rights to set the system time, and then use NET Time /set /yes

or you could download the updated time service and configure that.

I managed to get time sync working from our PDC Emulator at my old place for around 8000/9000 mixed clients, dont get me wrong though, it took some pissing about with!

Kieran_Burns

iTrader: (1)

if i'm missing something obvious forgive me...

but you set one of your win2k/3 servers as the time source in the login script

net time /setsntp:<win2k_server_name>

and have THAT do the same with an external time source - there are loads available

then as above...

NET Time /set /yes