Cups network printer inop after SUSE 10.0 to 10.2

destiny200 · 04-12-2007, 04:02 PM

The printer is connected to the server and will print OK. But no other machine on the network has access. All other functions of the network work fine. (nfs and router) I used yast to configure the printer in 10.0 and had no problems at all. In fact it was very easy. But thats not the case in 10.2.

I removed and reinstalled printers on both server and laptop after update.
Any ideas why yast doesn't work in 10.2?

Thanks
Steven

Here is information on the system.

Firewall = Internal zone is unprotected. All ports are open on the server and laptop.

Telnet 10.8.8.6 631 from laptop gives me

(telnet to address 10.8.8.6 connection refused.)

10.8.8.6 is the server static ip address for the network.

Server rccups status = running

server cupsd.conf =

# "$Id: cupsd.conf.in 5454 2006-04-23 21:46:38Z mike $"
#
# Sample configuration file for the Common UNIX Printing System (CUPS)
# scheduler. See "man cupsd.conf" for a complete description of this
# file.
#

# Log general information in error_log - change "info" to "debug" for
# troubleshooting...
LogLevel info

# Administrator user group...
SystemGroup sys root

# Only listen for connections from the local machine.
Listen localhost:631
Listen /var/run/cups/cups.sock

# Show shared printers on the local network.
Browsing On
BrowseOrder allow,deny
BrowseAllow @LOCAL

# Default authentication type, when authentication is required...
DefaultAuthType Basic

# Restrict access to the server...
<Location />
Order allow,deny
Allow From localhost
Allow From 127.0.0.2
</Location>

# Restrict access to the admin pages...
<Location /admin>
Encryption Required
Order allow,deny
Allow From localhost
</Location>

# Restrict access to configuration files...
<Location /admin/conf>
AuthType Basic
Require user @SYSTEM
Order allow,deny
Allow From localhost
</Location>

# Set the default printer/job policies...
<Policy default>
# Job-related operations must be done by the owner or an adminstrator...
<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 CUPS-Move-Job>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>

# All administration operations require an adminstrator to authenticate...
<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>
AuthType Basic
Require user @SYSTEM
Order deny,allow
</Limit>

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

<Limit All>
Order deny,allow
</Limit>
</Policy>

#
# End of "$Id: cupsd.conf.in 5454 2006-04-23 21:46:38Z mike $".

comprookie2000 · 04-15-2007, 02:26 PM

I think this is the part to edit;

Code:

# Restrict access to the server...
<Location />
  Order allow,deny
  Allow localhost
  Allow 192.168.0.*
</Location>

restart cups once you open it up for your lan.

Quakeboy02 · 04-15-2007, 02:38 PM

In general, it's better to manage your CUPS printers from here: http://localhost:631/