[Samba] Samba kerberos more time sensitive that Windows?
ktm at rice.edu
Thu Mar 15 20:10:11 GMT 2007
On Fri, Mar 16, 2007 at 08:58:19AM +1300, Jason Haar wrote:
> Jeremy Allison wrote:
> > It truely is a strange case. I find that if I change
> > the clock on the client and log in it re-syncs the
> > time from the DC and all connections to servers work
> > (as you'd expect with the correct time).
> > If I log in then change the client time and then attach
> > to the Samba server it fails to login (interal logs show
> > clock-skew errors).
> That is our situation. Whatever this VMware bug is, it is stopping the
> virtualized OS from slewing the time. So I'd guess the OS fails to be
> able to re-sync against the DC, and so it fails later when it tries
> connecting to the Samba server. However (as mentioned in my original
> mail), this problem doesn't appear to affect Win2K3 servers - only Samba.
> As mentioned, this problem is really a VMware problem, so we're off
> fixing the cause - but I think it's always a good idea to make Samba
> look more like a Windows server - even if it means handling such a
> hare-brained situation. But - that's easy for me to say :-)
> Jason Haar
> Information Security Manager, Trimble Navigation Ltd.
> Phone: +64 3 9635 377 Fax: +64 3 9635 417
> PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1
We had similar problems with NTP running on a guest VM. The knowledge
base said to use NTP on the host machine and vmtools (the guest machine
tools) on the guest to sync its time with the host. Otherwise we had
many, many load related timing problems with the guest machines.
More information about the samba