RE: connection timeout

_______________________________________________
FreeNX-kNX mailing list
FreeNX-kNX <at> kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx

Re: Connect to NT4 Terminal Server ?

Gian Filippo Pinzari schrieb:

> may you please send us the logs so we can try to investigate
> this issue?

Unfortunately these were not very informative. Is there a way to 
increase verbosity like with the commercial NXServer?

Anyway, if I pass the "-4" paramater to nxdesktop I get to the login 
screen of my NT4 Terminal Server. I added it in /usr/bin/nxnode, line 
165 like this:

$NX_DIR/bin/nxdesktop -4 -name "NX - $user <at> $HOSTNAME:$display - $session 
(GPL Edition)" $K $G $U $P $agent_server 2>>~/.nx/C-$sess_id/session &

With that settings I can login to the WTS, but after some time the 
client just quits silently. Log says:
"End of session requested by remote proxy."

Is there a better way to pass parameters to nxdesktop? It would be nice 
if I could do this on the client side to optimize both for rdp4 and rdp5 
sessions.

--

-- 
Mit freundlichen Grüßen

André Sänger

*checked by MailMarshal*

Re: Connect to NT4 Terminal Server ?

André Sänger wrote:
> Anyway, if I pass the "-4" paramater to nxdesktop I get to the login 
> screen of my NT4 Terminal Server. I added it in /usr/bin/nxnode, line 
> 165 like this:

Does FreeNX share the same node.conf format? I think so. In this
case there is a better way to manage this: just add -4 to the
AGENT_EXTRA_OPTIONS_RDP key.

> With that settings I can login to the WTS, but after some time the 
> client just quits silently. Log says:
> "End of session requested by remote proxy."

This probably means that the Windows TS disconnected nxdesktop,
nxdesktop exited and the proxy link was closed. It can also be that
nxdesktop exited abnormally and, hopefully, told us why. You should
check the session logs on the server side.

> Is there a better way to pass parameters to nxdesktop? It would be nice 
> if I could do this on the client side to optimize both for rdp4 and rdp5 
> sessions.

See above.

At the present moment we don't plan to add more configuration para-
meters to the client, we are rather trying to reduce them. We need
to do that without restricting the ability of the user of having
full control of the session settings. My idea is that the client
on the local machine should just start the tunnel and then a GUI
running on the server side should manage the session, including the
desktop parameters. This will require some time to be implemented.
An example of such a design is the NX Manager application. It is
a "NX client" built with a Web GUI, able to perform any operation
nxclient can and obviously much more, as for example the system
management tasks. A future server-side nxclient may be a Web appli-
cation as well, running inside Konqueror or Mozilla. Probably the
switch will happen in version 2.

There have been discussions lately on this topic. Some people don't
realize that having a "fat" client on the local machine helped a
lot in the development. This is not a design choice or a NX limita-
tion. We could have never managed to achieve the required reliabi-
lity without a complete client infrastructure, good error reporting
and full control of the session timelife on the client.

The client GUI will never go away completely. There are things that
we'll still need to do on the client side to manage the NX environ-
ment, but such a GUI will not be required to run a NX session as
we know it today.

/Gian Filippo.

[PATCH] FreeNX unix-default

Hi,

I have updated the patch that adds default session support to nxnode 
according to suggestions given by *Gian Filippo Pinzari ( 
http://mail.kde.org/pipermail/freenx-knx/2004-November/000459.html ).
It should now work on any distribution that stores X11 configuration in 
/etc/X11. It executes $HOME/.Xclients if it exists or 
/etc/X11/xdm/Xsession if the first file doesn't exist.

If the patch is ok, please add it to the next release.

-- 
Best regards,
Kalev Lember
*

--- /tmp/nxnode	2004-11-21 00:50:41.000000000 +0200
+++ /usr/bin/nxnode	2004-12-01 13:16:57.722273040 +0200
 <at>  <at>  -125,6 +125,13  <at>  <at>  node_start_applications()
 		unix-application)
 			STARTX=$(which $application)
 		;;
