[FreeNX-kNX] redhat + cups + client printing

Alastair Johnson alastair at solutiontrax.com
Fri Sep 29 09:15:51 UTC 2006


Hi Bob,

Printing on FreeNX doesn't yet work out of the box, but can usually(?) be made 
to work. Printing on a nomachine NX server should work out of the box 
(provided the cups setup on the server works). From the path to your config 
file I'm guessing you're using the nomachine server. If this is the case then 
nomachine may be a better source of support. If you're using FreeNX then we 
will need to know the versions of the client, the FreeNX and the RedHat 
install.

Your description of how it works is more or less right. The client is 
configured for cups printing. It creates a new printer in CUPS which prints 
to the one it is sharing, but is restricted by username and a random password 
which it only tells the server about. The server then creates a new printer 
in CUPS which points back to the one shared by the client. The exact 
mechanism for this is different in nomachine's server and FreeNX but the 
effect is the same. The user prints to the CUPS printer configured on the 
server, which passes it aling the chain until it finally reaches the printer 
that was originally shared.

If your client machine and your NX server can both see the same external CUPS 
server there seems little point using the print forwarding. It is only really 
useful if you want to print to a printer the client can print to, but the 
server normally can't.


On Thursday 28 September 2006 15:29, bob flynn wrote:
> Hi,
>
> I am trying to enable printer support for cups on a red hat system for nx
> clients.
>
> Currently I have an NX server running fine, its the print support through
> nx which I am stumbling at.
>
> I understand the that*_
> _*
> The ENABLE_CUPS_SUPPORT key must be activated in the /usr/NX/etc/node.cfg
> configuration file:
>
> ENABLE_CUPS_SUPPORT = "1"
>
> and then;
>
> Set the following key in the /usr/NX/etc/node.cfg configuration file to fit
>
>
> CUPS_BACKEND_PATH = "/usr/lib/cups/backend"
> CUPS_BIN_PATH = "/usr/bin"
> CUPS_SBIN_PATH = "/usr/sbin"
>
> The above is taken from a nx systems admin manual.
>
> My question is relating to this bit;
>
> CUPS_BACKEND_PATH = "/usr/lib/cups/backend"
>
> on my system, this shows;
>
> nx_server> pwd
> /usr/lib/cups
> nx_server> ls
> filter
>
> So, should I be looking elsewhere for this ?
>
> A brief overview of the configuration.
>
> NX server is also cups client
> Cups server is a separate machine providing the cups info
> The nx server simply runs a cups client which talks to the cups server to
> get the available printers.
>
> I am abit confused as to what the configuration should be. My understanding
> is;
>
> 1. From a unix/linux client which can see a cups printer, run nxclient and
> enable printing. 2. This should be passed to the nx server, which sets up a
> dummy cups printer, which redirects back to the nx client ?
>
> Any help would be appreciated.
>
> -Bob
>
>
>
>
> The information contained in this e-mail and in any attachments is
> confidential and is designated solely for the attention of the intended
> recipient(s). If you are not an intended recipient, you must not use,
> disclose, copy, distribute or retain this e-mail or any part thereof. If
> you have received this e-mail in error, please notify the sender by return
> e-mail and delete all copies of this e-mail from your computer system(s).
> Please direct any additional queries to: communications at s3group.com. Thank
> You.




More information about the FreeNX-kNX mailing list