[Samba] Re: can't access Samba share when clocks skew is too great
lz at csltd.com.ua
Fri Sep 22 14:06:42 GMT 2006
Thanks, I understand. As a matter of fact, yes, I do need help with GPOs
(not NTP on Samba server - thanks, that's clear to me), so if you can offer
a suggestion, I'd appreciate (I understand this is off topic on the Samba
At the same time, as I mentioned in the previous post, I'm trying to
understand why clients with incorrect clock can connect to Windows servers
and can't connect to Samba. I thought Samba tried to emulate Windows file
server as close as possible. In this particular case I thought Samba would
fall back to NTLM auth. Maybe I misunderstand something.
"Aaron Kincer" <kincera at gmail.com> ???????/???????? ? ???????? ?????????:
news:4513E916.8060106 at gmail.com...
It is pretty standard behavior for encrypted authentication schemes to
reject authentication requests when the time deviation between the
client and server are too far apart. This is by design. It is basically
a timeout from Active Directory's perspective. You can use Active
Directory GPOs to configure clients to use NTP and you can also
configure NTP on your Samba server (use cron to sync time hourly if you
must). This should fix your authentication issue. If you need help with
GPOs or configuring NTP on your Samba server, let me know.
Bruno Rodrigues Neves wrote:
> 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?
> On 9/22/06, Leonid Zeitlin <lz at csltd.com.ua> 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
>> accessed. I understand that Kerberos cannot authenticate the clients due
>> clock skew; however, I thought that in such case Samba could falls back
>> 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.
>> 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
More information about the samba