UPDATE: After I successfully followed these steps, I observed my Windows 7 machines were not being able to authenticate with Samba, which caused non-public shares to become inaccessible.After lots of googling around and some trial-and-fail attempts, I was able to verify that the following step seems to have been missing: The new Samba seems to look for its smbpasswd file in the default location, which is the same folder where is (/opt/etc/samba).
Sony do you even test the updates before you unleash them on your trusting customers?You need to RESTART (logout and login is NOT enough) any Windows client after updating the Samba server to access the new shares, due to some weird caching in Windows.The config for the new Samba server can be found in /opt/etc/samba/smb.conf, so changing the samba config would involve editing this file, i.e.I know how to build Samba from source, but I am not sure how to upgrade it correctly without losing my domain controller data (Samba is my domain controller). I hope not, because it is very boring and not practical solution. So generally did some body upgrade Samba from any old version to much newer version with 100% success? The Update Process Run the following steps, whether you are updating a Samba Active Directory (AD) domain controller (DC), a Samba NT4-style PDC, a Samba domain member, or a standalone installation: Stop all Samba services. In case you switch to new major release, read the release notes of the initial version (x.y.0) and the ones from minor versions up to the new version you will update to.The documentation was not very clear about that (at least I didn't find a helpful guide). For example, if you update from 4.4.4 to 4.6.2, read the 4.5.0, 4.6.0, 4.6.1, and 4.6.2 release notes.