[FreeNX-kNX] (no subject)

Felipe García torcaz99 at hotmail.com
Thu Oct 6 22:47:10 UTC 2011


I'm to detail the problem:

I've configured free-nx on CentOS5.5:

nx-3.4.0-7.el5.centos

freenx-0.7.3-7.el5.centos



 If I connect using nxclient (downlaoded from nomachine), I've no 
problem for creating a KDE session or Gnome session for Linux and 
Windows clients.

  

 If I create a desktop "unix-custom" and say to run a command or select 
"Run the console", it works on Linux but not on Windows clients. For 
working on windows clients I've to enable "New virtual desktop" instead 
of "Floating window" .



  The problem is that I've to run programs in "Floating window" instead of "New virtual desktop" for windows clients.

  

  I suppose is a problem of configuration of node.conf, but don't know what I have to configure.



  ¿Any help? 



  Thanks



1- This is the message that is displayed in a nx window:


	Quote:
	
	
		
			
				The connection with the remote server was shut down.

Please check the state of your network connection.
			
		
	
	
2- This is what I see in session log:


	Quote:
	
	
		
			
				Info: Display running with pid '3268' and handler '0x19060e'.



NXPROXY - Version 3.5.0



Copyright (C) 2001, 2011 NoMachine.

See http://www.nomachine.com/ for more information.



Info: Proxy running in client mode with pid '4956'.

Session: Starting session at 'Wed Oct  5 14:58:30 2011'.

Warning: Connected to remote version 3.4.0 with local version 3.5.0.

Info: Connection with remote proxy completed.

Warning: Unrecognized session type 'unix-desktop'. Assuming agent session.

Info: Using ADSL link parameters 512/24/1/0.

Info: Using cache parameters 4/4096KB/16384KB/16384KB.

Info: Using pack method 'adaptive-7' with session 'unix-desktop'.

Info: Using ZLIB data compression 1/1/32.

Info: Using ZLIB stream compression 4/4.

Info: No suitable cache file found.

Info: Forwarding X11 connections to display ':0'.

Info: Forwarding auxiliary X11 connections to display ':0'.

Info: Listening to font server connections on port '11000'.

Session: Session started at 'Wed Oct  5 14:58:30 2011'.

Error: Connection with remote peer broken.

Error: Please check the state of your network and retry.

Session: Terminating session at 'Wed Oct  5 14:58:34 2011'.

Session: Session terminated at 'Wed Oct  5 14:58:34 2011'.
			
		
	
	


3- This is what I see in messages:


	Quote:
	
	
		
			
				NX> NX> 103 Welcome to: server1.company.com user: user1

NX> 105 listsession --user="user1" --status="suspended,running" --geometry="1440x900x32+render" --type="unix-console"

NX> 127 Sessions list of user 'user1' for reconnect:



Display Type             Session ID                       Options  Depth Screen         Status      Session Name

------- ---------------- -------------------------------- -------- -----
 -------------- ----------- ------------------------------





NX> 148 Server capacity: not reached for user: user1

NX> 105

startsession  --rootless="1" --virtualdesktop="0" --link="adsl" 
--backingstore="1" --encryption="1" --cache="16M" --images="64M" 
--shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" 
--session="xclock" --type="unix-console" --client="winnt" 
--kbload="pc102/es" --keymap="es" --keyboard="pc102/es" --aux="1" 
--screeninfo="1434x842x32+render"



NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: not detected)







NX> 700 Session id: server1.company.com-1000-EA268B031C43D455F1A97613A490F0A0

NX> 705 Session display: 1000

NX> 703 Session type: unix-console

NX> 701 Proxy cookie: d266e1f540dceede4a70c81c70c4c37c

NX> 702 Proxy IP: 10.16.137.224

NX> 706 Agent cookie: d266e1f540dceede4a70c81c70c4c37c

NX> 704 Session cache: unix-console

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> 999 Bye



Info: Closing connection to slave with pid 14618.

1001 Bye.

NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot 
set SESSION_LOG_CLEAN=0 in node.conf and investigate 
"/home/DOM/user1/.nx/F-C-server1.company.com-1000-EA268B031C43D455F1A97613A490F0A0/session".
 You might also want to try: ssh -X myserver; /usr/bin/nxnode --agent to
 test the basic functionality. Session log follows:

NX> 596 Session startup failed.

NX> 1006 Session status: closed

NX> 1001 Bye.

Info: Closing connection to slave with pid 14618.
			
		


Any help will be appreciated.
Thanks

To: freenx-knx at kde.org
From: chris at ccburton.com
Date: Thu, 6 Oct 2011 20:15:18 +0100
Subject: Re: [FreeNX-kNX] (no subject)



freenx-knx-bounces at kde.org wrote on 06/10/2011 13:59:46:



> Hallo:



> I've installed FreeNX on CentOS 5.5 and is has worked fine.

> But on another compurter if I run:



[SNIP]



> I receive an error (only in Windows clients,
Linux clients work fine):



So it follows the client ??



Are you running the latest client version ??



> "The connection with the remote server was
shut down. 



It fell over.



> Please check the state of your nework connection."



What's in the logs ??



> 

> For running a command, I have to select "New virtual desktop",
but 

> then I don't have a rootless window. And I need a "Rootless window".

> 

> Can any tell me how to solve the problem?

> 

> Thanks


________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________ 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20111007/c963f7ad/attachment.html>


More information about the FreeNX-kNX mailing list