<br><tt><font size=2>Antoine Martin <antoine@nagafix.co.uk> wrote
on 29/09/2009 09:39:21:<br>
<br>
> Hi,<br>
> <br>
> I am trying to figure out how NX does the printer forwarding.</font></tt>
<br>
<br><tt><font size=2>Well . . .</font></tt>
<br>
<br><tt><font size=2>It uses an ssh tunnel which redirects a port on the
FreeNX server back to the workstation, so you can then connect to a port
on the WS :631 or :445, via the redirected port.</font></tt>
<br>
<br>
<br><tt><font size=2>> How does it tell the client sessions to connect
to a different printer<br>
> on the fly when the client connects from a different location?<br>
</font></tt>
<br>
<br><tt><font size=2>FreeNX runs a separate cups printer daemon for each
user, which it configures with the printer/queue identified by .
. .</font></tt>
<br>
<br><tt><font size=2>1/ the printer name on the workstation, as configured
on the workstation cups daemon if the workstation is NIX or the printer
share if the WS is windows</font></tt>
<br><tt><font size=2>2/ the port on the server which is redirected to the
workstation, via which the user cupsd spools</font></tt>
<br><tt><font size=2>3/ the printer/share name and the login details (
for connecting back to the workstation ) which are set up in the NX client,
and passed over during connection</font></tt>
<br><tt><font size=2>4/ a .ppd driver file to correspond to the printer's
MODEL, which FreeNX asks the user to select because it can't (well, doesn't
anyway) tell just from the printer name.</font></tt>
<br>
<br>
<br><tt><font size=2>> Can it be done/is it done without samba?<br>
> <br>
</font></tt>
<br>
<br><tt><font size=2>Samba (smb:// smbspool)is used if the WS is windows
or NIX configured with smbspool printing to a samba share.</font></tt>
<br>
<br><tt><font size=2>ipp:// is used if the WS is running cupsd ie a NIX
WS.</font></tt>
<br>
<br>
<br><tt><font size=2>Basic printing stuff which you should know already
. . .</font></tt>
<br>
<br><tt><font size=2>For a Postscript printer, the user cupsd, using the
normal .ppd driver, passes Postscript on to the remote printer, which does
a raw dump to the printer, ie it doesn't process again.</font></tt>
<br>
<br><tt><font size=2>For a non Postscript (ie. windows) printer, the user
cupsd .ppd driver causes cupsd to pass the postscript print job through
a postscript to windows printing converter ( automagically ) then on to
the remote printer, again you need a raw dump to the printer, which windows
does automatically but smbd needs to have configured.</font></tt>
<br>
<br>
<br><tt><font size=2>> Can anyone point me to some documentation?</font></tt>
<br>
<br>
<br><tt><font size=2>No ! Did you not try Google.</font></tt>
<br>
<br><tt><font size=2><br>
> I would like to understand the mechanism, and emulate it using simple<br>
> scripts. (I am not interested in using it via NX, rather I want to<br>
</font></tt>
<br>
<br><tt><font size=2>You need a print share on the windows workstation
or a cups printer set up on the NIX workstation.</font></tt>
<br>
<br><tt><font size=2>You need to set up a reverse tunnel from the workstation
to a port on the NIX server. Use Openssd on a NIX WS or cygwin's Openssh
on windows WS.</font></tt>
<br>
<br><tt><font size=2>For a NIX workstation, you need to set up an ipp printer
(typically) in cups on the server, pointing via the re-directed port to
the workstation.</font></tt>
<br>
<br><tt><font size=2>For a windows WS you need an smb printer set up in
cups on the server, which uses smbspool to connect via the redirected port
to the print share on the workstation after the .ppd file has kicked off
PS to Windows conversion.</font></tt>
<br>
<br>
<br><tt><font size=2>> understand it/test it by hand).<br>
></font></tt>
<br>
<br>
<br><tt><font size=2>Good luck !!</font></tt>
<br>
<br>
<br><tt><font size=2>Note, there is quite a bit more to FreeNX printing,
( the bit you are not interested in ), and some of the windows printing
is a bit creacky.</font></tt>
<br>
<br><tt><font size=2>The FreeNX authors did a sizable amount of work though
overall !!! and I dread to think how much time they have spent . . .</font></tt>
<br><tt><font size=2> <br>
</font></tt>
<br><tt><font size=2>> Thanks<br>
> Antoine<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>