[FreeNX-kNX] FreeNX 0.5.0 - Snapshot 5

thomas.vonsteiger at bluewin.ch thomas.vonsteiger at bluewin.ch
Thu Mar 16 22:13:19 UTC 2006


You are right, netcat is missing.
With a link from nc nxclient startup normal.
I wrote this steps to the FAQ.

manyThx for all.
Thomas

-----Ursprüngliche Nachricht-----
Von: Fabian Franz [mailto:FabianFranz at gmx.de] 
Gesendet: Donnerstag, 16. März 2006 16:43
An: freenx-knx at kde.org
Cc: thomas.vonsteiger at bluewin.ch
Betreff: Re: [FreeNX-kNX] FreeNX 0.5.0 - Snapshot 5

Am Mittwoch, 15. März 2006 00:56 schrieb thomas.vonsteiger at bluewin.ch:
> Hi,
>
> I have tested freenx snapshot 5 with nxserver 1.5.0-50 on FedoraCore 4.
> WinXP with Windowsclient nxclient 1.5.0-138 running perfect incl. resuming
> of a old session. For this nxserver-from-xp-2-fc3.log
>
> From nxclient-1.5.0-155 on FedoraCore 4 to nxserver on FC4 I can not start
> a session. Becose there is a problem like:
>
> Info: Proxy running in client mode with pid '3144'.
> Info: Aborting the procedure due to signal '15', 'SIGTERM'.
>
> For this nxserver-from-fc4-2-fc4.log
>
> Are you have a idea whats the problem ?

Yes, I have. You enabled SSL tunneling on FC 4 and not on the Windows
client.

I guess you are missing netcat (also called nc) on your server or don't have

an appropriate entry in nxloadconfig.

I think its patched in the NX RPMs, but you might also just do an alias from

nc to netcat.

I fixed this in SVN.

To be sure that this is the error do:

nxloadconfig --check

Please add trying this line to the FAQ, while you are at it.

cu

Fabian

-- 
      *** Consulting - Training - Workshops - Troubleshooting ***
   @@@ LiveCDs (Knoppix), Debian, Remote Desktop Access (FreeNX) @@@

--- Fabian Franz --- www.fabian-franz.de --- consulting at fabian-franz.de




More information about the FreeNX-kNX mailing list