Setting Up a Simple Print Server on the Local Network

If you have successfully set up a printer on the local machine, you have also successfully set up a print server for the local network. The SUSE default settings in the CUPS configuration file /etc/cups/cupsd.conf ensure this. In the Browsing Options section of /etc/cups/cupsd.conf, this is controlled by the lines:

BrowseAllow @LOCAL BrowseDeny All

The CUPS server advertises itself on the local network and is ready to accept jobs from other machines after they have been set up correctly to print to it. Of course, you can change this behavior if you want to, but for the time being we assume that you have the default configuration on the machine that has the printer attached.

In this example, the printer is attached to the machine hatter, and we are setting up printing on another SUSE Linux machine. Do the following:

1. Start the YaST printer module. If no printers have been set up before, and no local printers are detected, choose Add. You will now see a screen where you choose between adding local or network printers. Choose Network Printers and a dialog appears, similar to the one in Figure 19-5.

2. Select Print via CUPS Network Server and then, in the next screen, choose the CUPS Client-Only configuration. You will be asked to give the server name, as shown in Figure 19-6 (or you can allow YaST to detect it, or choose it from a list of all hosts on the network).

3. After you have clicked OK and Finish, you should be able to print across the network to the printer attached to the server named hatter.

Part IV

FIGURE 19-5

Choosing a printer type: remote CUPS server

FIGURE 19-5

Choosing a printer type: remote CUPS server

FIGURE 19-6

Setting up the remote CUPS server in YaST

FIGURE 19-6

Setting up the remote CUPS server in YaST

Starting and Stopping the CUPS Server

On SUSE, CUPS is started and stopped by the commands rccups start and rccups stop. It is just another service controlled in the usual way. If you make changes to the CUPS configuration files, you will need to restart CUPS for the changes to take effect.

You can check that CUPS is running with the command rccups status. By default, CUPS will be started in runlevels 2,3, and 5.

Checking That the Remote CUPS Server Is Available

From the client machine, you may want to be sure that CUPS is running on the server and available across the network. As with other services, you can check this by seeing if you can connect to the relevant port, using a command like:

telnet hatter 631

If you see output like this, CUPS is available across the network:

Trying 192.168.2.6 ... Connected to hatter. Escape character is '"]'.

Now use Ctrl+] and type quit to disconnect.

If there is a problem you may see this:

telnet: connect to address 192.168.2.6: Connection refused

Such code appears for a number of reasons: There could be a problem with the network, CUPS might not be running, or there could be a firewall rule on hatter blocking the connection.

Was this article helpful?

0 0

Post a comment