[FreeNX-kNX] Printing issue - Fedora 11

Fri Oct 16 11:51:57 UTC 2009

Vivek <vivek at visolve.com> wrote on 16/10/2009 11:55:14:

> Chris,
> 
> Thanks for your reply.
> 
>  >>What cupsds are running, what ports are they listening to.
> 
> 1. cupsd
> 2. /usr/sbin/cupsd -c /home/vivek/.nx/cups/cupsd.conf
> 
> They are using two ports  631 and 20000
> 

Good, that's the ticket . . .

>  >>Did you do the -F patch or was it the distro ???
> 
> It came with distro..
> 

Good. That's what a distro is for really . . .

>  >>What is in /home/vivek/.nx/cups/ppd
> 
> iii) No ppd files under  /home/vivek/.nx/cups/ppd/  and No directory 
> with name cups under 
> /home/vivek/.nx/S-tsrv-co-2011-60D1D093D91A07B88AE13BC8606F9295/
> 
>  >>Are you running the cups wrapper on the client ???????
> 
> Are you talking about nxcupsd-wrapper script ?. If yes, i did. i have 

Right. 

You need the wrapper to cache the .ppd file in /home/vivek/.nx/cups/ppd

ON THE CLIENT, so that ENABLE_CUPS_SEAMLESS can get it from th client
user-space cupsd.

It's generally quicker to pass PostScript across a wan link, often
the data is 10x smaller then after connversion.

> changed the variable SYSTEM_CUPSD="/usr/NX/bin/nxclient" and tried it. 
> But it didn't work.
> 

No, it wouldn't.

You need to keep SYSTEM_CUPSD="/usr/sbin/cupsd"  ( or where ever it is )

in the wrapper script, but change :-

<option key=CUPSD path" value="/path/to/the/wrapper/file" />

in the relevant /home/vivek/.nx/config/nx-server.cfg  file

or change(same thing) "System CUPS daemon" under the Environment Tab

after pressing "Configure" on the Login screen on the NoMachine client.

It looks to me like it's all set up. Lets try a test.

Whilst connected . . 

On the SERVER . .

Find which port the tunnel is using netstat -napt|grep agent

Typicaly 3020 or some such . . .

Look in /home/vivek/.nx/C-sesssion-id/cups/printers.conf
for the line which looks like :-

DeviceURI 
nxipp://vivek:Copy-this-password,-don't-copy-the-@@@@-sign!!!@127.0.0.1:port/printers/LaserJet_P2015.ppd

The :port after 127.0.0.1 should be the one the agent is listening on.

This will allow you to point a browser at 
http:/localhost:put-whatever-the-tunnel-port-is-in-here 
and log in OVER THE TUNNEL to the client user-space cups web interface
using Username vivek and password the password you just copied 6 lines up
from the printer.conf file ( missing out the @ sign ).

Under the Printers Tab on the Cups web interface, you should see:- 

the LaserJet_P2015 with "Make and Model:" set to "Local Raw Printer" 
and "Device URI:" set to "http://127.0.0.1:631/printers/LaserJet_P2015

If you now print from the session, you should see the job appearing under 
the jobs tab or not.

This will tell us where the stop is occuring eg you might not get as far 
as the web interface over the tunnel or your spooling might not be 
allowed. You can now check the cupsd error log to tell us what is 
happening.

The job should re-spool onto THE CLIENT into /home/vivek/.nx/cups/spool/

Jobs remain here even after the remote session has been closed and 
restarted, 
so if anything has spooled ever. you should see a Cxxxxx control file for 
it, 
and if it hasn't printed a dxxxxx data file also.

This causes some surprises for users connecting up printers, not to 
mention
security issues.

Note The user cupsd doesn't start until you try to connect remotely.

> 
> Thanks
> Vivek
> 
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
> 
> 
http://openfacts2.berlios.de/wikien/index.php/BerliosProject: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
> ________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20091016/c67ba541/attachment.html>