I tried some experiments today with longer usernames (e.g. 32
characters, which is the maximum allowed on the Linux distros I
tried). mounting with 32 character usernames worked fine (at least
to Samba). I wouldn't expect anything different to Windows.
I don't remember any recent change to add this support so as long as
you are running a kernel from the last three or four years, hard to
guess what is the issue (if you have evidence like a wireshark trace
or debugging information showing the username getting
remapped/corrupted when passed down that might be helpful)
Can you see the module version (modinfo cifs or "cat
/proc/fs/cifs/DebugData | grep Version") and the kernel version
("uname -a")?
On Wed, Jul 31, 2019 at 2:39 PM Nathan Shearer <mail@xxxxxxxxxxxxxxxx> wrote:
>
> I spent the last two days trying to mount a windows share, and it turns
> out it was not a problem with:
>
> * share permissions
> * filesystem permissions
> * incorrect password
> * firewalls
> * antivirus software
> * smb version
>
> But was in fact an issue with the username. The username I had was 23
> characters, which is longer than the "pre-Windows 2000" logon name which
> is what cifs was using, even with smb vers=3.0. The error was always
> status code 0xc000006d STATUS_LOGON_FAILURE which this time was actually
> an authentication problem since the client was using the wrong username.
>
> Is there any plan to support windows usernames in samba/cifs that are
> *post* windows 2000 era?
>
> # mount.cifs -V
> mount.cifs version: 6.9
>
--
Thanks,
Steve
