Deploying Suse Linux Enterprise Server
 |
Purchase "Deploying Suse Linux Enterprise Server" at Lulu.com |
CUPS Print Server
- Installing a Printer
- Configuring the CUPS Print Server
- Using the Web Interface to Manage CUPS
- Configuring Client Computers
Configuring Clients to Print Through CUPS
Configuring Microsoft Windows Clients
When dealing with Microsoft Windows Clients, there are two ways to configure them to print to CUPS servers. The most popular way is to utilize the Samba server, as this service will automatically share the CUPS printers. This method is covered in-depth in the Samba Chapter of this book.
The second way to configure a Windows machine to print via a CUPS server is to manually create a printer on the client that will send the print job directly to a printer on the CUPS server. This is more of a brute force way to print to a CUPS server, but can be useful in certain circumstances.
Selecting a Network Printer and Entering the Printer Address as a URL
The first step to configure a Windows Client to print in this way is to start the Add Printer Wizard. You are probably very familiar with these steps, but to communicate with the CUPS Server, you must configure it as a "Network Printer" and you must manually enter the Address of the CUPS printer on your server. For example: "http://server1.private.lan:631/printers/hpdeskjet"
Once you point to the correct address, continue on in the Add Printer Wizard and it will ask you for the correct driver to use. You can either use a specific driver for that particular printer, or you can simply use one of the Apple Postscript drivers that are already available.
Assigning a Driver to the CUPS Printer and the New Printer Listed
Note - Remember this is a very basic way to setup a Windows Client to Print to a CUPS Server and you may encounter some problems with certain Firewalls on the client machine. I highly recommend using the Samba server if you are going to share your printers with multiple Microsoft Windows clients.
Configuring a SLED Client
When configuring Suse Linux Enterprise Clients for printing you have the option of configuring them in a few ways. Each way has it's benefits and drawbacks and you must decide which way would be the best for that particular client. These Ways include:
CUPS Client Only - This configuration directly ties your print queue to the print queue(s) of the server. This is the most secure method of configuring your clients, but has the drawback of only being able to print to one server (which probably isn't a problem with most networks) and having all of the printers from the server listed on your client.
CUPS Using Broadcasting - This configuration simply "listens" for the CUPS Server broadcast and automatically adds any printers that are present on the servers that are broadcasting their presence on the network.
Remote IPP Queue - This configuration allows you to manually add remote printers to your machine. This, of course, is the most labor intensive way of adding printers, but it does give you the advantage of only adding the printers to the machine that makes sense (the printer is within the general vicinity).
Selecting the Connection Type and Configuring a Client Only Machine
Configuring CUPS to Listen to Broadcasts and Adjusting CUPS Permissions to Allow Broadcasts
Configuring a Connection to a Remote Queue and Configuring that Queue
|
Purchase "Deploying Suse Linux Enterprise Server" at Lulu.com |
