Hopefully simple for you m$ gurus..

I have a Domain controller running 2kserver..

most the client pcs on the domain are also 2k

for some reason.. even tho they are suppost to syncronise their time with the domain controller at logon.. they dont.. am i missing anything?

thanks in advance

Check the w32time service is running, and no other time synchronisation services. Then if you want real synchronisation, throw the lot away and get an ntp implementation like xntpd

Check the w32time service is running, and no other time synchronisation services. Then if you want real[/i'] synchronisation, throw the lot away and get an ntp implementation like xntpd

on the server or client?

Client, mainly.

Make sure that the time service is running on server and all PCs. It's not by default under Win2K Pro. You'll also need to synchronise your server's time with an external time source (for accuracy) by issuing "net time \\servername /setsntp:". There're loads of public "atomic clocks" out there.

Client, mainly.

Well have just tried to start it on the server.. but its complaining that it cant start?

to get a PDC to pass down the time to clients does w32time have to be enabled? is there anyway i can enable the service on the clients automatically?

Well have just tried to start it on the server.. but its complaining that it cant start?

to get a PDC to pass down the time to clients does w32time have to be enabled?

Yes.

Incidentally, are you using W2K in native mode...? If so, then there's no such concept as "primary domain controller" anymore. Microsnot call it "global catalog server" now...

Just being picky.

Yes I think so. w32time is an implementation of simple ntp (sntp). So there's a hierarchy time source -> server -> client.

What's in your event log when the service tries to start?

"unexpected error when trying to start service: the port may be in use"

You have another service registered against the ntp port - do a "netstat -noa" (hope the -o works in 2k) and look for a process against the ntp port (TCP port 123). Find out what it is and stop it.

You have another service registered against the ntp port - do a "netstat -noa" (hope the -o works in 2k) and look for a process against the ntp port (TCP port 123). Find out what it is and stop it.

the O switch doenst work..

but there is a UDP listed against port 123...

Cant help with the port problem. We had the same problem, in the end I added an entry to the logon script to force the sync myself using the command,

net time \\servername /set /y where the servername is the name of the 2k server you want to sync with.

OK get tcpview which will give you the process id.

Cant help with the port problem. We had the same problem' date=' in the end I added an entry to the logon script to force the sync myself using the command,

net time \\servername /set /y where the servername is the name of the 2k server you want to sync with.[/quote']

Does this need any permissions tho?

The user may need admin rights on the workstation I think, not a problem where I work because one of the main apps requires local admin rights for installing updates.

You needed local admin rights on NT4, but you don't on XP for the command to work not sure about 2K.

Out of interest, why port 123? NTP normally uses port 37, or so I thought :confused:

Here's the relevant bit of my services file:

time               37/tcp    timserver
time               37/udp    timserver
rlp                39/udp    resource               #Resource Location Protocol
nameserver         42/tcp    name                   #Host Name Server
nameserver         42/udp    name                   #Host Name Server
nicname            43/tcp    whois
domain             53/tcp                           #Domain Name Server
domain             53/udp                           #Domain Name Server
bootps             67/udp    dhcps                  #Bootstrap Protocol Server
bootpc             68/udp    dhcpc                  #Bootstrap Protocol Client
tftp               69/udp                           #Trivial File Transfer
gopher             70/tcp
finger             79/tcp
http               80/tcp    www www-http           #World Wide Web
kerberos           88/tcp    krb5 kerberos-sec      #Kerberos
kerberos           88/udp    krb5 kerberos-sec      #Kerberos
hostname          101/tcp    hostnames              #NIC Host Name Server
iso-tsap          102/tcp                           #ISO-TSAP Class 0
rtelnet           107/tcp                           #Remote Telnet Service
pop2              109/tcp    postoffice             #Post Office Protocol - Version 2
pop3              110/tcp                           #Post Office Protocol - Version 3
sunrpc            111/tcp    rpcbind portmap        #SUN Remote Procedure Call
sunrpc            111/udp    rpcbind portmap        #SUN Remote Procedure Call
auth              113/tcp    ident tap              #Identification Protocol
uucp-path         117/tcp
nntp              119/tcp    usenet                 #Network News Transfer Protocol
ntp               123/udp                           #Network Time Protocol

So it looks like it could be either, although the only one actually called "ntp" is 123. However "time" may be the windows service. However on my home PC here, 123 is in use, but 37 is not, and "windows time" is running (The name changed from 2k to xp IIRC).