[FreeNX-kNX] cant get working remote printing

[chris at ccburton.com]

Eric Bazzana <ebazzana at gmail.com> Sent by: freenx-knx-bounces at kde.org
Please respond toUser Support for FreeNX Server and kNX Client 
<freenx-knx at kde.org>


sorry, first mail get wrong.

Hello, im trying to get working remote printing and cant do it. 
I have a linux server, with free-nx NXSERVER - Version 3.2.0-74-SVN OS 
(GPL, using backend: 3.4.0)
Client machine is Windows XP, with NoMachine NX Client version 3.5.0-7.
I have a printer on client machine working and shared.

When i start de client on WinXP, go to "configure" -> "Services" -> "Add" 
-> select printer, and set user/pass of an account on WinXp.

Start client session, printer is configured and CUPS server is running. I 
go to CUPS admin page, and "Print Test Page", job is bloqued 
with "Connection failed: NT_STATUS_CONNECTION_REFUSED".

After enable logging capabilities, i see in error_log of CUPS:
D [22/Aug/2012:02:13:55 -0300] [Job 1] + exec /usr/lib/cups/backend/smb 
smb://natyeric:pass@127.0.0.1:445/PDFCreator 1 anonymous 'Test Page' 1 
'job-uuid=urn:uuid:4963ba7e-5e2b-3b2d-5366-51a65e024647 
job-originating-host-name=localhost time-at-creation=1345612435 
time-at-processing=1345612435' 
/home/hp/.nx/C-hp-american-2003-0698DF717CB9B4B752BB11977B64DF6E/cups/spool/d00001-001

E [22/Aug/2012:02:13:55 -0300] [Job 1] Connection failed: 
NT_STATUS_CONNECTION_REFUSED

D [22/Aug/2012:02:13:55 -0300] [Job 1] Set job-printer-state-message to 
"Connection failed: NT_STATUS_CONNECTION_REFUSED", current level=ERROR

but if run /usr/lib/cups/backend/smb smb://
natyeric:amor at 127.0.0.1:445/PDFCreator 1 anonymous 'Test Page' 1 
'job-uuid=urn:uuid:4963ba7e-5e2b-3b2d-5366-51a65e024647 
job-originating-host-name=localhost time-at-creation=1345612435 
time-at-processing=1345612435' 
/home/hp/.nx/C-hp-american-2003-0698DF717CB9B4B752BB11977B64DF6E/cups/spool/d00001-001 
in a terminal, the print job is sent, and gets printed on WinXP client 
machine.

someone has any tip to get this working.
thanks, Eric.


smb printing can be quite "entertaining" . . . .


Recently we've had to set ( some of us anyway)
        use client driver = Yes
in the printer's stanza in smb.conf to get remote smb spooling working 
again,
BUT
that's to samba on the workstation, tho' it gave the same 
NT_STATUS_CONNECTION_REFUSED error message !?!?!?

So. . . 

A/ (looking for obvious points)

I don't see the same lines in my logs as you post from yours.
but
I note the "pass"  for the password in your "cups" log differs from the 
"amor" in the second example on the command line
so
unless your logging is managing to filter and anonymize passwords in an 
smb uri
or
you have only changed one of them manually before posting
then
there is a password mismatch.



B/ (trying to think how one would work and the other not)

Remote nxsmb printing re-directs :445 to the nxagent "tunnel" port using 
libnxredir.so.0
then
smb spools (eventually) to  the re-directed :445


It's possible to set this redirection for the whole nx session using
        ENABLE_SAMBA_PRELOAD=1
in node.conf ( but I don't know if it works, cos I don't use it )
so
if you've done that then the 
        /usr/bin/smbspool
which
        /usr/lib/cups/backend/smb
links to should connect to the nxagent "tunnel" port and spool over the 
tunnel
but
if you haven't set this and port 445 is to samba on your Linux machine and 
haven't used nxsmb or LD_PRELOAD to load the .so
then
if you are using a test environment, you might be spooling to your 
workstation printer via samba 
i.e.
 outside the nxagent tunnel (which used to be the recomended method a few 
years ago for local eg. USB printers, tho' its not much use remotely)
which
might explain why it works that way.

. . . .  else I can't think of any reason why it would work one way and 
not the other
and
I can spool to xp just fine . . . .








-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20120724/86910923/attachment.html>