| 2008-07-19 12:43:55 |
tonyw |
description |
Applying the recent upgrade to winbind (3.0.28a-1ubuntu4.4) broke access to samba shares from both Windows and Linux Clients when the username is listed in smbusers. Removing the winbind package on the server fixed the problem and restored access.
The Server is running XUbuntu 8.04 and is fully up-to-date as regards packages. Samba has both smbusers and smbpasswd files in use and which are used to map Windows login names (with spaces) to Unix user names. Samba Unix extensions are not in use on the server in order to avoid other access control problems (from Linux clients with different UID mappings). Same security is set to "user" and the network is organised as a Workgroup rather than a Windows Domain.
When the upgrade was applied access was refused to both Windows and Linux clients using user names in the smbusers file. However, access was possible from both Windows and Linux clients by logging in using an existing Unix Username on the server. This problem persisted despite rebooting both client and server.
Inspection of the upgrade logs showed that Winbind was the only candidate for causing the problem. Removing Winbind restored access to clients using smbusers usernames. Conclusion, the Winbind update is broken. |
Applying the recent upgrade to winbind (3.0.28a-1ubuntu4.4) broke access to samba shares from both Windows and Linux Clients when the username is listed in smbusers. Removing the winbind package on the server fixed the problem and restored access.
The Server is running XUbuntu 8.04 and is fully up-to-date as regards packages. Samba has both smbusers and smbpasswd files in use and which are used to map Windows login names (with spaces) to Unix user names. Samba Unix extensions are not in use on the server in order to avoid other access control problems (from Linux clients with different UID mappings). Samba security is set to "user" and the network is organised as a Workgroup rather than a Windows Domain.
When the upgrade was applied access was refused to both Windows and Linux clients using user names in the smbusers file. However, access was possible from both Windows and Linux clients by logging in using an existing Unix Username on the server. This problem persisted despite rebooting both client and server.
Inspection of the upgrade logs showed that Winbind was the only candidate for causing the problem. Removing Winbind restored access to clients using smbusers usernames. Conclusion, the Winbind update is broken. |
|
