Nomachine's Solaris NX client doesn't work with SUSE 10.1 NX server
Hi, I cannot connect to the SUSE 10.1 NX server with the Nomachine's Solaris NX client (http://www.nomachine.com/) running on SPARC Solaris 9. Has anybody got it working? Any ideas how to fix it? I used knx to connect from a 400 MHz Celeron PC to a 2.8 GHz Pentium4 PC (both running SUSE 10.1) via knx over a 10 Mb/s Ethernet and I was pleasantly surprised with the speed. So I would like to use NX on a Solaris client too. More info: SUSE firewall is switched off on the server. Knx sessions from from the server to the server work OK. The session log follows (IP address and hostname are changed): NX> 203 NXSSH running with pid: 19216 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: xxx.xxx.xx.xx on port: 22 NX> 202 Authenticating user: nx NX> 208 Using auth method: publickey HELLO NXSERVER - Version 1.4.0-44 OS (GPL) NX> 105 hello NXCLIENT - Version 1.4.0 NX> 134 Accepted protocol: 1.4.0 NX> 105 SET SHELL_MODE SHELL NX> 105 SET AUTH_MODE PASSWORD NX> 105 login NX> 101 User: malusek NX> 102 Password: NX> 103 Welcome to: xxxxx user: malusek NX> 105 listsession --user="malusek" --status="suspended,running" --geometry="1600x1200x24+render" --type="unix-kde" NX> 127 Sessions list of user 'malusek' for reconnect: Display Type Session ID Options Depth Screen Status Session Name ------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------ NX> 148 Server capacity: not reached for user: malusek NX> 105 startsession --link="lan" --backingstore="1" --nodelay="1" --cache="16M" --images="64M" --media="0" --session="xxxxx" --type="unix-kde" --cookie="******" --geometry="1024x768+288+192" --kbtype="pc105/se" --screeninfo="1024x768x24+render" NX> 1000 NXNODE - Version 1.4.0-44 OS (GPL) NX> 700 Session id: xxxxx-1002-5EC0CB0F3DA6A7E802A960B4C39D89B4 NX> 705 Session display: 1002 NX> 703 Session type: unix-kde NX> 701 Proxy cookie: 7f4f72b1017039af696b8c6915d90d5b NX> 702 Proxy IP: xxx.xxx.xx.xx NX> 706 Agent cookie: 21f4c49d80bcb74e07041d300f0f206e NX> 704 Session cache: unix-kde NX> 707 SSL tunneling: 0 /usr/bin/nxserver: line 880: 16764 Terminated ( sleep $AGENT_STARTUP_TIMEOUT; exit 1 ) NX> 105 NX> 504 Session startup failed. NX> 1004 Error: nxagent failed to start with: Unrecognized option: 1 NX> 1001 Bye. Killed by signal 15. -- A.M.
On Wednesday 06 September 2006 03:31, Alexandr Malusek wrote:
[...] /usr/bin/nxserver: line 880: 16764 Terminated ( sleep $AGENT_STARTUP_TIMEOUT; exit 1 ) NX> 105 NX> 504 Session startup failed. NX> 1004 Error: nxagent failed to start with: Unrecognized option: 1
I get the same error in all my attempts to connect from a Suse 10.1 client. I tried to my old 9.3 box, on which freenx and nxclient was working fine, and I tried to connect to various 10.1 servers and I always get this message: Error: nxagent failed to start with: Unrecognized option: 1 I googled for it, but I only found some hints that modify "nxnode", but still don't seem to solve the problem, such as here: http://www.linuxforums.org/forum/suse-linux-help/69482-remote-control-suse-1... At least you are being able to connect from Suse to Suse, is that right? Carlos FL --
Newer SUSE might have NX v2, please check that your client on Slowaris also uses nxclient v2.
I solved the same problem by installing the "2xterminalserver-1.5.0-61.i586.rpm" from http://code.2x.com/linuxterminalserver/downloads /JK
Jan Karjalainen
I solved the same problem by installing the "2xterminalserver-1.5.0-61.i586.rpm" from http://code.2x.com/linuxterminalserver/downloads
I have installed the NoMachine's NX server on the SUSE 10.1 server. This solution is known to work but, in my case, it doesn't. It seems that the Solaris client has problems with graphics, for instance icons are shifted from their locations. If I start nxclient on the Solaris machine and redirect the display to a Linux machine (e.g. "ssh -X solaris_machine nxclient") then the client works OK. Therefore I think that the NX server from code.2x.com won't help. Anyway, I have given up. The old Solaris machine will be replaced with a Linux PC in about 1 month. -- A.M.
Carlos F Lange
On Wednesday 06 September 2006 03:31, Alexandr Malusek wrote:
[...] /usr/bin/nxserver: line 880: 16764 Terminated ( sleep $AGENT_STARTUP_TIMEOUT; exit 1 ) NX> 105 NX> 504 Session startup failed. NX> 1004 Error: nxagent failed to start with: Unrecognized option: 1
I get the same error in all my attempts to connect from a Suse 10.1 client. I tried to my old 9.3 box, on which freenx and nxclient was working fine, and I tried to connect to various 10.1 servers and I always get this message: Error: nxagent failed to start with: Unrecognized option: 1
I googled for it, but I only found some hints that modify "nxnode", but still don't seem to solve the problem, such as here: http://www.linuxforums.org/forum/suse-linux-help/69482-remote-control-suse-1...
At least you are being able to connect from Suse to Suse, is that right?
Yes, a connection from SUSE 10.1 to SUSE 10.1 worked without problems when SuSEfirewall was switched off on both machines. (The basic firewall setup described in the reference manual worked for one or two initial sessions but then stopped working since, in the default setup, the client needed a much wider range of opened ports.) -- A.M.
participants (4)
-
Alexandr Malusek -
Alexey Eremenko -
Carlos F Lange -
Jan Karjalainen