[FreeNX-kNX] Parse error in remote options string

[Rob Thomas]

I've fixed my "Parse error in remote options string" problem !!! The
NX client session name that I got the other office to setup contained
a space, mine didn't. The session name is actually passed as a
parameter to the server and therefore it must be seeing the bit after
the space as another parameter. I don't know exactly how its passed
but maybe it would be better if the client surrounded it with quotes.
But the fix for now is not to have any whitespace. Hope this fixes
your problem too Jason.
As for your SSL comment below, if you have the SSL box ticked then all
traffic is tunnelled through the SSH port, 22 by default. If its not
ticked then it uses the SSH port and others, can't remember which
right now. So your box might either be behind a firewall device or the
local firewall on the server which could have certain ports blocked \
open.
Cheers
Rob
---------- Forwarded message ----------
From: Jason Tally <jtally at o9studios.com>
Date: Thu, 09 Dec 2004 17:33:49 -0500
Subject: Re: [FreeNX-kNX] Parse error in remote options string
To: FreeNX-kNX at kde.org


Hi Rob,

Yes this is consistent I have yet to connect successfully either
directly on the lan or over the Internet. I also get another error
message if I try to connect without checking the box labeled "Enable SSL
encryption of all traffic" where after the client says "negotiating link
parameters" for a while it comes up with a box that states:

NX client was not able to establish an unencrypted channel with the
server. This could be due to the remote server being behind a firewall.
If this is the case, you should be able to run your session by selecting
the option "Enable SSL encryption of all traffic" in the configuration
dialog.

I'm going to try to use the NX client on the latest Knoppix 3.6 to see
if I can rule out a problem with the client.
Jason




Rob Thomas wrote:

>Update : I've managed to get a 3rd user to connect ok from the other
>office therefore the network must be ok. The only thing i can think of
>now is either a configuration problem on their machine or maybe a
>conflicting application.
>Rob
>
>---------- Forwarded message ----------
>From: Rob Thomas <welshblob at gmail.com>
>Date: Thu, 9 Dec 2004 13:08:13 +0000
>Subject: Re: [FreeNX-kNX] Parse error in remote options string
>To: freenx-knx at kde.org
>
>
>Hi Jason,
>Is this consistent? I'm using CentOS and Whitebox for my nxserver
>machines with Rick Stouts rpms and have seen this problem sometimes
>when I first connect with a new user, reconnecting normally sorts that
>out.
>I also have this problem with an nxserver on an adsl line on the
>internet which we're trying to connect to from two offices. These
>offices are technically on the same network and connect to the
>internet via the same proxy cluster. In my office I and my colleagues
>can connect to this box ok everytime using various ID's but two users
>at the other office (the only two I think have used it) can not
>connect. Their error messages seem to toggle between these
>
>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 '2740'.
>Info: Waiting for connection from any host on port '4986'.
>Info: Accepted connection from '127.0.0.1' on port '3074'.
>Info: Connection with remote proxy established.
>Error: Remote NX proxy closed the connection.
>Error: Please check your authorization credentials.
>
>OR
>
>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 '2432'.
>Info: Waiting for connection from any host on port '1287'.
>Info: Accepted connection from '127.0.0.1' on port '1370'.
>Info: Connection with remote proxy established.
>Error: Parse error in remote options string 'NX> '.
>
>I'm really not sure whats wrong as I connected from that office a
>couple of weeks ago ok.
>Cheers
>Rob
>
>*******************************************
>
>
>On Wed, 08 Dec 2004 22:09:38 -0500, Jason Tally <jtally at o9studios.com> wrote:
>
>
>>Ok I have a fresh Debian testing(sarge) install that I did a "apt-get
>>update", "apt-get dist-upgrade" before installing the nxserver package
>>by adding the following to my sources.list doing an "apt-get update" and
>>then "apt-get install nxserver"
>>deb http://archive.kalyxo.org/kalyxo/ staging main
>>deb http://archive.kalyxo.org/kalyxo/ experimental main
>>it installed the version 0.2.7 (although nxserver --status gives me
>>"NXSERVER - Version 1.4.0-02 OS_(GPL)") after this I did nxserver
>>--adduser jtally and copied the client.id_dsa.key to my windows client
>>(version 1.4.0-75)
>>When I attempt to connect I get an error Session xxxxxxxxxxxxxxxxx
>>Failed. clicking on details gives me this
>>
>>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 '1060'.
>>Info: Waiting for connection from any host on port '7200'.
>>Info: Accepted connection from '127.0.0.1' on port '7281'.
>>Info: Connection with remote proxy established.
>>Error: Parse error in remote options string 'NX> '.
>>
>>Thanks in advance for any help.
>>
>>Jason Tally
>>_______________________________________________
>>FreeNX-kNX mailing list
>>FreeNX-kNX at kde.org
>>https://mail.kde.org/mailman/listinfo/freenx-knx
>>
>>
>>
>_______________________________________________
>FreeNX-kNX mailing list
>FreeNX-kNX at kde.org
>https://mail.kde.org/mailman/listinfo/freenx-knx
>
>
>
>
>

_______________________________________________


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