[FreeNX-kNX] Client-side CUPS printing

[Alastair Johnson]

On Monday 05 November 2007, Prakash Velayutham wrote:
> Hello Fabian,
>
> Which port numbers get opened on the server and client-side for
> printing?

Many and varied ;-) This may have changed since I last looked at it, but IIRC 
it's:
Client port 631 - your existing local CUPS
Client port 20000ish, cupsd started by nxclient on the client, port forwarded 
to 2000+display (usually 3000ish) on the server
Server port 9000+display (usually 10000ish) cupsd on server started by nxnode 
in response to client's addprinter request

This was back with 1.5 series clients, and before Fabian updated the printing, 
but it looks valid from a quick glance at node.conf

> Now I see that a cups daemon starts up on the client-side with 20000
> port. But on the server side, I am not positive what port I should
> check for, and how the printers should be checked and configured.
>
> Based on some other thread, I changed my CUPS printing configuration
> on the server-side to listen to localhost:3000 and that asks me for a
> username/password now. I am giving my client-side username/password
> there, but it keeps coming back with the same dialog over and over.
> Could you please explain how that is to be done?

IIRC, and if it hasn't changed, port 3000 on the server is a tunnel to a cupsd 
on the client started by nxclient. It uses a random password that's announced 
to the server in the session setup but doesn't usually find its way into the 
logs. Check the $password variable in node_cmd_addprinter in the nxnode 
script.

> Thanks,
> Prakash
>
> On Nov 4, 2007, at 9:53 AM, Fabian Franz wrote:
> >> This link says officially "RunAsUser" support was removed in 1.2.
> >> Isn't this the option that enables usermode cupsd? Or am I confused?
> >
> > Nope, you are confused ;-).
> >
> > RunAsUser is an option to have cupsd running as root be run as
> > another user like lp as far as I understood.
> >
> >> Regardless, I have changed the NXClient CUPS daemon location (thanks
> >> for the pointer) to the wrapper script, but when I start up the
> >> connection, it still complains with "cupsd: Child exited with status
> >> 127".
> >
> > Hm, strange. I dunno what this means, but you can startup the cupsd-
> > wrapper script yourself with the cupsd.conf:
> >
> > ./nxcupsd-wrapper -c $HOME/.nx/cups/cupsd.conf
> >
> > You can also find log files in that directory, that could give you
> > additional pointers.
> >
> > cu
> >
> > Fabian
> > ________________________________________________________________
> >     Were you helped on this list with your FreeNX problem?
> >    Then please write up the solution in the FreeNX Wiki/FAQ:
> >  http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
> >         Don't forget to check the NX Knowledge Base:
> >                 http://www.nomachine.com/kb/
> >
> > ________________________________________________________________
> >       FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
> >      https://mail.kde.org/mailman/listinfo/freenx-knx
> > ________________________________________________________________
>
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
>   http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com/kb/
>
> ________________________________________________________________
>        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>       https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________