Joan Antoni Torres
2011-Apr-19 06:54 UTC
[Samba] Samba PDC + OpenLDAP + Windows 7 user name length
Hello, We have the following configuration: - OpenLDAP 2.4.21 - Samba 3.5.2 - Windows 7 x64 - Roaming Profiles We have 2500 users and format of usernames are: name.firtsname.secondname (Spanish has first and second name) Windows 7 clients are joined to the Samba domain. Everything works fine, users can logon in Samba domain, network volumes (F: , G: ...) are mapped correctly and the user profile is stored on the server at user logoff. What is wrong? We have problems when the username is longer than 19 characters. These users, can't logon, they see next error in the screen: "error in the local Session Manager service to start a session. The data area passed to a system call is too small." (translated from Spanish version) After this, Windows 7 makes an automatic logoff. The funny thing is that the profile of these users with too long name, are stored in profile shared and the whole name, not truncated. This same environment with Samba + OpenLDAP works fine with Windows XP clients and users with names greater than 19 characters haven't any problem. Any ideas? Any help would be welcome. Greetings Jantoni
Volker Lendecke
2011-Apr-19 14:19 UTC
[Samba] Samba PDC + OpenLDAP + Windows 7 user name length
On Tue, Apr 19, 2011 at 08:54:18AM +0200, Joan Antoni Torres wrote:> Hello, > > We have the following configuration: > > - OpenLDAP 2.4.21 > - Samba 3.5.2 > - Windows 7 x64 > - Roaming Profiles > > We have 2500 users and format of usernames are: > > name.firtsname.secondname (Spanish has first and second name) > > Windows 7 clients are joined to the Samba domain. Everything works > fine, users can logon in Samba domain, network volumes (F: , G: ...) > are mapped correctly and the user profile is stored on the server at > user logoff. > > What is wrong? We have problems when the username is longer than 19 > characters. These users, can't logon, they see next error in the > screen:https://bugzilla.samba.org/show_bug.cgi?id=7343 This is known and sounds VERY much like a Win7 bug. You might contact Microsoft about this. I've tried without success. With best regards, Volker -- SerNet GmbH, Bahnhofsallee 1b, 37081 G?ttingen phone: +49-551-370000-0, fax: +49-551-370000-9 AG G?ttingen, HRB 2816, GF: Dr. Johannes Loxen