samba - May 2003 - Network Time problems with Windows 2k

I searched through the documentation and mailing list archives to find a
solution but was unsuccessful. I saw that others had encountered this
but I was unable to find a solution. Suggestions

 

This is with samba 2.2.8a functioning as a PDC and Windows clients sp3 

RH8.0

 

Thanks 

 

 

 

Because of repeated network problems, the time service has not been able
to find a domain controller to synchronize with for a long time. To
reduce network traffic, the time service will wait 960 minutes before
trying again. No synchronization will take place during this interval,
even if network connectivity is restored. Accumulated time errors may
cause certain network operations to fail. To tell the time service that
network connectivity has been restored and that it should resynchronize,
execute "w32tm /s" from the command line. 

 

Ross Anderson    rosander@owbn.org

Lead Engineer,Guthrie Theater 

http://www.guthrietheater.org

On Tuesday 06 May 2003 09:14, Ross Anderson wrote:
> Because of repeated network problems, the time service has not been able
> to find a domain controller to synchronize with for a long time. 
Not a Samba issue. Windows Time Service is looking for an NTP (SNTP, NNTP) 
server. The NT4 like NetBIOS type time server that Samba can be allows the 
time to be synched with the "net time" command and not this service.
Either
set up an NTP server and direct the clients to it or place the proper net 
time command in a logon script. The biggest problem with the "net
time" style
is that if the users aren't admins it will fail on the Win2k/XP boxes, so 
basically I reserve its use only for the non-NT based Windows.