Hi Bruno, Thanks, I understand that. Still, I'm not sure why Samba wouldn't use NTLM auth if Kerberos fails. It appears that Windows file servers do exactly that, since clients with incorrect clock can connect to Windows servers and are telling me that "Samba is not working for them, while Windows is".
Thanks, Leonid "Bruno Rodrigues Neves" <[EMAIL PROTECTED]> ???????/???????? ? ???????? ?????????: news:[EMAIL PROTECTED] Hi Leonid, I don´t know the cause of this problem, but if you try add into your netlogon script a line such as a "set time" in order to set the clock to the same from the server? Regards! -- Bruno On 9/22/06, Leonid Zeitlin <[EMAIL PROTECTED]> wrote: > Hi all, > I have a Samba 3.0.23c server joined to an Windows 2003 AD domain. Users > access it from Windows workstations (XP, 2000). The problem is that if a > workstation has its time off by more than 5 minutes, Samba server cannot > be > accessed. I understand that Kerberos cannot authenticate the clients due > to > clock skew; however, I thought that in such case Samba could falls back to > NTLM auth. At least, the workstations with the wrong clock can access > Windows file servers, but not Samba. Is Samba's behavior in this case > intentional? Is this supposed to work? How can I help or debug this > situation? Any help is appreciated. > > Thanks, > Leonid > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
