10/13/2019 Install Samba 4 On Debian Wheezy Upgrade
COMPILING SAMBA 4 ON DEBIAN WHEEZY. I then changed it up a bit to use GIT instead of manually downloading the packages as it makes it easier to upgrade in the future. The modified proceedures are below. I like compiling in /usr/src — and I’m letting Samba 4 install to its default location, which I know is a horrific violation of.
![]()
: English - Simple Samba file sharing server setup This is a minimal Samba setup to let other machines access files on a Debian machine. Install Samba Server # apt-get install samba Install Samba Client # apt-get install samba-client Configure the Samba daemon Edit the Samba configuration file. # nano /etc/samba/smb.conf In the global section, check the name of the workgroup.
It might be useful to know it when you'll try to connect from a Windows machine: global. Workgroup = STURBAIN Locate the home share definition: homes In that section you may enable read-write access to the home directories: read only = no To share files in some other path on the system, add another share definition such as: ourfiles comment = Some useful files read only = no locking = no path = /pathtoourfiles guest ok = no Add Samba users Samba uses it's own password system so users need to be added by root. Note that the users have to exist in /etc/passwd # smbpasswd -a me # smbpasswd -a you You will be prompted for a password for each of those users. To list existing Samba users: pdbedit -w -L Restart the Samba daemon # /etc/init.d/samba restart or, if you are using systemd # /usr/sbin/service smbd restart Try to access the shares (as a normal user) Try locally first, then from another machine on the network which also installed samba client. When prompted, use the password entered when adding the user to Samba. To access my share: $ smbclient //ourmachine/me To access your share: $ smbclient -U you //ourmachine/you To access our shared(!) share: $ smbclient //ourmachine/ourfiles See also.
If you’re like me, and were wanting to get the Samba security fixes in place quickly for Debian Jessie version of SAMBA — you’ll maybe have learned that they decided not to backport the fixes for man-in-the-middle, but instead upgrade the whole thing to SAMBA 4.2. That’s all well and good — but the security update broke SAMBA on my Debian boxes in the test lab (which run Jessie). The fix was pretty simple after some fairly serious wasted time Googling for it. By default, it SAMBA will now require the winbind package to be installed, otherwise it will silently fail to start.
The symptom I had was that internal DNS resolution for SAMBA stopped working. And nothing was bound to port 53. Of course, that was because Samba wasn’t starting at all.
I hope that helps someone — just make sure winbind is installed and running. They really should have tested this better, even with such a bad flaw in the Microsoft and Samba stuff.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |