[prev in list] [next in list] [prev in thread] [next in thread]
List: freenx-knx
Subject: Re: [FreeNX-kNX] ssh problems gone, now real freenx problems
From: freenx () claymccoy ! com
Date: 2005-08-09 14:11:19
Message-ID: 19465220.1123596680065.JavaMail.freenx () claymccoy ! com
[Download RAW message or body]
Okay, which nx directory? The one on the client side in the users hoem
directory?
Thanks,
Clay
> I have only just got round to subscribing to this list since Gian Fillipo
> had to stop the original NX list which I understand but is still a pity.
>
> Similar ssh problems come up with native NX as well, which is what I am
> running (1.5.0).
>
> It happens for example when you reinstall or upgrade the server or do
> anything that regenerates the key pair. The easiest way that I have found
> to get round this is to remove the .nx directory completely (ie rm -rf
> .nx).
>
> The next time you initiate the client, the wizard is invoked and this
> forces a new copy of the public key to be taken.
>
> HTH
>
> John
>
> John Logsdon "Try to make things as simple
> Quantex Research Ltd, Manchester UK as possible but not simpler"
> j.logsdon@quantex-research.com a.einstein@relativity.org
> +44(0)161 445 4951/G:+44(0)7717758675 www.quantex-research.com
>
>
> On Mon, 8 Aug 2005, Clay McCoy wrote:
>
> > Thanks for all the help. Somehow ssh started working. I noticed there
> > was a new rpm, so I completely removed the old one, installed then new
> > one, and I noticed that the key was different. So I moved this new key
> > generated from the new rpm over and now I can ssh with a key as nx.
> > Thanks for all the great explanations, I learned a lot.
> >
> > But FreeNX still does not work. It seems brittle in the sense that
> > something different happens every time, without me changing anything. I
> > got a lot of one time errors that never repeated themselves. One told
> > me to look in the sshlog file in a "temp" folder in the users directory
> > on my client machine.
> >
> > I got this a lot:
> >
> > ----------------------------------------------------------------------------
------------
> > NXPROXY - Version 1.5.0
> >
> > Copyright (C) 2001, 2005 NoMachine.
> > See http://www.nomachine.com/ for more information.
> >
> > Info: Proxy running in client mode with pid '178'.
> > Error: Failed to set TCP_NODELAY flag on FD#19 to 1. Error is 102
> > 'Operation not supported on socket'.
> > Info: Aborting the procedure due to signal '15', 'SIGTERM'.
> > ----------------------------------------------------------------------------
------------
> >
> > It doesn't seem to matter if I "disable no-delay on TCP connection" or
> > not. So I left it unchecked.
> >
> > Then I left "Enable SSL encryption of all traffic" unchecked, and I got
> > this:
> >
> > ----------------------------------------------------------------------------
------------
> > NXPROXY - Version 1.5.0
> >
> > Copyright (C) 2001, 2005 NoMachine.
> > See http://www.nomachine.com/ for more information.
> >
> > Info: Proxy running in client mode with pid '192'.
> > Info: Connecting to remote host '192.168.0.3:5000'.
> > Info: Connection to remote proxy '192.168.0.3:5000' established.
> > Info: Synchronizing local and remote caches.
> > Info: Handshaking with remote proxy completed.
> > Info: Using cache parameters 4/262144/8192KB/8192KB.
> > Info: Using image cache parameters 1/1/32768KB.
> > Info: Using wan link parameters 16384/8/4/20.
> > Info: Using pack method '16m-jpeg-9' with session 'unix-kde'.
> > Info: Using ZLIB data compression level 1.
> > Info: Using ZLIB data threshold set to 32.
> > Info: Not using ZLIB stream compression.
> > Info: Using remote ZLIB data compression level 1.
> > Info: Not using remote ZLIB stream compression.
> > Info: No suitable cache file found.
> > Info: Using remote server '192.168.0.3:5000'.
> > Info: Starting X protocol compression.
> > Error: Failed to set TCP_NODELAY flag on FD#25 to 1. Error is 102
> > 'Operation not supported on socket'.
> > Info: Established X server connection.
> > Info: Using shared memory support in X server.
> > Info: End of session requested by signal '15' 'SIGTERM'.
> > Warning: Parent process appears to be dead. Exiting watchdog.
> > ----------------------------------------------------------------------------
------------
> >
> > And if I logon again right after that without changing anything the
> > window of the application actually comes up! But when I resume the one
> > session in the list, it times out.
> > "Timeout encountered in communication with the NX server."
> >
> > I have followed the directions on:
> > http://fedoranews.org/contributors/rick_stout/freenx/
> > I am using fedora core 4 and the mac os X nomachine client.
> >
> > Any help is appreciated,
> > Thanks,
> > Clay
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > FreeNX-kNX mailing list
> > FreeNX-kNX@kde.org
> > https://mail.kde.org/mailman/listinfo/freenx-knx
> >
>
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX@kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
>
Return-Path: <freenx-knx-bounces-+freenx=claymccoy.com@kde.org>
Received: from ktown.kde.org (ktown.kde.org [131.246.103.200])
by www7.kc.aoindustries.com (8.13.1/8.13.1) with SMTP id j797oeaD015711
for <freenx@claymccoy.com>; Tue, 9 Aug 2005 02:50:43 -0500
Received: (qmail 20054 invoked by uid 72); 9 Aug 2005 07:50:38 -0000
Received: (qmail 20050 invoked from network); 9 Aug 2005 07:50:37 -0000
Received: from pythagoras.zen.co.uk (212.23.3.140)
by ktown.kde.org with SMTP; 9 Aug 2005 07:50:32 -0000
Received: from [217.155.43.225] (helo=quantex-research.com)
by pythagoras.zen.co.uk with esmtp (Exim 4.30) id 1E2OsZ-0000NT-G5
for freenx-knx@kde.org; Tue, 09 Aug 2005 07:50:31 +0000
Received: from localhost (j.logsdon@localhost)
by quantex-research.com (8.8.7/8.8.7) with ESMTP id IAA13549
for <freenx-knx@kde.org>; Tue, 9 Aug 2005 08:50:34 +0100
Date: Tue, 9 Aug 2005 08:50:33 +0100 (GMT)
From: John Logsdon <j.logsdon@quantex-research.com>
To: User Support for FreeNX Server and kNX Client <freenx-knx@kde.org>
In-Reply-To: <42F81C23.5060508@claymccoy.com>
Message-ID: <Pine.LNX.4.10.10508090832300.13675-100000@quantex-research.com>
MIME-Version: 1.0
X-Originating-Pythagoras-IP: [217.155.43.225]
Subject: Re: [FreeNX-kNX] ssh problems gone, now real freenx problems
X-BeenThere: freenx-knx@kde.org
X-Mailman-Version: 2.1.6
Precedence: list
Reply-To: User Support for FreeNX Server and kNX Client <freenx-knx@kde.org>
List-Id: User Support for FreeNX Server and kNX Client <freenx-knx.kde.org>
List-Unsubscribe: <https://mail.kde.org/mailman/listinfo/freenx-knx>,
<mailto:freenx-knx-request@kde.org?subject=unsubscribe>
List-Archive: <http://mail.kde.org/pipermail/freenx-knx>
List-Post: <mailto:freenx-knx@kde.org>
List-Help: <mailto:freenx-knx-request@kde.org?subject=help>
List-Subscribe: <https://mail.kde.org/mailman/listinfo/freenx-knx>,
<mailto:freenx-knx-request@kde.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www7.kc.aoindustries.com id j797oeaD015711
X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on
www7.kc.aoindustries.com
X-Spam-Level:
X-Spam-Status: No, score=0.7 required=3.0 tests=FORGED_RCVD_HELO,
INVALID_TZ_GMT autolearn=no version=3.0.0
I have only just got round to subscribing to this list since Gian Fillipo
had to stop the original NX list which I understand but is still a pity.
Similar ssh problems come up with native NX as well, which is what I am
running (1.5.0).
It happens for example when you reinstall or upgrade the server or do
anything that regenerates the key pair. The easiest way that I have found
to get round this is to remove the .nx directory completely (ie rm -rf
.nx).
The next time you initiate the client, the wizard is invoked and this
forces a new copy of the public key to be taken.
HTH
John
John Logsdon "Try to make things as simple
Quantex Research Ltd, Manchester UK as possible but not simpler"
j.logsdon@quantex-research.com a.einstein@relativity.org
+44(0)161 445 4951/G:+44(0)7717758675 www.quantex-research.com
On Mon, 8 Aug 2005, Clay McCoy wrote:
> Thanks for all the help. Somehow ssh started working. I noticed there
> was a new rpm, so I completely removed the old one, installed then new
> one, and I noticed that the key was different. So I moved this new key
> generated from the new rpm over and now I can ssh with a key as nx.
> Thanks for all the great explanations, I learned a lot.
>
> But FreeNX still does not work. It seems brittle in the sense that
> something different happens every time, without me changing anything. I
> got a lot of one time errors that never repeated themselves. One told
> me to look in the sshlog file in a "temp" folder in the users directory
> on my client machine.
>
> I got this a lot:
>
> ----------------------------------------------------------------------------------------
> NXPROXY - Version 1.5.0
>
> Copyright (C) 2001, 2005 NoMachine.
> See http://www.nomachine.com/ for more information.
>
> Info: Proxy running in client mode with pid '178'.
> Error: Failed to set TCP_NODELAY flag on FD#19 to 1. Error is 102
> 'Operation not supported on socket'.
> Info: Aborting the procedure due to signal '15', 'SIGTERM'.
> ----------------------------------------------------------------------------------------
>
> It doesn't seem to matter if I "disable no-delay on TCP connection" or
> not. So I left it unchecked.
>
> Then I left "Enable SSL encryption of all traffic" unchecked, and I got
> this:
>
> ----------------------------------------------------------------------------------------
> NXPROXY - Version 1.5.0
>
> Copyright (C) 2001, 2005 NoMachine.
> See http://www.nomachine.com/ for more information.
>
> Info: Proxy running in client mode with pid '192'.
> Info: Connecting to remote host '192.168.0.3:5000'.
> Info: Connection to remote proxy '192.168.0.3:5000' established.
> Info: Synchronizing local and remote caches.
> Info: Handshaking with remote proxy completed.
> Info: Using cache parameters 4/262144/8192KB/8192KB.
> Info: Using image cache parameters 1/1/32768KB.
> Info: Using wan link parameters 16384/8/4/20.
> Info: Using pack method '16m-jpeg-9' with session 'unix-kde'.
> Info: Using ZLIB data compression level 1.
> Info: Using ZLIB data threshold set to 32.
> Info: Not using ZLIB stream compression.
> Info: Using remote ZLIB data compression level 1.
> Info: Not using remote ZLIB stream compression.
> Info: No suitable cache file found.
> Info: Using remote server '192.168.0.3:5000'.
> Info: Starting X protocol compression.
> Error: Failed to set TCP_NODELAY flag on FD#25 to 1. Error is 102
> 'Operation not supported on socket'.
> Info: Established X server connection.
> Info: Using shared memory support in X server.
> Info: End of session requested by signal '15' 'SIGTERM'.
> Warning: Parent process appears to be dead. Exiting watchdog.
> ----------------------------------------------------------------------------------------
>
> And if I logon again right after that without changing anything the
> window of the application actually comes up! But when I resume the one
> session in the list, it times out.
> "Timeout encountered in communication with the NX server."
>
> I have followed the directions on:
> http://fedoranews.org/contributors/rick_stout/freenx/
> I am using fedora core 4 and the mac os X nomachine client.
>
> Any help is appreciated,
> Thanks,
> Clay
>
>
>
>
>
>
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX@kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
>
_______________________________________________
FreeNX-kNX mailing list
FreeNX-kNX@kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx
_______________________________________________
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic