You are not logged in.

#1 2013-01-14 01:20:11

ghborrmann
Member
Registered: 2012-05-01
Posts: 9

Network Computer Can't See My CUPS Printer

I've installed my printer, and tried to follow the CUPS printer sharing wiki, but I haven't been able to get another computer to list it as a network printer.  My printer (a HP LaserJet 1200) installed successfully on my up-to-date Arch Linux system,   and prints normally.  The cups and cups-browsed daemons have been enabled and are running.  I have another Linux computer on my network running Fedora 17.  When I go to the CUPS page (localhost:631) it does not show the Arch Linux printer.  Running "nmap 192.168.1.0/24" on the Fedora computer shows the ArchLinux machine, but reports that all 1000 ports are closed.

My research on this issue has identified that there was a major change going from cups 1.5 to cups 1.6, affecting printer discovery.  I note that ArchLinux is running cups 1.6.1-6, while Fedora has cups 1.5.4-11, so this may be related to my problem.  However, I don't think it is normal for all ports to be closed.  I have modified the cupsd.conf file to allow 192.168.1.*, but is there more I have to do to enable communication between the computers?

Any suggestions would be appreciated.

Offline

#2 2013-01-14 01:28:58

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: Network Computer Can't See My CUPS Printer

I haven't been able to get my Arch machine (cups 1.6) to see networked printers still running 1.5.

For a while I downgraded to 1.5, but that wasn't sustainable. Now I am harassing the sysadmins to upgrade to 1.6 because older cups clients can still connect to the newer version, it just doesn't work the other way...


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2013-01-14 19:34:26

ghborrmann
Member
Registered: 2012-05-01
Posts: 9

Re: Network Computer Can't See My CUPS Printer

jasonwryan wrote:

... older cups clients can still connect to the newer version, it just doesn't work the other way...

You  seem to be saying that it should work in my case: an older cups client attempting to connect to the newer version on my server.  In that case, there must be something else wrong with my configuration.  Is it normal for port 631 to appear closed from a client computer?

Offline

Board footer

Powered by FluxBB