<br>
<br><tt><font size=2>Vivek <vivek@visolve.com> wrote on 16/10/2009
11:55:14:<br>
<br>
> Chris,<br>
> <br>
> Thanks for your reply.<br>
> <br>
> >>What cupsds are running, what ports are they listening
to.<br>
> <br>
> 1. cupsd<br>
> 2. /usr/sbin/cupsd -c /home/vivek/.nx/cups/cupsd.conf<br>
> <br>
> They are using two ports 631 and 20000<br>
> </font></tt>
<br>
<br><tt><font size=2>Good, that's the ticket . . .</font></tt>
<br>
<br><tt><font size=2><br>
> >>Did you do the -F patch or was it the distro ???<br>
> <br>
> It came with distro..<br>
> </font></tt>
<br>
<br><tt><font size=2>Good. That's what a distro is for really . . .</font></tt>
<br>
<br><tt><font size=2><br>
> >>What is in /home/vivek/.nx/cups/ppd<br>
> <br>
> iii) No ppd files under /home/vivek/.nx/cups/ppd/ and
No directory <br>
> with name cups under <br>
> /home/vivek/.nx/S-tsrv-co-2011-60D1D093D91A07B88AE13BC8606F9295/<br>
> <br>
> >>Are you running the cups wrapper on the client ???????<br>
> <br>
> Are you talking about nxcupsd-wrapper script ?. If yes, i did. i have
<br>
</font></tt>
<br><tt><font size=2>Right. </font></tt>
<br>
<br><tt><font size=2>You need the wrapper to cache the .ppd file in /home/vivek/.nx/cups/ppd</font></tt>
<br>
<br><tt><font size=2>ON THE CLIENT, so that ENABLE_CUPS_SEAMLESS can get
it from th client</font></tt>
<br><tt><font size=2>user-space cupsd.</font></tt>
<br>
<br><tt><font size=2>It's generally quicker to pass PostScript across a
wan link, often</font></tt>
<br><tt><font size=2>the data is 10x smaller then after connversion.</font></tt>
<br>
<br><tt><font size=2>> changed the variable SYSTEM_CUPSD="/usr/NX/bin/nxclient"
and tried it. <br>
> But it didn't work.<br>
> </font></tt>
<br>
<br><tt><font size=2>No, it wouldn't.</font></tt>
<br>
<br><tt><font size=2>You need to keep SYSTEM_CUPSD="/usr/sbin/cupsd"
( or where ever it is )</font></tt>
<br>
<br><tt><font size=2>in the wrapper script, but change :-</font></tt>
<br>
<br><tt><font size=2><option key=CUPSD path" value="/path/to/the/wrapper/file"
/></font></tt>
<br>
<br><tt><font size=2>in the relevant /home/vivek/.nx/config/nx-server.cfg
file</font></tt>
<br>
<br><tt><font size=2>or change(same thing) "System CUPS daemon"
under the Environment Tab</font></tt>
<br>
<br><tt><font size=2>after pressing "Configure" on the Login
screen on the NoMachine client.</font></tt>
<br>
<br>
<br>
<br><tt><font size=2>It looks to me like it's all set up. Lets try a test.</font></tt>
<br>
<br><tt><font size=2>Whilst connected . . </font></tt>
<br>
<br><tt><font size=2>On the SERVER . .</font></tt>
<br>
<br><tt><font size=2>Find which port the tunnel is using netstat -napt|grep
agent</font></tt>
<br>
<br><tt><font size=2>Typicaly 3020 or some such . . .</font></tt>
<br>
<br><tt><font size=2>Look in /home/vivek/.nx/C-sesssion-id/cups/printers.conf</font></tt>
<br><tt><font size=2>for the line which looks like :-</font></tt>
<br>
<br><tt><font size=2>DeviceURI nxipp://vivek:Copy-this-password,-don't-copy-the-@@@@-sign!!!@127.0.0.1:port/printers/LaserJet_P2015.ppd</font></tt>
<br>
<br><tt><font size=2>The :port after 127.0.0.1 should be the one the agent
is listening on.</font></tt>
<br>
<br><tt><font size=2>This will allow you to point a browser at http:/localhost:put-whatever-the-tunnel-port-is-in-here
</font></tt>
<br><tt><font size=2>and log in OVER THE TUNNEL to the client user-space
cups web interface</font></tt>
<br><tt><font size=2>using Username vivek and password the password you
just copied 6 lines up</font></tt>
<br><tt><font size=2>from the printer.conf file ( missing out the @ sign
).</font></tt>
<br>
<br><tt><font size=2>Under the Printers Tab on the Cups web interface,
you should see:- </font></tt>
<br>
<br><tt><font size=2>the LaserJet_P2015 with "Make and Model:"
set to "Local Raw Printer" </font></tt>
<br><tt><font size=2>and "Device URI:" set to "</font></tt><a href=http://127.0.0.1:631/printers/LaserJet_P2015><tt><font size=2>http://127.0.0.1:631/printers/LaserJet_P2015</font></tt></a>
<br>
<br><tt><font size=2>If you now print from the session, you should see
the job appearing under the jobs tab or not.</font></tt>
<br>
<br><tt><font size=2>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.</font></tt>
<br>
<br><tt><font size=2>The job should re-spool onto THE CLIENT into /home/vivek/.nx/cups/spool/</font></tt>
<br>
<br><tt><font size=2>Jobs remain here even after the remote session has
been closed and restarted, </font></tt>
<br><tt><font size=2>so if anything has spooled ever. you should see a
Cxxxxx control file for it, </font></tt>
<br><tt><font size=2>and if it hasn't printed a dxxxxx data file also.</font></tt>
<br>
<br><tt><font size=2>This causes some surprises for users connecting up
printers, not to mention</font></tt>
<br><tt><font size=2>security issues.</font></tt>
<br>
<br><tt><font size=2>Note The user cupsd doesn't start until you try to
connect remotely.</font></tt>
<br>
<br>
<br>
<br><tt><font size=2><br>
> <br>
> Thanks<br>
> Vivek<br>
> <br>
> ________________________________________________________________<br>
> Were you helped on this list with your FreeNX
problem?<br>
> Then please write up the solution in the FreeNX Wiki/FAQ:<br>
> <br>
> </font></tt><a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ"><tt><font size=2>http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</font></tt></a><tt><font size=2><br>
> <br>
> Don't forget to check the NX Knowledge
Base:<br>
> </font></tt><a href=http://www.nomachine.com/kb/><tt><font size=2>http://www.nomachine.com/kb/</font></tt></a><tt><font size=2>
<br>
> <br>
> ________________________________________________________________<br>
> FreeNX-kNX mailing list --- FreeNX-kNX@kde.org<br>
> </font></tt><a href="https://mail.kde.org/mailman/listinfo/freenx-knx"><tt><font size=2>https://mail.kde.org/mailman/listinfo/freenx-knx</font></tt></a><tt><font size=2><br>
> ________________________________________________________________<br>
</font></tt>