+		unix-default)
+			if [ -f "$HOME/.Xclients" ]; then
+				STARTX="$HOME/.Xclients"
+			elif [ -f "/etc/X11/xdm/Xsession" ]; then
+				STARTX="/etc/X11/xdm/Xsession"
+			fi
+		;;
 	esac
 	[ -n "$STARTX" ] || return

_______________________________________________
FreeNX-kNX mailing list
FreeNX-kNX <at> kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx

Re: Connect to NT4 Terminal Server ?

Gian Filippo Pinzari schrieb:

> Does FreeNX share the same node.conf format? I think so. In this
> case there is a better way to manage this: just add -4 to the
> AGENT_EXTRA_OPTIONS_RDP key.

FreeNX didn´t create a node.conf by default. It created a /etc/nxserver 
directory though.
Can I put a node.conf there? Will it be recognized by freeNX?

--

-- 
Mit freundlichen Grüßen

André Sänger

*checked by MailMarshal*

Re: freenx and nxclient windows crash

[resending]

I gather nobody else is even seeing this problem? Is there a way for
me to gather more logs on the server to figure out what is going on?

On Tue, 30 Nov 2004 15:07:44 -0500, Aamer Akhter <aakhter <at> gmail.com> wrote:
> Hello,
> 
> I'm competely new to nx and freenx so I apologize beforehand about the
> quality of the below questions. Although I did do a some searches and
> the few things in existance did not appear to help.
> 
> I'm made rpm's from Rick Stout's rh src.rpms at:
>  http://fedoranews.org/contributors/rick_stout/freenx/
> 
> I hade to change the getent and useradd commands in the freenx spec
> file to cat passwd and luseradd so as not to get killed by NIS+
> searching (which was taking several hours). But other than that I did
> not change Rick's packages.
> 
> The system I'm building on is a RHEL3 system. And as far as I can tell
> nx and freenx seemed to install fine.
> 
> I'm using nxclient-1.4.0-75 on windows, and after connecting and auth,
> nxclient crashes.
> 
> On the server I see this afterwards:
> [11:13:10] nsite-l3vpn-1:/var/log> sudo nxserver --list
> NX> 100 NXSERVER - Version 1.4.0-02 OS_(GPL)
> NX> 127 Sessions list:
> 
> Display Username        Remote IP       Session ID
> ------- --------------- --------------- --------------------------------
> 1008    aakhter 10.83.132.173   B5E93783A517CEBF8E31060AC0402B23
> NX> 999 Bye
> 
> But I'm unsure of how to connect to this session... I'm connecting to
> port 22, and logging in with my username/password (which seem to
> work). From the secure logs I see that there is another connection
> created via the loopback. But I don't see anyother logs.
> 
> Neither X nor vnc seem to work, and fail in the same way in that
> nxclient crashes.
> 
> Is anybody else seeing this problem?
> 
> >rpm -qa | grep nx
> nx-1.4.0-0.rh.3
> freenx-0.2.7-0.rh.1.cel3
> 
> --
> Aamer Akhter / aakhter <at> gmail.com
> 

--

-- 
Aamer Akhter / aakhter <at> gmail.com

Problem using nxserver

Hi,

I installed nxserver (from debian.tu-bs.de) on a debian 3.1 running in a 
colinux process under windows XP.
Using nomachine client, I can get into the nxserver but the only thing I 
get is a 600x400 nx window with a working mouse cursor.
I am missing something to make it to work correctly (not an expert as 
you can see).
Below is basically what I installed.

Thanks in advance for your help.
Gilles

 >apt-get install console-data (azerty fr keyboard)
 >apt-get install locales (fr with euro)
dpkg-reconfigured it

 >apt-get upgrade
 >apt-get dist-upgrade (to unstable)

 >apt-get install xserver-xfree86
 >dpkg-reconfigure it

 >apt-get install konsole

 >apt-get install ssh
I manually modified the config file to Forward X11

 >apt-get install nxserver
