On Fri, Mar 16, 2007 at 08:58:19AM +1300, Jason Haar wrote: > > 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 :-)
The only way Windows servers could be handling this situation is to ignore clock-skew errors on incoming AP_REQ messages. I actually believe they're doing this, and I can't let Samba do the same. I've improved the error message for 3.0.25 so if Samba fails a login due to clock skew the client at least gets an error message to this effect. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
