[FreeNX-kNX] FreeNX Failing on RDP Connections
David Legg
davidlegg at savantis.co.uk
Wed Jun 13 15:39:21 UTC 2007
Hi All,
I have a 64-bit CentOS 5 installation where I previously had No Machine's
freely available NX Server installed, successfully using X and RDP
connections. I then decided to uninstall it and install FreeNX, because there
is no connection limit. I definitely uninstalled the previous NX Server, node
and client packages. The is FreeNX version 0.6.0-12, as-is from CentOS
extras.
After an explicit restart of the nxserver via nxserver --restart the remote X
connections worked fine, but I still can't connect to RDP Terminal Services
connections through it. Yes I do know how this works, and how you have to put
in your Linux machine's IP address and then the IP address of the Windows
machine the NX Server accesses by proxy. I'm using client version 2.1.0-17
from No Machine. The error messages I'm getting are these:
This is from the client window:
NX> 148 Server capacity: not reached for user: david
NX> 105
startsession --link="adsl" --backingstore="1" --nodelay="1" --encryption="1" --cache="8M" --images="32M" --media="0" --session="Windows
Server" --type="windows" --agent_server="192.168.40.3" --geometry="1024x738" --kbload=" --kbload=pc102/gb" --kbtype="pc102/gb" --keybd="1" --screeninfo="1024x738x32+render"
NX> 1000 NXNODE - Version 1.5.0-60 OS (GPL)
NX> 700 Session id:
base.savantis.localnet-1000-317994541C187B72ED1997B1AF78C44F
NX> 705 Session display: 1000
NX> 703 Session type: windows
NX> 701 Proxy cookie: eb133a55652924f359085cc2616fcc70
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: eb133a55652924f359085cc2616fcc70
NX> 704 Session cache: windows
NX> 707 SSL tunneling: 1
NX> 1009 Session status: starting
NX> 710 Session status: running
NX> 1002 Commit
NX> 105 /usr/bin/nxserver: line 1190: 26569 Terminated sleep
$AGENT_STARTUP_TIMEOUT
NX> 1006 Session status: running
NX> 596 Session startup failed.
NX> 1004 Error: NX Agent exited with exit status 1.
Can't
open /var/lib/nxserver/db/running/sessionId{317994541C187B72ED1997B1AF78C44F}:
No such file or directory.
mv: cannot stat
`/var/lib/nxserver/db/running/sessionId{317994541C187B72ED1997B1AF78C44F}':
No such file or directory
NX> 1006 Session status: closed
NX> 1001 Bye.
bye
Bye
NX> 999 Bye
Killed by signal 15.
From the session file in .nx I'm getting:
Info: Agent running with pid '26785'.
Info: Connecting to RDP server '192.168.40.3'
Session: Starting session at 'Tue Jun 12 21:27:26 2007'.
Loop: WARNING! Ignoring unknown option 'kbload' with value 'pc102/gb'.
Warning: Ignoring unknown option 'kbload' with value 'pc102/gb'.
Info: Proxy running in server mode with pid '26785'.
Info: Waiting for connection from '127.0.0.1' on port '5000'.
Info: Aborting the procedure due to signal '15'.
X connection to
nx,options=/home/david/.nx/C-base.savantis.localnet-1000-317994541C187B72ED1997B1AF78C44F/options:1000.0
broken (explicit kill or server shutdown).
In ~/.nx/errors I get:
Loop: WARNING! Disabling image cache with session 'session_rdp' and
link 'adsl'.
This is with the logging set to 7 and SESSION_LOG_CLEAN=0.
I'm at a bit of a loss, as it looks as if something is silently failing and
perhaps segfaulting somewhere. Are there some problems with FreeNX on a
64-bit system, even with 32-bit compatibility libraries installed that anyone
else has experienced like this? Does anyone else have this running OK? Is
there any more logging I can do to find out what else might be going on here?
Thanks,
David
More information about the FreeNX-kNX
mailing list