Source string Read only

(itstool) path: sect2/para
Context English State
If the <application>CUPS</application> clients have difficulty finding other <application>CUPS</application> printers shared across the network, sometimes it is helpful to add or create a file <filename>/usr/local/etc/cups/client.conf</filename> with a single entry as follows:
ServerName <replaceable>server-ip</replaceable>
In this case, <replaceable>server-ip</replaceable> would be replaced by the local <acronym>IP</acronym> address of the <application>CUPS</application> server on the network.
<trademark class="registered">Windows</trademark> Clients
Versions of <trademark class="registered">Windows</trademark> prior to XP did not have the capability to natively network with <acronym>IPP</acronym>-based printers. However, <trademark class="registered">Windows</trademark> XP and later versions do have this capability. Therefore, to add a <application>CUPS</application> printer in these versions of <trademark class="registered">Windows</trademark> is quite easy. Generally, the <trademark class="registered">Windows</trademark> administrator will run the <trademark class="registered">Windows</trademark> <literal>Add Printer</literal> wizard, select <literal>Network Printer</literal> and then enter the <acronym>URI</acronym> in the following syntax:
If one has an older version of <trademark class="registered">Windows</trademark> without native <acronym>IPP</acronym> printing support, then the general means of connecting to a <application>CUPS</application> printer is to use <package>net/samba410</package> and <application>CUPS</application> together, which is a topic outside the scope of this chapter.
CUPS Troubleshooting
Difficulties with <application>CUPS</application> often lies in permissions. First, double check the <citerefentry><refentrytitle>devfs</refentrytitle><manvolnum>8</manvolnum></citerefentry> permissions as outlined above. Next, check the actual permissions of the devices created in the file system. It is also helpful to make sure your user is a member of the <systemitem class="groupname">cups</systemitem> group. If the permissions check boxes in the Administration section of the <application>CUPS</application> web interface do not seem to be working, another fix might be to manually backup the main <application>CUPS</application> configuration file located at <filename>/usr/local/etc/cups/cupsd.conf</filename> and edit the various configuration options and try different combinations of configuration options. One sample <filename>/usr/local/etc/cups/cupsd.conf</filename> to test is listed below. Please note that this sample <filename>cupsd.conf</filename> sacrifices security for easier configuration; once the administrator successfully connects to the <application>CUPS</application> server and configures the clients, it is advisable to revisit this configuration file and begin locking down access.
# Log general information in error_log - change "info" to "debug" for
# troubleshooting...
LogLevel info

# Administrator user group...
SystemGroup wheel

# Listen for connections on Port 631.
Port 631
#Listen localhost:631
Listen /var/run/cups.sock

# Show shared printers on the local network.
Browsing On
BrowseOrder allow,deny
#BrowseAllow @LOCAL
BrowseAllow 192.168.1.* # change to local LAN settings
BrowseAddress 192.168.1.* # change to local LAN settings

# Default authentication type, when authentication is required...
DefaultAuthType Basic
DefaultEncryption Never # comment this line to allow encryption

# Allow access to the server from any machine on the LAN
&lt;Location /&gt;
Order allow,deny
#Allow localhost
Allow 192.168.1.* # change to local LAN settings

# Allow access to the admin pages from any machine on the LAN
&lt;Location /admin&gt;
#Encryption Required
Order allow,deny
#Allow localhost
Allow 192.168.1.* # change to local LAN settings

# Allow access to configuration files from any machine on the LAN
&lt;Location /admin/conf&gt;
AuthType Basic
Require user @SYSTEM
Order allow,deny
#Allow localhost
Allow 192.168.1.* # change to local LAN settings

# Set the default printer/job policies...
&lt;Policy default&gt;
# Job-related operations must be done by the owner or an administrator...
&lt;Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs \
Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription \
Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job \
Require user @OWNER @SYSTEM
Order deny,allow

# All administration operations require an administrator to authenticate...
&lt;Limit Pause-Printer Resume-Printer Set-Printer-Attributes Enable-Printer \
Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs \
Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer \
Promote-Job Schedule-Job-After CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class \
CUPS-Delete-Class CUPS-Accept-Jobs CUPS-Reject-Jobs CUPS-Set-Default&gt;
AuthType Basic
Require user @SYSTEM
Order deny,allow

# Only the owner or an administrator can cancel or authenticate a job...
&lt;Limit Cancel-Job CUPS-Authenticate-Job&gt;
Require user @OWNER @SYSTEM
Order deny,allow

&lt;Limit All&gt;
Order deny,allow



New source string

FreeBSD Doc / articles_cupsEnglish

New source string 5 months ago
Browse all component changes


English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: sect2/para
No labels currently set.
Source string location
Source string age
5 months ago
Translation file
, string 45