This post is provided to you by Walter “DaK_TaLeS”, my friend. So, everytime you read “I”, it refers to him and not to me. Biology Dictionary Free Download English Hindi. Just to introduce you his home-computer environment, he owns an home server/desktop hybrid system that provides SAMBA file-sharing and CUPS to export his printers to the whole family computers. As you may already imagine, other laptops run different versions of Windows (both 32 and 64 bits). The goal that I’ve been finally able to achieve is a smart configuration setup in order to export Windows printers drivers through CUPS service using SAMBA to share the printers onto a Windows network. This is a feature that isn’t spread out, but kind of useful.

To say it shortly, the shared printers will be available and installed on Windows systems with a simple double click, no need to Google for drivers. It’s a kind of magic. How to do so? There’s plenty of guides around the Internet so I won’t waste bits here explaining this (you can take a look at for further information). As the man-page states: cupsaddsmb exports printers to the SAMBA software (version 2.2.0 or higher) for use with Windows clients.

Install CUPS PostScript Windows Drivers. Go to the CUPS software download page and download the file cups-windows-6.0-sourde-tar.gz, this file contains the CUPS printer drivers for Windows. Uncompress it to a folder. Get inside the folder with your terminal screen and run: sudo make intall. This will create 4 files in your. I'm trying to setup a samba print server so that when users add a printer in Windows, the Cups postscript drivers are supplied and installed automatically.

Cupsaddsmb uses the new RPC-based printing support in SAMBA 2.2.x to provide printer drivers and PPD files to Windows client machines. In order to get through the next part of the walk-through, make sure you have SAMBA and CUPS services already installed.

Let’s configure SAMBA to provide this service by editing/adding the following lines in /etc/samba/smb.conf: [global] load printers = yes printing = cups printcap name = cups [printers] comment = All Printers path = /var/spool/samba browseable = no public = yes guest ok = yes writable = no printable = yes [print$] comment = Printer Drivers path = /etc/samba/drivers browseable = yes guest ok = no read only = yes write list = root Of course, you should edit your share options according to your needs. I feel comfortable creating an user on the server and make every service run with its credentials. This makes my family happier since they don’t have to rant against annoying login popups when accessing the printers.

[global] map to guest = bad user security = share guest ok = yes guest account = winsmb Notice that I’ve set winsmb as guest account for accessing the sharing. If you’ve chosen another username, edit the configuration above accordingly. At this point you should be able to see the shared printers from your Windows clients, but you won’t be able to automatically fetch the drivers through the LAN. Now go to a Windows client (it’s important that it’s running Windows 2000 or newer). These steps need to be performed for each kind of architecture in your Home facility. If you own two or more 32-bit version of Windows, you don’t need to do that more than once. You have to perform the following tasks once for 32-bit systems and once for 64-bit system.