setup
added user/passwd

that's about it

suspend/resume sessions not working with KNX?

Hi

Is it a known issue, that suspending/resuming sessions does not work
with the KNX client? I'm using FreeNX 0.2.7, NX 1.4.0 and knx
0.1. Does it only work with the NoMachine client?

Stefan

Public Key available
------------------------------------------------------
Stefan Dirsch (Res. & Dev.)   SUSE LINUX Products GmbH
Tel: 0911-740 53 0            Maxfeldstraße 5
FAX: 0911-740 53 479          D-90409 Nürnberg
http://www.suse.de            Germany 
------------------------------------------------------

Re: Resuming suspended sessions : Still not working

Rob Thomas wrote:
> Hi,
> I didn't see a solution to this posted previously so thought I'd
> repost. I've always had trouble resuming suspended sessions when using
> freenx. I tried the trial commercial version orginally and that worked
> fine. So I'm not sure what the problem is.
> Here are the steps I take after suspending a session,
> Login into session XYZ
> The dialog says:
> 	Connecting to x.x.x.x
> 	Connected to x.x.x.x
> 	Waiting authentication
> 	Authentication completed
> 	Resuming the suspended session
> 	Negotiating X protocol
> 	>>>> Window appears briefly (2/10 sec) and disappears.
> 	Session XYZ Failed -> Detail or Close buttons
> 
> To re-enable the connection, I need to do nxserver --terminate :ScreenID
> 
> I'm using NoMachine NXClient for Windows 1.4.0-75 on Windows XP SP1 
> Freenx\NX RedHat Enterprise 3 rpm's, from Rich Stout's page .... 
> 	freenx-0.2.5-0.rh.1.noarch.rpm
> 	nx-1.4.0-0.rh.3.i386.rpm
> .... on Whitebox Enterprise Linux 3.0 (RHEL3 rebuild) fully updated to
> 10/11/2004
> 
> Error Details are .....
> 
> NXPROXY - Version 1.4.0
> 
> Copyright (C) 2001, 2004 NoMachine.
> See http://www.nomachine.com/ for more information.
> 
> Info: Proxy running in client mode with pid '3260'.
> Info: Waiting for connection from any host on port '4309'.
> Info: Accepted connection from '127.0.0.1' on port '4398'.
> Info: Connection with remote proxy established.
> Info: Handshaking with remote proxy ':5000' completed.
> Info: Synchronizing local and remote caches.
> Info: Using cache parameters 4/262144/8192KB/8192KB.
> Info: Using image cache parameters 1/1/32768KB.
> Info: Using adsl link parameters 8192/80/16/4096.
> Info: Using pack method '16m-jpeg-7' with session 'unix-kde'.
> Info: Using ZLIB data compression level 3.
> Info: Using ZLIB data threshold set to 32.
> Info: Using ZLIB stream compression level 6.
> Info: Using remote ZLIB data compression level 3.
> Info: Using remote ZLIB stream compression level 6.
> Info: No suitable cache file found.
> Info: Using remote server connected on port '4309'.
> Info: Starting X protocol compression.
> Info: Established X server connection.
> Error: Decompression of data failed. Error is 'data error'.
> Error: Lost connection to peer proxy on FD#5.
> Error: Connection with remote peer broken.
> Error: Please report this problem to support personnel.
> 
> Any ideas?

I'm now getting this same error. It's possible I've had this a while, as 
I don't do much suspending. I've tried going back to Freenx 0.2.5, and 
NX snapshot 6, and every combination of Freenx/NX revision since then. I 
am able to get a successful resume using the 1.3.2 client, but not with 
1.4.0-57 or 1.4.0-75. I have completely removed every piece associated 
with Freenx, NX, and nxclient from both system, and still cannot get the 
1.4.0 series clients to resume properly. Anyone seen this problem?

Regards,

Rick Stout

Re: Resuming suspended sessions : Still not working

