[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freenx-knx
Subject:    [FreeNX-kNX] problem with RDP connection
From:       "vlho" <vlho () seznam ! cz>
Date:       2007-03-22 7:56:58
Message-ID: 000701c76c57$aa9933b0$0500a8c0 () datainter ! local
[Download RAW message or body]

Hello all,

I had this enviroment:
- server
CentOS 4.4 64-bit
freenx-0.5.0-11.c4.i386
nx-2.1.0.5.el4.centos.i386

- client
nomachine nxclient_2.1.0-16 for Windows

All was OK, I connected from nomachine nxclient direct on CentOS and also I connected \
via nomachine nxclient through RDP protocol to  Windows server.

Since I upgraded freenx-0.5.0-12-el4.centos.i386 last weekend, I have had problem \
with connection through RDP protocol. Direct connection is OK.

I get error message: Session startup failed.

I changed in /etc/nx/nxnode.conf this paramaters into:
NX_LOG_LEVEL=6
SeSSION_LOG_CLEAN=0

and then I got following reports:

- /var/log/nxserver.log

-- NX SERVER START: -c /usr/libexec/nx/nxserver - ORIG_COMMAND=
HELLO NXSERVER - Version 1.5.0-60 OS (GPL)
NX> 105 hello NXCLIENT - Version 1.5.0
NX> 134 Accepted protocol: 1.5.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: root
NX> 102 Password:
Info: Auth method: passdb ssh
NX> 103 Welcome to: gsxa.domain.local user: root
NX> 105 listsession --user="root" --status="suspended,running" \
--geometry="1680x1050x32+render" --type="windows" NX> 127 Sessions list of user \
'root' for reconnect:

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


NX> 148 Server capacity: not reached for user: root
NX> 105 
startsession --link="modem" --backingstore="1" --nodelay="1" --encryption="1" \
--cache="8M" --images="32M" --media="0" --session="DI  gsxa - 
bis" --type="windows" --agent_server="bis" --agent_domain="DIL" --geometry="1024x768" \
                --kbload=" --kbload=pc102/cz" --kbtype="pc102/cz" 
 --keybd="1" --screeninfo="1024x768x32+render"

&link=modem&backingstore=1&nodelay=1&encryption=1&cache=8M&images=32M&media=0&session=DI \
gsxa -  bis&type=windows&agent_server=bis&agent_domain=DIL&geometry=1024x768&kbload=&k \
bload=pc102/cz&kbtype=pc102/cz&keybd=1&screeninfo=1024x768x32+render&clientproto=1.5.0 \
&user=root&userip=192.168.0.5&uniqueid=CC7D232D330AC4BDB218194816B33456&display=1000&host=127.0.0.1
 root@127.0.0.1's password:
NX> 1000 NXNODE - Version 1.5.0-60 OS (GPL)
NX> 700 Session id: gsxa.domain.local-1000-CC7D232D330AC4BDB218194816B33456
NX> 705 Session display: 1000
NX> 703 Session type: windows
NX> 701 Proxy cookie: 1a2ab411801ce3127dfe45edf701e847
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: 1a2ab411801ce3127dfe45edf701e847
NX> 704 Session cache: windows
NX> 707 SSL tunneling: 1
NX> 1009 Session status: starting
NX> 710 Session status: running
NX> 1002 Commit
NX> 1006 Session status: running
NX> 105 bye
Bye
NX> 1004 Error: NX Agent exited with exit status 1.
NX> 1006 Session status: closed
NX> 999 Bye
NX> 596 Session startup failed.
NX> 1001 Bye.

- /root/.nx/ .... /session
Loop: WARNING! Ignoring unknown option 'kbload' with value 'pc102/cz'.
Warning: Ignoring unknown option 'kbload' with value 'pc102/cz'.
Info: Proxy running in server mode with pid '9772'.
Info: Waiting for connection from '127.0.0.1' on port '5000'.
Info: Accepted connection from '127.0.0.1' with port '32816'.
Info: Connection with remote proxy established.
Info: Aborting the procedure due to signal '15'.
X connection to nx,options=/root/.nx/C-gsxa.domain.local-1000-5D44E85BDEDDE20B4392B807D27465DC/options:1000.0 \
broken (explicit kill  or server shutdown).

If return freenx-0.5.0-11.c4.i386, connecting through RDP is OK.
If update freenx-0.5.0-12-el4.centos.i386, connetion does not work properly again.

I tested version freenx-0.6.0-9-el4.at.noarch, same problem as with \
freenx-0.5.0-12-el4.centos.i386 appeared. I tested latest version \
freenx-0.6.0-12.el4.at.i386.rpm, same problem I tested ditto on CentOS 32-bit, \
identical symptoms appeared.

Note: I have in CentOS installed VMware Server...

Is it bug?
Help me please. Thank you.

Sorry for my bad English. 

________________________________________________________________
     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@kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________


[prev in list] [next in list] [prev in thread] [next in thread]