[FreeNX-kNX] Printen to private network
Alastair Johnson
alastair at solutiontrax.com
Thu Nov 9 00:57:41 UTC 2006
On Tuesday 07 November 2006 20:42, Marcel kraan wrote:
> Hello Alastair,
>
> major breaktrue!!
> Almost... there...
>
> If i do a test print with CUPS (port 10002) i get this error
>
> cupsdoprint -P 'BrotherHL1270' -J 'KDE Print Test' -H 'localhost:10002' -U
> 'marcel' -o '
> multiple-document-handling=separate-documents-uncollated-copies
> orientation-requested=3' '/opt/share/apps/kdeprint/testprint.ps'
>
>
> if i change the line into (10002/3002)
> then a popup for a login/passwd arrives.. i add the login 'marcel' and the
> nx.log passwd AND YES.... a PERFECT cups 1.1.x "printer test page"
>
> cupsdoprint -P 'BrotherHL1270' -J 'KDE Print Test' -H 'localhost:3002' -U
> 'marcel' -o '
> multiple-document-handling=separate-documents-uncollated-copies
> orientation-requested=3' '/opt/share/apps/kdeprint/testprint.ps'
I thought we had got this far before. 3002 is the server end of the tunnel to
the client. You can try manually pointing the kde print config at port 3002,
or whichever port it is on the session you try it in. Go to Print Manager,
hit 'Configure Manager' then in the 'CUPS Server' section you can change the
port. When I tried this it failed because CUPS and kde had different ideas
about how to perform AuthType Digest, but you might be luckier. If this works
for you then in nxnode function node_cupsd_setup change:
echo "Port=$NODE_CUPSD_PORT" >> "$KDE_PRINTRC"
to:
echo "Port=$port" >> "$KDE_PRINTRC"
>
> If i can change the port somewhere? or?
You should check to see if the usermode CUPS is created:
ps -ef |grep cups
If that shows a cupsd running as marcel then you have a usermode cupsd
running. There will probably also be the system cupds running as root.
If you have a usermode cupsd then manually run the lpadmin command from the
end of cmd_node_addprinter. This will either create the printer on the
usermode cupsd, or give you an error that should say why it failed.
> i have removed the nx-client on the server there is no difference.
Then the nxclient script from FreeNX is working properly ;-)
>
> Alastair Johnson wrote:
> > On Thursday 12 October 2006 23:19, Marcel kraan wrote:
> >> Thanks Alastair,
> >>
> >>
> >> I think this config is the same as the default config from the last
> >> version nx?.. except the cups 1.1.x on my Fedora core5 server
> >>
> >> But for sure if it can work.... (before is trash my yum/rpm database
> >> with --force --nodeps)
> >>
> >> - my server is at a hosting provider far away :-) on an public ip.
> >> - different thin clients need to print trough the NX server to their
> >> thinclient-printer The thin clients are in a private 192.168.1.x
> >> network.
> >>
> >> So this is possible via the ssh-tunnel?
> >
> > I have an FC3 server at a hosting provider on a public IP and clients on
> > 192.168.x.x and I have printed via the ssh tunnel using CUPS after some
> > modifications (search the archives for details). The tunnel mechanism is
> > the same so SMB should work the same way, but I haven't tried it. Martin
> > says it works for him. My post 'Printing under FC5' describes the problem
> > I had with CUPS 1.2.x which you may be able to fix - I ran out of time.
> >
> > Would yum let you downgrade by specifying the full version number of the
> > package? I've never tried. It didn't get _too_ upset when I
> > used --force --nodeps to downgrade openldap though.
> >
> >> Alastair Johnson wrote:
> >>> On Thursday 12 October 2006 21:19, Marcel kraan wrote:
> >>>> My nxserver hangs on internet at a provider in holland
> >>>>
> >>>> Is it possible to print from the terminals (samba) from a private
> >>>> network. I have setup a cups printserver at the nx server.
> >>>> I have samba and lpd running on the terminals
> >>>>
> >>>> can i print to the private network???
> >>>> i can print to the internet IP but?? direct to the terminal?
> >>>> Is this possible?
> >>>
> >>> It is possible, but you probably need to modify the nxnode script. I
> >>> think you need CUPS 1.1.x on the server (FC5 uses 1.2.x which doesn't
> >>> work with FreeNX yet) and on the client use 'Enable SSL encryption of
> >>> all traffic'. This post from the archive is the best I've seen for
> >>> getting SMB printing working:
> >>>
> >>> -----------------------------------------------------------------
> >>> Re: [FreeNX-kNX] printing
> >>> From: Martin Steigerwald <ms at teamix.de>
> >>> To: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>
> >>>
> >>> Am Dienstag, 24. Januar 2006 20:49 schrieb Alastair Johnson:
> >>>> The first problem is in the freenx nxnode script in function
> >>>> cmd_node_addprinter() which handles the addprinter request from the
> >>>> client. This has to determine the printer driver to use, so calls a
> >>>> script confusingly called nxclient. This is NOT a client! It is meant
> >>>> to replicate certain functions of the nomachine nxclient as used by
> >>>> the nxserver though, such as allowing you to select a printer driver.
> >>>> For me this printer driver selection never displayed however, so for
> >>>> testing I modified
> >>>> cmd_node_addprinter() to bypass this for testing, hardwiring it to the
> >>>> driver for my printer. Another option may be to install the nomachine
> >>>> client on the server, since it seems the freenx nxclient script checks
> >>>> for the presence of the nomachine client, and calls it if present.
> >>>> I've not tried that yet though...
> >>>
> >>> Hello,
> >>>
> >>> yes that worked. After applied the patch I described in my "freenx
> >>> problems with smb printing setup" post I got dialogs to configure my
> >>> printer driver. It needs NoMachine's nxclient on the server which is
> >>> generally a good idea, cause it provides some other features:
> >>>
> >>> 1) nice dialog window for Terminate / Suspend instead of ugly xdialog
> >>> stuff
> >>>
> >>> 2) Suspend / Terminate buttons when you move the mouse to the title bar
> >>> of the window that displays the FreeNX session.
> >>>
> >>> Well, I paste the relevant snippet here:
> >>>
> >>> -----------------------------------------------------------------------
> >>> - nxnode uses "-noautokill" as option to nxclient, but nxclient
> >>> 1.5.0-138 does not seem to support this options and displays an error
> >>> dialog instead of the intended dialog -> I removed that option (see
> >>> diff below)
> >>>
> >>> - nxnode uses lpadmin as a the user of the session, but a user doesn't
> >>> have lpadmin in its path -> I expicitely specified the path
> >>>
> >>> - $KDEHOME does not appear to be set in KDE 3.3 and thus the default
> >>> value for $KDEPRINTRC does not work anymore (/etc/nxserver/node.conf)
> >>> --> I changed it to
> >>> KDE_PRINTRC="/home/$USER/.kde/share/config/kdeprintrc" cause
> >>> KDE_PRINTRC="~/.kde/share/config/kdeprintrc" didn't work
> >>>
> >>> Okay, thats it. I can do bug reports sometimes but I wanted to post it
> >>> right now so that people who come across the same problems can Google
> >>> it.
> >>>
> >>> appserver:/# diff -u /usr/lib/nx/nxnode.dist /usr/lib/nx/nxnode
> >>> --- /usr/lib/nx/nxnode.dist 2005-10-08 19:36:07.000000000 +0200
> >>> +++ /usr/lib/nx/nxnode 2005-12-21 18:30:42.529485000 +0100
> >>> @@ -797,10 +797,10 @@
> >>> ERROR=$(PASSWD="$password" "$COMMAND_SMBMOUNT"
> >>> "//$computername/$rdir" "$HOME/$dir" -o
> >>> username="$username,ip=127.0.0.1,port=$port" 2>&1) if [ $? -eq 0 ]
> >>> then
> >>> - $PATH_BIN/nxclient -dialog ok -caption "NXServer
> >>> Message" -message "Info: Share: '//$computername/$rdir' mounted on:
> >>> '$HOME/$dir'" -noautokill -display :$display &
> >>> + $PATH_BIN/nxclient -dialog ok -caption "NXServer
> >>> Message" -message "Info: Share: '//$computername/$rdir' mounted on:
> >>> '$HOME/$dir'" -display :$display &
> >>> echo "$HOME/$dir" >>
> >>> "$USER_FAKE_HOME/.nx/C-$SERVER_NAME-$display-$sessionid/scripts/mpoint"
> >>> else
> >>> - $PATH_BIN/nxclient -dialog ok -caption "NXServer
> >>> Message" -message "Info: Share: '//$computername/$rdir' failed to
> >>> mount: $ERROR" -noautokill -display :$display &
> >>> + $PATH_BIN/nxclient -dialog ok -caption "NXServer
> >>> Message" -message "Info: Share: '//$computername/$rdir' failed to
> >>> mount: $ERROR" -display :$display &
> >>> fi
> >>> }
> >>>
> >>> @@ -830,12 +830,13 @@
> >>> DEVICE_URI="ipp://localhost:$port/printers/$printer"
> >>> NAME="$printer"
> >>> fi
> >>> - MODEL=$($PATH_BIN/nxclient -printer "$NAME" -noautokill
> >>> -display
> >>>
> >>> : $display)
> >>>
> >>> + MODEL=$($PATH_BIN/nxclient -printer "$NAME" -display :$display)
> >>> [ -z "$MODEL" -o "$MODEL" = "cancel: aborted" ] && return
> >>>
> >>> PUBLIC="-u allow:$USER"
> >>> [ "$public" == "1" ] && PUBLIC=""
> >>> - lpadmin -p "$NAME" -E -v "$DEVICE_URI" -m "$MODEL" $PUBLIC
> >>> +# Teamix: User doesn't have lpadmin in his path
> >>> + /usr/sbin/lpadmin -p "$NAME" -E -v "$DEVICE_URI" -m "$MODEL"
> >>> $PUBLIC [ "$defaultPrinter" = "1" ] && lpadmin -d "$NAME"
> >>> }
> >>> -----------------------------------------------------------------------
> >>>
> >>>
> >>>
> >>>
> >>> ________________________________________________________________
> >>> 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
> > ________________________________________________________________
More information about the FreeNX-kNX
mailing list