Hi Rick, 
Well I've still got this problem and always had this error with freenx
but I can't say I ever tested it with the 1.3.2 client. I tried going
back to the 1.3.2 client with freenx 2.7 but just got connection
timeout errors. As a workaround, although not ideal, I am planning to
use the undocumented nxserver --list-suspended <userid> function, as
mentioned in a previous post, to produce a list that I could
automatically kill through a cron job script. I would need to do some
testing though to make sure I'm not going to kill any live sessions
though .
Anyway thanks for your efforts in compiling the rpms as its made using
freenx so much easier. Also thanks go to the development team for
producing and supporting such a great tool.
Regards
Rob

---------- Forwarded message ----------
From: Rick Stout <zipsonic <at> gmail.com>
Date: Thu, 02 Dec 2004 23:40:13 -0800
Subject: Re: [FreeNX-kNX] Resuming suspended sessions : Still not working
To: FreeNX-kNX <freenx-knx <at> kde.org>
Cc: welshblob <at> gmail.com

Rob Thomas wrote:

> Hi,
> I didn't see a solution to this posted previously so thought I'd
> repost. I've always had trouble resuming suspended sessions when using
> freenx. I tried the trial commercial version orginally and that worked
> fine. So I'm not sure what the problem is.
> Here are the steps I take after suspending a session,
> Login into session XYZ
> The dialog says:
>       Connecting to x.x.x.x
>       Connected to x.x.x.x
>       Waiting authentication
>       Authentication completed
>       Resuming the suspended session
>       Negotiating X protocol
>       >>>> Window appears briefly (2/10 sec) and disappears.
>       Session XYZ Failed -> Detail or Close buttons
>
> To re-enable the connection, I need to do nxserver --terminate :ScreenID
>
> I'm using NoMachine NXClient for Windows 1.4.0-75 on Windows XP SP1
> Freenx\NX RedHat Enterprise 3 rpm's, from Rich Stout's page ....
>       freenx-0.2.5-0.rh.1.noarch.rpm
>       nx-1.4.0-0.rh.3.i386.rpm
> .... on Whitebox Enterprise Linux 3.0 (RHEL3 rebuild) fully updated to
> 10/11/2004
>
> Error Details are .....
>
> NXPROXY - Version 1.4.0
>
> Copyright (C) 2001, 2004 NoMachine.
> See http://www.nomachine.com/ for more information.
>
> Info: Proxy running in client mode with pid '3260'.
> Info: Waiting for connection from any host on port '4309'.
> Info: Accepted connection from '127.0.0.1' on port '4398'.
> Info: Connection with remote proxy established.
> Info: Handshaking with remote proxy ':5000' completed.
> Info: Synchronizing local and remote caches.
> Info: Using cache parameters 4/262144/8192KB/8192KB.
> Info: Using image cache parameters 1/1/32768KB.
> Info: Using adsl link parameters 8192/80/16/4096.
> Info: Using pack method '16m-jpeg-7' with session 'unix-kde'.
> Info: Using ZLIB data compression level 3.
> Info: Using ZLIB data threshold set to 32.
> Info: Using ZLIB stream compression level 6.
> Info: Using remote ZLIB data compression level 3.
> Info: Using remote ZLIB stream compression level 6.
> Info: No suitable cache file found.
> Info: Using remote server connected on port '4309'.
> Info: Starting X protocol compression.
> Info: Established X server connection.
> Error: Decompression of data failed. Error is 'data error'.
> Error: Lost connection to peer proxy on FD#5.
> Error: Connection with remote peer broken.
> Error: Please report this problem to support personnel.
>
> Any ideas?

I'm now getting this same error. It's possible I've had this a while, as
I don't do much suspending. I've tried going back to Freenx 0.2.5, and
NX snapshot 6, and every combination of Freenx/NX revision since then. I
am able to get a successful resume using the 1.3.2 client, but not with
1.4.0-57 or 1.4.0-75. I have completely removed every piece associated
with Freenx, NX, and nxclient from both system, and still cannot get the
1.4.0 series clients to resume properly. Anyone seen this problem?

Regards,

Rick Stout