I recently replaced a samba server with a new machine. Version 3.0.14 was used on the old server and is used on the new server as well. I copied all of the configuration files using rsync from the old server to the new server. Now I have one user that cannot access a share on the new server, but that could be accessed on the old server. After much troubleshooting I have isolated the problem to the fact that samba on the new server treats the user as if it is part of a group in the invalid users for the share. /etc/group does put the user in the group that is an invalid users. Can anyone help? -- Billie H. Cleek Project Manager 3259 E. Sunshine Ave Suite AA Springfield, Missouri 65804 Tel: (417) 886-2528 Fax: (417) 886-2541 bcleek@essystemsinc.com http://www.essystemsinc.com PGP: 0xE9734285 Fingerprint = 1CF8 1903 8574 EFAD 0322 1A2E CC02 52B8 E973 4285
> I recently replaced a samba server with a new machine. Version 3.0.14 > was used on the old server and is used on the new server as well. I > copied all of the configuration files using rsync from the old server > to the new server. Now I have one user that cannot access a share on > the new server, but that could be accessed on the old server. After > much troubleshooting I have isolated the problem to the fact that > samba on the new server treats the user as if it is part of a group > in the invalid users for the share. /etc/group does put the user in > the group that is an invalid users. Can anyone help?...remove the user from the invalid group? Remove the group from Samba's list of invalid groups? You could try specifying "valid users = username" for just that share, but I don't know whether that will bypass Samba's invalid groups option. Cheers, Adam.
I found the problem; I had two groups with the same group id. The user that could not connect was in one of the groups. Problem solved. ESSI - Billie H. Cleek wrote:> I recently replaced a samba server with a new machine. Version 3.0.14 > was used on the old server and is used on the new server as well. I > copied all of the configuration files using rsync from the old server to > the new server. Now I have one user that cannot access a share on the > new server, but that could be accessed on the old server. After much > troubleshooting I have isolated the problem to the fact that samba on > the new server treats the user as if it is part of a group in the > invalid users for the share. /etc/group does put the user in the group > that is an invalid users. Can anyone help? >-- Billie H. Cleek Project Manager 3259 E. Sunshine St Suite AA Springfield, Missouri 65804 Tel: (417) 886-2528 Fax: (417) 886-2541 bcleek@essystemsinc.com http://www.essystemsinc.com PGP: 0xE9734285 Fingerprint = 1CF8 1903 8574 EFAD 0322 1A2E CC02 52B8 E973 4285
Apparently Analagous Threads
- Step-by-Step Tutorial: How to Setup Your Own e-Commerce Online Store using WooCommerce 3.4.5, Wordpress 4.9.8, and CentOS 1805 (LAMP) in Amazon AWS Cloud
- why more than one temp file for a single rsync download?
- RE: Presales Question - Customer Service (fwd)
- Problem with tor2 driver and Zapata Tormenta 2 Quad T1/PRI Card