Re: how to access remote CUPS printer?

On Mon, 2006-09-25 at 07:29 +0930, Tim wrote:
Michael Hennebry wrote:
How do I print to a remote CUPS printer
from machines on which I am not root?
On the remote machine, FC5, I am root.
On the clients, FreeBSD and FC3, I am not root,
but can open TCP ports.
Is there a nonroot IPP client that can
be used to print on a remote printer?

I think we need to know what's meant by "remote". Another device on the
local network? Something on a distant network? Over the internet?


Amadeus W. M.:
On the CUPS server you must make the print queues shared. The clients'
CUPS will automatically see the shared queues on the network.

On the server, go to System->Administration->Printing, click on the
queue you want to share, then Edit, etc.

Oh, and you must have port 631 tcp and udp open on the CUPS server.

Aaron Konstam:
That is absolutely the wrong way to share printers using CUPS. All
printers on the same lan as the server can print to the server's
printers by default. No configuration is required.

Amadeus W. M.:
And exactly why is it absolutely wrong? It works flawlessly on
my lan. And in fact if I don't make the queues shared on the CUPS
server, they are not automatically seen by the clients.

I wonder if the situation gets confused if one's printing through CUPS
via Samba? I found that to be a right disaster.

But ignoring Samba, if you configure a printer with CUPS (using the
webpage) on the machine that the printer is directly connected to, it
acts as a server for the rest of the network, by default. Automatically
advertising the fact.

When other unconfigured client PCs connect to the network, they're
informed that there's a printer, automatically by CUPS (the server, and
their local CUPS finding it), and they use it, by default,
automatically.

Alternatively, if you configure your print server using the Gnome GUI
tool (don't know about non-Gnome alternatives, I haven't tried them),
you do seem to need to fiddle with more options to get it acting as a
server for your network. It seems that the default options are more
restrictive.

Once you start manually configuring clients, they tend to stop
automatically finding other printers on your network. There's something
unreliable, here. I've systems where I can configure a local printer,
and the network printer is available as a choice. Sometimes the default
printer choice doesn't stick. Sometimes only the local printer is
found.
When the client is receiving information of printers from the server
automatically it takes extra configuration in the cupsd.conf in order
for the local printer on the client to be accessable. Unfortunately I ma
in the middle of a flooding diaster and I don't have access to the
machine where I have done this.

Personally, I got jack of the lot of those half-arsed configuration
tools. Configuring CUPS by hand editing the configuration files seems
better, you've got your options spelt out for you. The CUPS webserver
configuration doesn't let you set half the things that you could. The
Gnome GUI tool seems to make a mess of things for lots of peopl
--
I am unaware of any printer configuration that cannot be done through
the web interface (or at least lpoptions). What configuration is that?
--
Aaron Konstam <akonstam@xxxxxxxxxxxxx>

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: Small business thinking about backing up data, having a server and 2-3 users - is SBS200
    ... is networked to the Master with a crossover network cable. ... Master on the Master PC and Client on the Slave pc. ... Since this machine is a server is should handle the requests ok ... Most real firewall appliances have HTTP and SMTP proxy services that allow ...
    (microsoft.public.windows.server.sbs)
  • RE: Private addresses on public network
    ... anybody accesses those computers from an external network," -- even when the ... JavaScript delivered to the client that causes the client to retrieve ... the attacker, the request results in another JavaScript response that tells ... Moving beyond a single server ...
    (Security-Basics)