[FreeNX-kNX] Re: rdp session does not work

[olafs6 at gmx.de]

Hi!

Am Montag, 27. September 2010 12:08:39 schrieb chris at ccburton.com:
> olaf <olafs6 at gmx.de> wrote on 26/09/2010 23:53:06:
> > Hi!
> >
> > I am trying to connect from nomachine-Client (on Ubuntu and OpenSuse)
> > over my FreeNX-Server (OpenSuse 11.2) to a Windows XP Prof. Machine, but
> > this does not work.
> 
> To windows ??

Yes. Is this not correct?
I think (thought?) it is possible to connect with the nomachine-client 
("Desktop" = Windows/rdp -> Settings -> IP of the Windows-Machine) "through" 
the FreeNX-Server/Machine to a Windows XP-pro computer.
(Computer with nomachine client -> FreeNX-Server -> Windows XP computer)

> > NX> 704 Session cache: windows
> > NX> 707 SSL tunneling: 1
> > NX> 105 /usr/bin/nxserver: line 1371:  6532 Terminated
> > sleep $AGENT_STARTUP_TIMEOUT
> > NX> 596 Session startup failed.
> > NX> 280 Exiting on signal: 15
> 
> Did you just restart the NX server, 

A few days before.

> or not connect for a week or so ??
There are nx-sessions parallel to these tests and messages.
The server is used every day by 1-4 users.

> This timeout is usually when NX is trying to load its libraries for
> the first time and you can expect 4 - 8 episodes before it starts
> working normally.

I remember this or a similar  problem. I found a solution somewhere (here?) a 
few month before.

> 
> If this is thcase then the quick (and nasty) fix is a sleep
> command, see my earlier posts
> 

Could this be the same error?
As you can see in actual error message I paste below, there is a similar 
message, and at this moment I have not reboot the server for days. There are a 
few normal nx-sessions (from ThinCient with Thinstation/nomachine to the 
FreeNX-Server) at the same time.
All works fine, with the exception of Windows rdp sessions.

I have activate
SESSION_LOG_CLEAN=0 in node.conf
and have a look at
"/home/nxuser/.nx/F-C-serv-1006-898EE5FA09568090AB6DF2733B0BE214/session
but there is only some text like the output of "man rdesktop" or something 
similar.

Bye
Olaf



NX> 203 NXSSH running with pid: 21506
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
NX> 200 Connected to address: 192.168.nx.server on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
HELLO NXSERVER - Version 2.1.0-72 OS (GPL, using backend: 3.4.0)
NX> 105 hello NXCLIENT - Version 2.1.0
NX> 134 Accepted protocol: 2.1.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: nxuser
NX> 102 Password:
NX> 103 Welcome to: serv user: nxuser
NX> 105 listsession --user="nxuser" --status="suspended,running" --
geometry="1920x1080x24+render" --type="windows"
NX> 127 Sessions list of user 'nxuser' for reconnect:

Display Type             Session ID                       Options  Depth 
Screen         Status      Session Name
------- ---------------- -------------------------------- -------- ----- 
-------------- ----------- ------------------------------

NX> 148 Server capacity: not reached for user: nxuser
NX> 105 startsession  --link="lan" --backingstore="1" --encryption="1" --
cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --
composite="1" --media="0" --imagecompressionmethod="0" --session="xp" --
type="windows" --agent_server="192.168.windows.xp" --agent_user="XPuser" 
agent_password="******" --geometry="800x600+560+240" --client="linux" --
keyboard="pc102/de" --screeninfo="800x600x24+render" 

NX> 1000 NXNODE - Version 2.1.0-72 OS (GPL, using backend: 3.4.0)
NX> 700 Session id: serv-1006-898EE5FA09568090AB6DF2733B0BE214
NX> 705 Session display: 1006
NX> 703 Session type: windows
NX> 701 Proxy cookie: b658daa244bd56ff1b7b4e80144c7696
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: b658daa244bd56ff1b7b4e80144c7696
NX> 704 Session cache: windows
NX> 707 SSL tunneling: 1
NX> 105 /usr/bin/nxserver: line 1371: 18816 Terminated              sleep 
$AGENT_STARTUP_TIMEOUT
NX> 596 Session startup failed.
NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set 
SESSION_LOG_CLEAN=0 in node.conf and investigate "/home/nxuser/.nx/F-C-
serv-1006-898EE5FA09568090AB6DF2733B0BE214/session". You might also want to 
try: ssh -X myserver; /usr/bin/nxnode --agent to test the basic functionality. 
Session log follows:
Can't open 
/var/lib/nxserver/db/running/sessionId{898EE5FA09568090AB6DF2733B0BE214}: No 
such file or directory.
NX> 280 Exiting on signal: 15