[FreeNX-kNX] NX printing through port 445

Prakash Velayutham prakash.velayutham at cchmc.org
Mon Dec 10 20:46:18 UTC 2007


Wonderful folks. It is finally working.

Here is a gist of what all had to be done, in case someone else is  
interested.

* Samba had to be recompiled (source file $SAMBA_ROOT/source/libsmb/ 
cliconnect.c). Just change the occurrence of "cli->port == 445" to  
"cli->port != 139" (around line 1337). Thanks to Fabian for this.

Do we tell someone in Samba team about this?

This was required as I was trying to use 445 instead of the default  
139 port on the client-side. Looks like forwarding port 139 alone does  
not work in some networks like mine, but 445 alone works fine.

* Change COMMAND_SMBMOUNT and COMMAND_SMBUMOUNT to refer to the newly  
built smbmount and smbumount execs.

* In /usr/lib/cups/backend, change the link of "smb" to smbspool in  
the newly built samba.

* In SuSE 10.2 (I do not know of the other distros), even if you  
install the FreeNX (0.7.1-1.1) RPM, the NX_VERSION string in /usr/bin/ 
nxloadconfig file gets set as 1.5.0-70. Just change this manually.

* I have the following changes in the default node.conf file in my  
servers, which seems to work fine now.

ENABLE_KDE_CUPS="1"
KDE_PRINTRC="$KDEHOME/share/config/kdeprintrc"
ENABLE_CUPS_SERVER_EXPORT="1"

I think that is it. Now printing works just fine inside the NX session.

Special thanks to Fabian.

Prakash

On Dec 10, 2007, at 11:58 AM, Alastair Johnson wrote:

> On Monday 10 December 2007, Prakash Velayutham wrote:
>> Hi Fabian,
>>
>> Once again, thanks.
>>
>> On Dec 10, 2007, at 11:05 AM, Fabian Franz wrote:
>>>> Hi,
>>>>
>>>>>> Here is all the client-side logs.
>>>>
>>>> Attached are the files.
>>>
>>> HELLO NXSERVER - Version 1.5.0-70 OS (GPL)]
>>>
>>> So your nxserver is putting itself as 1.5.0-70.
>>>
>>> And in runlog we can find the message: "Server does only support
>>> SAMBA forcing port 139." There yo uahve it.
>>>
>>> It needs to read 2.1.0-71, because that (choose of protocol) is why
>>> I bumped the version number to 2.1.0.
>>
>> I get this on the server, though.
>>
>> mannose:~ # rpm -qa | grep NX
>> NX-2.1.0-127.1
>> FreeNX-0.7.1-1.1
>> mannose:~ #
>>
>> Should I just remove and reinstall both NX and FreeNX?
>
> This should be set in nxloadconfig:
> NX_VERSION=2.1.0-71
>
> I know the RPMs have some aspects of nxloadconfig changed from the  
> normal
> values so things work smoothly on the distro. This one may be a  
> historical
> mistake, or may be deliberate because of the allowable nx version in
> dependencies. It may also be overridden in /etc/nxserver/node.conf, or
> because you somehow have an older nxloadconfig somewhere.
>
>>
>>> cu
>>>
>>> Fabian
>>
>> Thanks,
>> Prakash
>> ________________________________________________________________
>>     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