[RESOLVED] No propagation of newly created users
Published: September 15, 2021 - 7:53 AM
Hello,
First of all, thank you for your very comprehensive and easy-to-use documentation on Samba AD, thanks to the different color blocks on your pages.
I just migrated from Samba NT4 to Samba AD.
Everything went smoothly.
I also have a Samba file server that I joined to the domain with WinBind and a Linux server (without Samba) that I joined to the domain with sssd (following your documentation).
The users resulting from the migration can:
- mount the shares defined on the Samba file server without any problems from a session opened on a Windows 10 PC joined to the domain.
- open SSH sessions on the Linux server
without any problems. However, if I create a new user on Samba AD with: `samba-tool user create`, this new user cannot mount the file server shares (it invariably asks me for a login and password).
This new user also cannot open an SSH session on the Linux server. The sssd log on the Linux server reports "user unknown".
On the Linux server, `getent passwd` does not list this new user.
On the Samba file server, `wbinfo -u` correctly lists this new user.
However, this new user can log in without issue on a newly joined Windows 10 PC or on a PC already included in the migration, but once logged in, this new user cannot connect to the shares defined on the Samba file server (the login and password prompts without success).
In fact, the Samba file server and the Linux server do not recognize this new user, as if Samba AD had not propagated to them.
What's wrong? Is it Samba AD or my method of creating a new user?
In the file server's smb.conf file, I correctly used the "rfc2307" mode (because I was migrating from SambaNT4), and in the Linux server's sssd.conf file, I added "ldap_id_mapping = False".
Thank you.
Regards,
D. Vuillet
First of all, thank you for your very comprehensive and easy-to-use documentation on Samba AD, thanks to the different color blocks on your pages.
I just migrated from Samba NT4 to Samba AD.
Everything went smoothly.
I also have a Samba file server that I joined to the domain with WinBind and a Linux server (without Samba) that I joined to the domain with sssd (following your documentation).
The users resulting from the migration can:
- mount the shares defined on the Samba file server without any problems from a session opened on a Windows 10 PC joined to the domain.
- open SSH sessions on the Linux server
without any problems. However, if I create a new user on Samba AD with: `samba-tool user create`, this new user cannot mount the file server shares (it invariably asks me for a login and password).
This new user also cannot open an SSH session on the Linux server. The sssd log on the Linux server reports "user unknown".
On the Linux server, `getent passwd` does not list this new user.
On the Samba file server, `wbinfo -u` correctly lists this new user.
However, this new user can log in without issue on a newly joined Windows 10 PC or on a PC already included in the migration, but once logged in, this new user cannot connect to the shares defined on the Samba file server (the login and password prompts without success).
In fact, the Samba file server and the Linux server do not recognize this new user, as if Samba AD had not propagated to them.
What's wrong? Is it Samba AD or my method of creating a new user?
In the file server's smb.conf file, I correctly used the "rfc2307" mode (because I was migrating from SambaNT4), and in the Linux server's sssd.conf file, I added "ldap_id_mapping = False".
Thank you.
Regards,
D. Vuillet