[prev in list] [next in list] [prev in thread] [next in thread]
List: freenx-knx
Subject: Re: [FreeNX-kNX] 64b CentOS 4.6 - disconnect/terminate don't work
From: "Adrian Coman" <adrian () trustic ! eu>
Date: 2008-08-19 17:49:06
Message-ID: fd2a59450808191049h78f22fbla711e2345551010a () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
1. The problem I mentioned earlier is fixed, I can now disconnect/terminate
a session.
However I have another issue: when connecting to a session (new or resumed)
the NX client keeps a window saying "negotiating link parameters" even after
the session is started. After ~1min the NX session is automatically closed
(suspended).The NX server log is saying:
NX> 596 Error: Session failed. Reason was: Session: Display failure
detected at 'Tue Aug 19 20:36:10 2008'.
NX> 1009 Session status: suspending
NX> 1005 Session status: suspended
Here is my config:
distribuition: CentOS 4.6, 64 bits
freenx-0.7.2-3.el4.centos
nx-3.2.0-8.el4.centos
2. I can not start any shadow session, the NX client message is
NX> 203 NXSSH running with pid: 4988
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
ssh: connect to host xxx.yyy port 22: Connection refused
3. When using the Nomachine server (the free version) I get a list of
available suspended sessions when connecting, and I'm presented with several
options: connect to an already running session, open a new one, terminate an
already existing session. When using the freenx server I don't get these
options, I'm directly connected to the suspended session. Do youy know why?
Thanks,
Adrian
On Tue, Aug 19, 2008 at 6:43 PM, albinootje <albinootje@gmail.com> wrote:
> Adrian Coman wrote:
>
> hi,
>
> > I've got a server with 8G of memory, so I need to have a 64b distro. I
> can
> > connect and start a NX session, but when I want to close the NX Client
> > application, the disconnect/terminate/cancel window is not accesible.
> > Basically I can only close the NX Client application by windows task
> manager
> > ... When I press the close button of the NX client window, nothing
> happens.
>
> which linux-distribution and which FreeNX server version are you using ?
>
> FreeNX 0.7.1 server has this in the changelog :
>
> * Added 'dialog_interface=dialog' option since many
> installations may
> not have Xdialog and since xmessage is very limiting. This new
> option
> will work on any machine that has dialog and xterm.
> (puterguy@bat.berlios.de)
>
> so i assume that any version before that needs the Xdialog software
> installed,
> do you have that installed ?
>
>
>
> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
> http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
> Don't forget to check the NX Knowledge Base:
> http://www.nomachine.com/kb/
>
> ________________________________________________________________
> FreeNX-kNX mailing list --- FreeNX-kNX@kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>
[Attachment #5 (text/html)]
<div dir="ltr">1. The problem I mentioned earlier is fixed, I can now \
disconnect/terminate a session.<div><div style="margin-left: 40px;"><br>However I \
have another issue: when connecting to a session (new or resumed) the NX client keeps \
a window saying "negotiating link parameters" even after the session is \
started. After ~1min the NX session is automatically closed (suspended).The NX server \
log is saying:<br> <br>NX> 596 Error: Session failed. Reason was: Session: \
Display failure detected at 'Tue Aug 19 20:36:10 2008'.<br>NX> 1009 \
Session status: suspending<br>NX> 1005 Session status: suspended<br><br>Here is my \
config:<br> <br>distribuition: CentOS 4.6, 64 \
bits<br><br>freenx-0.7.2-3.el4.centos<br>nx-3.2.0-8.el4.centos<br></div><br></div><div><div>2. \
I can not start any shadow session, the NX client message is<br><br><div \
style="margin-left: 40px;"> NX> 203 NXSSH running with pid: 4988<br>NX> 285 \
Enabling check on switch command<br>NX> 285 Enabling skip of SSH config \
files<br>NX> 285 Setting the preferred NX options<br>ssh: connect to host xxx.yyy \
port 22: Connection refused<br> </div><br>3. When using the Nomachine server (the \
free version) I get a list of available suspended sessions when connecting, and \
I'm presented with several options: connect to an already running session, open a \
new one, terminate an already existing session. When using the freenx server I \
don't get these options, I'm directly connected to the suspended session. Do \
youy know why?<br> <br><br>Thanks,<br>Adrian<br><br><div class="gmail_quote">On Tue, \
Aug 19, 2008 at 6:43 PM, albinootje <span dir="ltr"><<a \
href="mailto:albinootje@gmail.com">albinootje@gmail.com</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d">Adrian \
Coman wrote:<br> <br>
hi,<br>
<br>
> I've got a server with 8G of memory, so I need to have a 64b distro. I \
can<br> > connect and start a NX session, but when I want to close the NX \
Client<br> > application, the disconnect/terminate/cancel window is not \
accesible.<br> > Basically I can only close the NX Client application by windows \
task manager<br> > ... When I press the close button of the NX client window, \
nothing happens.<br> <br>
</div>which linux-distribution and which FreeNX server version are you using ?<br>
<br>
FreeNX 0.7.1 server has this in the changelog :<br>
<br>
* Added 'dialog_interface=dialog' option since \
many<br> installations may<br>
not have Xdialog and since xmessage is very \
limiting. This new<br> option<br>
will work on any machine that has dialog and \
xterm.<br> (<a \
href="mailto:puterguy@bat.berlios.de">puterguy@bat.berlios.de</a>)<br> <br>
so i assume that any version before that needs the Xdialog software<br>
installed,<br>
do you have that installed ?<br>
<br>
<br>
<br>
________________________________________________________________<br>
Were you helped on this list with your FreeNX problem?<br>
Then please write up the solution in the FreeNX Wiki/FAQ:<br>
<a href="http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ" \
target="_blank">http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ</a><br> \
Don't forget to check the NX Knowledge Base:<br> \
<a \
href="http://www.nomachine.com/kb/" \
target="_blank">http://www.nomachine.com/kb/</a><br> <br>
________________________________________________________________<br>
FreeNX-kNX mailing list --- <a \
href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a><br> <a \
href="https://mail.kde.org/mailman/listinfo/freenx-knx" \
target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br> \
________________________________________________________________<br> \
</blockquote></div><br></div></div></div>
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:
http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
Don't forget to check the NX Knowledge Base:
http://www.nomachine.com/kb/
________________________________________________________________
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