obey pam restrictions = yes
pam password change = yes
I reconfigured the server at these points (and profile acls = yes). At
least it improved the unaccessible profile: One of the 2 concurrent
clients gets its profile instantly, the other one has a minute of
waiting before getting its data.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/05/2007 02:02 PM, Tim Boneko wrote:
Has anybody had this problem before? If not, where should i
start digging?
By the logs you sent, definetely PAM. :-)
I'm running Samba 3.0.24 on Debian stable with slapd-2.2.23 backend.
Felipe Augusto van de Wiel schrieb:
PAM: UNKNOWN PAM ERROR is not something nice to see
on your longs.
That's sad but true...
Did you already increase the log level of Samba?
I'll check that tomorrow (hopefully).
Simultaneously should be interpreted at the exactly
same
Has anybody had this problem before? If not, where should i start digging?
I'm running Samba 3.0.24 on Debian stable with slapd-2.2.23 backend.
smb.conf is attached below.
When two different users log in at the same moment, the login process
seems to freeze for a minute and the client (win2k)
