- 1 Introduction to this HOWTO
- 2 Getting acquainted with Samba
- 3 Server Software Installation
- 4 Server Configuration
- 5 Configuration of the Clients
- 6 Links and Resources
Introduction to this HOWTO
This HOWTO is designed to help you move a network from many different clients speaking different languages, to many different machines that speak a common language. The ultimate goal is to help differing architectures and technologies, come together in a productive, happily coexisting environment.
Following the directions outlined in this HOWTO should give you an excellent step towards a peaceful cohabitation between Windows, and virtually all known variations of *nix.
This HOWTO originally started not as a HOWTO, but as a FAQ. It was intended to explore the functionality and power of the Gentoo system, portage and the flexibility of USE flags. Like so many other projects, it was quickly discovered what was missing in the Gentoo realm: there weren't any Samba HOWTOs catered for Gentoo users. These users are more demanding than most; they require performance, flexibility and customization. This does not however imply that this HOWTO was not intended for other distributions; rather that it was designed to work with a highly customized version of Samba.
This HOWTO will describe how to share files and printers between Windows PCs and *nix PCs. It will also show you how to mount and manipulate shares.
There are a few topics that will be mentioned, but are out of the scope of this HOWTO. These will be noted as they are presented.
This HOWTO is based on a compilation and merge of an excellent HOWTO provided in the Gentoo forums by Andreas "daff" Ntaflos and the collected knowledge of Joshua Preston. The link to this discussion is provided below for your reference:
Before you use this guide
There are a several other guides for setting up CUPS and/or Samba, please read them as well, as they may tell you things left out of this HOWTO (intentional or otherwise). One such document is the very useful and well written Gentoo Printing Guide, as configuration issues and specific printer setup is not discussed here.
After presenting the various USE flags, the following list will outline all of the topics covered as they are presented:
- On the Samba server:
- Install and configure Samba
- Install and configure CUPS
- Adding the printer to CUPS
- Adding the PS drivers for the Windows clients
- On the Unix clients:
- Install and configure CUPS
- Configuring a default printer
- Mounting a Windows or Samba share
- On the Windows Clients:
- Configuring the printer
- Accessing Samba shares
We will need the following:
- net-print/cups (built with the
- net-print/hplip (if you have an HP printer)
- A kernel of sorts (2.6)
- A printer (PS or non-PS)
- A working network (home/office/etc) consisting of more than one machine)
The main package we use here is
net-fs/samba, however, you will need a kernel with CIFS support enabled in order to mount a Samba or Windows share from another computer. CUPS will be emerged if it is not already.
Getting acquainted with Samba
The USE Flags
Before emerging anything, take a look at some of the various USE flags available to Samba.
Depending on the network topology and the specific requirements of the server, the USE flags outlined below will define what to include or exclude from the emerging of Samba.
|USE flag (what is that?)||Default||Recommended||Description|
||No||Include support for Kerberos. The server will need this if it is intended to join an existing domain or Active Directory. See the note below for more information.|
||No||Enables Access Control Lists. The ACL support in Samba uses a patched ext2/ext3, or SGI's XFS in order to function properly as it extends more detailed access to files or directories; much more so than typical *nix GID/UID schemas.|
||No||This enables support for the Common Unix Printing System. This provides an interface allowing local CUPS printers to be shared to other systems in the network.|
||No||Enables the Lightweight Directory Access Protocol (LDAP). If Samba is expected to use Active Directory, this option must be used. This would be used in the event Samba needs to login to or provide login to a Domain/Active Directory Server. The kerberos USE flag is needed for proper functioning of this option.|
||No||Include support for pluggable authentication modules (PAM). This provides the ability to authenticate users on the Samba Server, which is required if users have to login to your server. The kerberos USE flag is recommended along with this option.|
||No||Link Samba against libreadline. This is highly recommended and should probably not be disabled.|
||No||Python bindings API. Provides an API that will allow Python to interface with Samba.|
||No||Winbind allows for a unified logon within a Samba environment. It uses a Unix implementation of Windows RPC calls, PAM and the name service switch (supported by the c library) to enable Windows NT domain users to appear and work as Unix users on a Unix system.|
A couple of things worth mentioning about the USE flags and different Samba functions include:
- ACLs on ext2/3 are implemented through extended attributes (EAs). EA and ACL kernel options for ext2 and/or ext3 will need to be enabled (depending on which file system is being used - both can be enabled).
- While Active Directory, ACL, and PDC functions are out of the intended scope of this HOWTO, you may find these links as helpful to your cause:
Server Software Installation
First of all: be sure that all your hostnames resolve correctly. Either have a working domain name system running on your network or appropriate entries in your /etc/hosts file.
cupsaddsmb often borks if hostnames don't point to the correct machines.
Hopefully now you can make an assessment of what you'll actually need in order to use Samba with your particular setup. The setup used for this HOWTO is:
To optimize performance, size and the time of the build, the USE flags are specifically included or excluded.
ppds to your USE flags to make sure that when CUPS is built, it has proper foomatic support:
echo "net-print/cups ppds" >> /etc/portage/package.use
echo "net-fs/samba readline cups pam" >> /etc/portage/package.use
Now install the samba software:
emerge --ask net-fs/samba
This will emerge Samba and CUPS.
You only need to emerge this if you use an HP printer.
emerge --ask net-print/hplip
The main Samba configuration file is /etc/samba/smb.conf . It is divided in sections indicated by [sectionname]. Comments are either # or ;. A sample smb.conf is included below with comments and suggestions for modifications. If more details are required, see the man page for smb.conf , the installed smb.conf.example , the Samba Web site or any of the numerous Samba books available.
[global] ## # Replace MYWORKGROUPNAME with your workgroup/domain workgroup = ## MYWORKGROUPNAME ## # Of course this has no REAL purpose other than letting # everyone knows it's not Windows! # %v prints the version of Samba we are using. server string = Samba Server %v ## # We are going to use cups, so we are going to put it in here ;-) printcap name = cups printing = cups load printers = yes ## # We want a log file and we do not want it to get bigger than 50kb. log file = /var/log/samba/log.%m max log size = 50 ## # We are going to set some options for our interfaces... socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 ## # This is a good idea, what we are doing is binding the # samba server to our local network. # For example, if eth0 is our local network device interfaces = lo eth0 bind interfaces only = yes ## # Now we are going to specify who we allow, we are afterall # very security conscience, since this configuration does # not use passwords! hosts allow = 127.0.0.1 192.168.1.0/24 hosts deny = 0.0.0.0/0 ## # Other options for this are USER, DOMAIN, ADS, and SERVER # The default is user security = share ## # No passwords, so we're going to use a guest account! guest ok = yes ## # Now we setup our print drivers information! [print$] comment = Printer Drivers path = /etc/samba/printer ## # this path holds the driver structure guest ok = yes browseable = yes read only = yes ## # Modify this to "username,root" if you don't want root to # be the only printer admin) write list = root ## # Now we'll setup a printer to share, while the name is arbitrary # it should be consistent throughout Samba and CUPS! [HPDeskJet930C] comment = HP DeskJet 930C Network Printer printable = yes path = /var/spool/samba public = yes guest ok = yes ## # Modify this to "username,root" if you don't want root to # be the only printer admin) printer admin = root ## # Now we setup our printers share. This should be # browseable, printable, public. [printers] comment = All Printers browseable = no printable = yes writable = no public = yes guest ok = yes path = /var/spool/samba ## # Modify this to "username,root" if you don't want root to # be the only printer admin) printer admin = root ## # We create a new share that we can read/write to from anywhere # This is kind of like a public temp share, anyone can do what # they want here. [public] comment = Public Files browseable = yes public = yes create mode = 0766 guest ok = yes path = /home/samba/public
If you like to use Samba's guest account to do anything concerning printing from Windows clients: don't set
guest only = yesin the
[global]section. The guest account seems to cause problems when running
cupsaddsmbsometimes when trying to connect from Windows machines. See below, too, when we talk about
cupsaddsmband the problems that can arise. Use a dedicated printer user, like
printmeor whatever. It doesn't hurt and it will certainly protect you from a lot of problems.
Now create the directories required for the minimum configuration of Samba to share the installed printer throughout the network.
At least one Samba user is required in order to install the printer drivers and to allow users to connect to the printer. Users must exist in the system's /etc/passwd file. The next example uses the root user, but others can be used as well.
pdbedit -a root
The Samba passwords need not be the same as the system passwords in /etc/passwd .
You will also need to update /etc/nsswitch.conf so that Windows systems can be found easily using NetBIOS:
nano -w /etc/nsswitch.conf
hosts: files dns wins
This is a little more complicated. CUPS' main config file is /etc/cups/cupsd.conf . It's structure is similar to Apache's httpd.conf file, so many you may find it familiar. Outlined in the example are the directives that need to be changed:
ServerName PrintServer ## # your printserver name ServerAdmin root@PrintServer ## # the person for printer-related hate-mail, e.g. you AccessLog /var/log/cups/access_log ## # probably doesn't need changing ErrorLog /var/log/cups/error_log ## # doesn't really need changing either LogLevel debug ## # only while installing and testing, should later be # changed to 'info' MaxClients 100 ## # I've had to set this to 1000000000 or so because some time back, # there seemed to be a bug in CUPS' controlling of the web interface, # making CUPS think a denial of service attack was in progress when # I tried to configure a printer with the web interface. weird. BrowseAddress @IF(eth0) ## # Change this to your internal net interface <Location /> Order Deny,Allow Deny From All Allow From 192.168.1.* ## # the addresses of your internel network # e.g. 192.168.1.* will allow connections from any host on # the 192.168.1.0 network. change to whatever suits you </Location> <Location /admin> AuthType Basic AuthClass System Allow From 192.168.1.* ## # same as above, allow any host on the # 192.168.1.0 network to connect and do # administrative tasks after authenticating Order Deny,Allow Deny From All </Location>
Edit /etc/cups/mime.convs to uncomment some lines. The changes to mime.convs and mime.types are needed to make CUPS print Microsoft Office document files.
The following line is found near the end of the file. Uncomment it:
application/octet-stream application/vnd.cups-raw 0
Edit /etc/cups/mime.types to uncomment some lines.
The following line is found near the end of the file. Uncomment it:
CUPS needs to be started on boot, and started immediately.
rc-update add cupsd default
Installing a printer for and with CUPS
First, go to LinuxPrinting.Org to find and download the correct PPD file for your printer and CUPS. To do so, click the link Printer Listings to the left. Select your printers manufacturer and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click "Show". On the page coming up click the "recommended driver" link after reading the various notes and information. Then fetch the PPD file from the next page, again after reading the notes and introductions there. You may have to select your printers manufacturer and model again. Reading the CUPS quickstart guide is also very helpful when working with CUPS.
Now you have a PPD file for your printer to work with CUPS. Place it in /usr/share/cups/model . The PPD for the HP DeskJet 930C was named HP-DeskJet_930C-hpijs.ppd . You should now install the printer. This can be done via the CUPS web interface or via command line. The web interface is found at http://PrintServer:631 once CUPS is running.
lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd
Remember to adjust to what you have. Be sure to have the name (
-p argument) right (the name you set above during the Samba configuration!) and to put in the correct
parallel:/dev/blah or whatever device you are using for your printer.
You should now be able to access the printer from the web interface and be able to print a test page.
Installing the Windows printer drivers
Now that the printer should be working it is time to install the drivers for the Windows clients to work. Samba 2.2 introduced this functionality. Browsing to the print server in the Network Neighbourhood, right-clicking on the printer share and selecting "connect" downloads the appropriate drivers automatically to the connecting client, avoiding the hassle of manually installing printer drivers locally.
There are two sets of printer drivers for this. First, the Adobe PS drivers which can be obtained from Adobe (PostScript printer drivers). Second, there are the CUPS PS drivers, to be obtained by emerging
net-print/cups-windows . There doesn't seem to be a difference between the functionality of the two, but the Adobe PS drivers need to be extracted on a Windows System since it's a Windows binary. Also the whole procedure of finding and copying the correct files is a bit more hassle. The CUPS drivers support some options the Adobe drivers don't.
This HOWTO uses the CUPS drivers for Windows. Install them as shown:
emerge --ask cups-windows
Now we'll use the script
cupsaddsmb provided by the CUPS distribution. Be sure to read its manpage (
man cupsaddsmb), as it will tell you which Windows drivers you'll need to copy to the proper CUPS directory. Once you've copied the drivers, restart CUPS by running
/etc/init.d/cupsd restart . Next, run
cupsaddsmb as shown:
cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C
Instead of HPDeskJet930C you could also specify "-a", which will "export all known printers":
cupsaddsmb -H PrintServer -U root -h PrintServer -a
The execution of this command often causes the most trouble. Read through the posts in this thread for some troubleshooting tips.
Here are common errors that may happen:
- The hostname given as a parameter for
PrintServer) often does not resolve correctly and doesn't identify the print server for CUPS/Samba interaction. If an error like: Warning: No PPD file for printer "CUPS_PRINTER_NAME" - skipping! occurs, the first thing you should do is substitute
localhostand try it again.
- The command fails with an NT_STATUS_UNSUCCESSFUL . This error message is quite common, but can be triggered by many problems. It's unfortunately not very helpful. One thing to try is to temporarily set
security = userin your smb.conf . After/if the installation completes successfully, you should set it back to share, or whatever it was set to before.
This should install the correct driver directory structure under /etc/samba/printer . That would be /etc/samba/printer/W32X86/2/ . The files contained should be the 3 driver files and the PPD file, renamed to YourPrinterName.ppd (the name which you gave the printer when installing it (see above).
Pending no errors or other complications, your drivers are now installed.
Finalizing our setup
Lastly, setup our directories.
chmod 755 /home/samba
chmod 755 /home/samba/public
Testing our Samba configuration
We will want to test our configuration file to ensure that it is formatted properly and all of our options have at least the correct syntax. To do this we run
Load smb config files from /etc/samba/smb.conf Processing section "[printers]" Global parameter guest account found in service section! Processing section "[public]" Global parameter guest account found in service section! Loaded services file OK. Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions ... ...
Starting the Samba service
Now configure Samba to start at bootup; then go ahead and start it.
rc-update add samba default
Checking our services
It would probably be prudent to check our logs at this time also. We will also want to take a peak at our Samba shares using
smbclient -L localhost
Password: ## (You should see a BIG list of services here.)
Configuration of the Clients
Printer configuration of *nix based clients
Despite the variation or distribution, the only thing needed is CUPS. Do the equivalent on any other UNIX/Linux/BSD client.
emerge --ask cups
nano -w /etc/cups/client.conf
ServerName PrintServer ## # your printserver name
That should be it. Nothing else will be needed.
If you use only one printer, it will be your default printer. If your print server manages several printers, your administrator will have defined a default printer on the server. If you want to define a different default printer for yourself, use the
First list the available printers:
HPDeskJet930C accepting requests since Jan 01 00:00 laser accepting requests since Jan 01 00:00
Now define your printer (in the example, HPDeskJet930C) as the default printer:
lpoptions -d HPDeskJet930C
To enable printing on the Unix/Linux systems, either specify the printer to be used, or just use the default printer (second example):
lp -d HPDeskJet930C anything.txt
Just point your web browser to
http://printserver:631 on the client if you want to manage your printers and their jobs with a nice web interface. Replace
printserver with the name of the machine that acts as your print server, not the name you gave to the cups print server if you used different names.
Don't forget to install
net-fs/sambaon the client(s) that will be accessing the shares.
Now is time to configure our kernel to support CIFS. Since I'm assuming we've all compiled at least one kernel, we'll need to make sure we have all the right options selected in our kernel. For simplicity's sake, make it a module for ease of use. It is the author's opinion that kernel modules are a good thing and should be used whenever possible.
Then make the module/install it; insert it with:
Once the module is loaded, mounting a Windows or Samba share is possible. Use
mount to accomplish this, as detailed below.
The syntax for mounting a Windows/Samba share is:
mount -t cifs [-o username=xxx,password=xxx] //server/share /mnt/point
You can drop the
password options if no password is needed.
mount -t cifs //PrintServer/public /mnt/public
After you mount the share, you would be able to access it as if it were a local drive.
Printer Configuration for Windows NT/2000/XP clients
That's just a bit of point-and-click. Browse to \\PrintServer and right click on the printer (HPDeskJet930C) and click connect. This will download the drivers to the Windows client and now every application (such as Word or Acrobat) will offer HPDeskJet930C as an available printer to print to. :-)
Links and Resources
These are some links that may help you in setting up, configuration and troubleshooting your installation:
- CUPS Homepage
- Samba Homepage , especially the chapter on Samba/CUPS configuration
- LinuxPrinting dot Org
- Kurt Pfeifle's Samba Print HOWTO ( This HOWTO really covers ANYTHING and EVERYTHING I've written here, plus a LOT more concerning CUPS and Samba, and generally printing support on networks. A really interesting read, with lots and lots of details.)
- FreeBSD Diary's CUPS Topic
TroubleshootingSee this page from Kurt Pfeifle's "Printing Support in Samba 3.0" manual. Lots of useful tips there! Be sure to look this one up first, before posting questions and problems! Maybe the solution you're looking for is right there.
This article is based on a document formerly found on our main website gentoo.org.
The following people have contributed to the original document: Andreas "daff" Ntaflos, Joshua Preston, Joshua Saddler
They are listed here as the Wiki history does not provide for any attribution. If you edit the Wiki article, please do not add yourself here, your contributions are recorded on the history page.