Ubuntu
samba package

  1. Bug #1292548
  2. Comment #2

Comment 2 for bug 1292548

Revision history for this message
Raoul Bhatia (raoul-bhatia) wrote : Re: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty) breaks access to the server

Thank you for your fast reply.

Updating Samba 3 to Samba 4 *is* possible, please see https://wiki.samba.org/index.php/Updating_Samba .

There might be some configuration changes but all in all it is no big deal to manually merge them - at least not for a basic setup without any active directory (AD) integration.

As stated, when using Samba 2:4.1.3+dfsg-2ubuntu3 from Ubuntu trusty, things do not work even with the most basic/default config file.

Replacing the packages with a more recent Version 2:4.1.5+dfsg-1 from Debian Jessie helps to resolve this issue. No further configuration changes compared to 2:4.1.3+dfsg-2ubuntu3 from trusty are required.

I simply downloaded all packages and issued
# dpkg -i libsmbclient_4.1.5+dfsg-1_amd64.deb libwbclient0_4.1.5+dfsg-1_amd64.deb python-samba_4.1.5+dfsg-1_amd64.deb samba_4.1.5+dfsg-1_amd64.deb samba-common_4.1.5+dfsg-1_all.deb samba-common-bin_4.1.5+dfsg-1_amd64.deb samba-dsdb-modules_4.1.5+dfsg-1_amd64.deb samba-libs_4.1.5+dfsg-1_amd64.deb samba-vfs-modules_4.1.5+dfsg-1_amd64.deb smbclient_4.1.5+dfsg-1_amd64.deb

Please let me know what else you require to address this bug report.

Thanks,
Raoul