Re: [gentoo-user] CUPS remote printing drives me crazy

[Mick]

On Wednesday, 12 September 2018 16:21:14 BST Helmut Jarausch wrote:
> On 09/12/2018 03:55:16 PM, Neil Bothwick wrote:
> > On Wed, 12 Sep 2018 14:50:36 +0200, Helmut Jarausch wrote:
> > > On one machine - called SERVER - I have a USB printer which works
> > > just fine with CUPS.
> > > I've tried to make it "shared". This printer has the name
> > > USB_printer.
> >
> > > On the other machine, which has no physical printer itself, I just
> > > want to add a remote printer which
> > > uses  USB_printer on the SERVER.
> > >
> > > If I try to configure this remote printer, my first problem is its
> > > name (URL)
> > > I've tried  ipp://SERVER:631/printers/USB_printer  but when I try to
> > > print to it,
> > > I always get "printer cannot be located"

If the SERVER is a domain name, rather than an IP address, your client will 
have to be able to resolve it.  So, add it in your /etc/hosts, or use the 
server's IP address.


> > > Would anybody be so kind to share (the relevant parts) of his/her
> > > cupsd.conf on the server as well as
> > > on the client?

I used to have such a set up running here, but this was the best part of 10 
years ago and my memory is not what it used to be!  ;-)


> > Have you allowed access to the server from the local network?
> > Something
> > like this in cupsd.conf
> >
> > # Restrict access to the server...
> > <Location />
> >
> >   Order allow,deny
> >   Allow localhost
> >   Allow 192.168.1.*
> >
> > </Location>
>
> Thanks Neil,
>
> do I need this on the client machine, as well?
> (I do have it on the server machine)
>
> Helmut

No, you only need this on the server, BUT there's more you will have to set 
up.

1. Set the server in cupsd.conf to be listening for connections on the IP 
address which will be used by the client.  The default is to only listen to 
connections from localhost.

2. As Neil suggested make sure you allow PC(s) from your LAN subnet to access 
the cups server.

3. Check your firewall on the server allows connections over the corresponding 
protocol (port 631).

4. Use telnet/netcat/nmap to see if the client can access an open port 631 on 
the server.

This should get you talking to the server.

Should you still have problems printing, you can thereafter troubleshoot it in 
more detail by checking the server's cupsd logs.

Beyond simple printing you can allow access to the server's admin pages, logs 
and what have your from the client, but you may not wish to do this for 
security reasons.
-- 
Regards,
Mick