windows shadowing of local session disconnects immediately, works in linux though

Bug #605820 reported by Matt B
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
FreeNX Server
New
Undecided
Unassigned

Bug Description

I'm using freenx-server from freenx-server_0.7.3+teambzr104-0freenxteam1~hardy1_i386.deb

Shadowing local sessions works fine from linux clients, both in the nomachine web application (java applet) and nomachine linux client. However, shadowing local sessions fails on windows clients (tested on windows xp and windows 7), with an immediate disconnect.

I used to use the nomachine free server and it didn't have the problem with shadowing sessions from windows.
Freenx-0.7.3 will authenticate fine from windows, but there is a delay once the local session is clicked on and before the display window is opened, that isn't there when I connect from Linux. As soon as it opens the display window and shows the !M icon, it closes, and gives an error:
The connection with the remote server was shut down.
Please check the state of your network connection.
I am able to shadow existing nx sessions from windows, but not the local session. However, I can shadow the local session from linux.

This happens from both the web application and the desktop application (as expected).

The other weird thing is that when there are more sessions open (shadowing the local session) and you try to select them from the dropdown list in the nomachine connection dialog, it will hop back to the top one in the list (which is not the local session). If I hold down control, and click Attach it will attach but still fail as above.

Here is my package list (from dpkg):
rc freenx-media 0.7.3+teambzr104-0freenxteam1~hardy1 Remote desktop/application/thin-client server media support
ii freenx-server 0.7.3+teambzr104-0freenxteam1~hardy1 Remote desktop/application/thin-client server core features
ri freenx-session-launcher 0.7.3+teambzr104-0freenxteam1~hardy1 Remote desktop/application/thin-client server ConsoleKit helper
ii libxcompshad3 3.3.0-2-0freenxteam1~hardy1 NoMachine NX - NX compression library

See below for my nxserver log. I set logging to 7.
I looked through node.conf but didn't see any particular issues.
If this issue is corrected in new builds and I can fix it by building from source please let me know (or if there are new packages ).

NX> 148 Server capacity: not reached for user: .*
NX> 105 attachsession --link="modem" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" --imagecompressionmethod="0" --render="1" --session="my.server.com" --type="shadow" --client="winnt" --keyboard="pc102/en_US" --id="D23B5212DC27F20148B58678A351610C" --display="0"

Info: Using /etc/nxserver/nxacl to change session parameters or deny session.
&link=modem&backingstore=1&encryption=1&cache=16M&images=64M&shmem=1&shpix=1&strict=0&composite=1&media=0&imagecompressionmethod=0&render=1&session=my.server.com&type=shadow&client=winnt&keyboard=pc102/en_US&id=D23B5212DC27F20148B58678A351610C&display=0&clientproto=3.2.0&login_method=SSH&shadowdisplay=0&shadowhost=&shadowcookie=******&user=dnsadmin&userip=91.62.124.188&uniqueid=D6E125FDBE741B020EFD55152917CC93&display=1009&host=127.0.0.1
nxnode_reader: NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.3.0)
NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.3.0)
server_nxnode_echo: NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.3.0)
nxnode_reader: NX> 700 Session id: my.server.com-1009-D6E125FDBE741B020EFD55152917CC93
nxnode_reader: NX> 705 Session display: 1009
nxnode_reader: NX> 703 Session type: shadow
nxnode_reader: NX> 701 Proxy cookie: d047aade802046935d176dfc0d2a5200
nxnode_reader: NX> 702 Proxy IP: 127.0.1.1
nxnode_reader: NX> 706 Agent cookie: d047aade802046935d176dfc0d2a5200
nxnode_reader: NX> 704 Session cache: shadow
nxnode_reader: NX> 707 SSL tunneling: 1
NX> 700 Session id: my.server.com-1009-D6E125FDBE741B020EFD55152917CC93
NX> 705 Session display: 1009
NX> 703 Session type: shadow
NX> 701 Proxy cookie: d047aade802046935d176dfc0d2a5200
NX> 702 Proxy IP: 127.0.1.1
NX> 706 Agent cookie: d047aade802046935d176dfc0d2a5200
NX> 704 Session cache: shadow
NX> 707 SSL tunneling: 1
server_nxnode_echo: NX> 700 Session id: my.server.com-1009-D6E125FDBE741B020EFD55152917CC93
server_nxnode_echo: NX> 705 Session display: 1009
server_nxnode_echo: NX> 703 Session type: shadow
server_nxnode_echo: NX> 701 Proxy cookie: d047aade802046935d176dfc0d2a5200
server_nxnode_echo: NX> 702 Proxy IP: 127.0.1.1
nxnode_reader: NX> 1009 Session status: starting
NX> 1009 Session status: starting
nxnode_reader: NX> 710 Session status: running
NX> 710 Session status: running
nxnode_reader: NX> 1002 Commit
NX> 1002 Commit
nxnode_reader: NX> 1006 Session status: running
NX> 1006 Session status: running
server_nxnode_echo: NX> 706 Agent cookie: d047aade802046935d176dfc0d2a5200
server_nxnode_echo: NX> 704 Session cache: shadow
server_nxnode_echo: NX> 707 SSL tunneling: 1
server_nxnode_echo: NX> 1009 Session status: starting
server_nxnode_echo: NX> 710 Session status: running
server_nxnode_echo: NX> 1002 Commit
session_status D6E125FDBE741B020EFD55152917CC93 Running
NX> 105 server_nxnode_echo: NX> 1006 Session status: running
bye
Bye
NX> 999 Bye
Info: Closing connection to slave with pid 30207.
nxnode_reader: 1001 Bye.
1001 Bye.
nxnode_reader: NX> 1001 Bye.
NX> 1001 Bye.
server_nxnode_echo: NX> 1001 Bye.
Info: Closing connection to slave with pid 30207.

Revision history for this message
Jeremy Wilkins (wjeremy) wrote :

I will have a look at this on Saturday. It seems to be a video display color depth issue. We had a similar problem with session resuming a while back. If the shadow session tries to start in 24bit color depth but the server tries to match the color depth that could cause a problem. Windows sessions now are almost always 32bit color. It can be fixed because 24bit color in Linux and 32bit color in windows is still for the most part compatible.

Revision history for this message
Matt B (mattbecker3240) wrote :

any updates on this one? I'd love to see freenx able to shadow from windows clients.

Revision history for this message
Jeremy Wilkins (wjeremy) wrote :

Unfortunately my time is spread too thin right now and I am sick for the next 10 days. My first opportunity to look at this won't be until the week of Sep 6 while I am on holidays.

Revision history for this message
Jeremy Wilkins (wjeremy) wrote :

If the patch foe bug #589723 fixes it let me know. It is here:
https://bugs.launchpad.net/freenx-server/+bug/589723

Revision history for this message
Matt B (mattbecker3240) wrote :

I don't think that this is a color issue (at least on my setup with hardy (ubuntu 8.04) and freenx 0.7.3+teambzr104-0freenxteam1~hardy1

as it occurs even when I put color depth to 24 bit on windows xp. Also those two lines are already in my /usr/bin/nxserver:

depth=$(getparam screeninfo | cut -d "x" -f3 | cut -d "+" -f1 )
                        [ "$depth" = "32" ] && depth=24
                        geom=$(getparam screeninfo | cut -d "x" -f1,2)
                        render=$(getparam screeninfo | cut -d "+" -f2 )
                        available="N/A"
                        udepth=$(echo $3 | cut -d "x" -f3 | cut -d "+" -f1 )
                        [ "$udepth" = "32" ] && udepth=24
                        urender=$(echo $3 | cut -d "+" -f2 )

I tried adding the hack from Marcus as well,

stringinstring "unix-" "$4" || available="N/A"
+ available="$(getparam status)"

but it also didn't resolve the issue.

nxclient still exits when I try to shadow system session from windows (works from linux just fine of course)

Revision history for this message
Jeremy Wilkins (wjeremy) wrote :

Are both the Windows and Linux machines remote?

Revision history for this message
Matt B (mattbecker3240) wrote : Re: [Bug 605820] Re: windows shadowing of local session disconnects immediately, works in linux though
Download full text (6.2 KiB)

no the clients are both local (my desktop :-) machine )
The server is remote, it's an ubuntu hardy machine.

--- On Fri, 9/3/10, Jeremy Wilkins <email address hidden> wrote:

From: Jeremy Wilkins <email address hidden>
Subject: [Bug 605820] Re: windows shadowing of local session disconnects immediately, works in linux though
To: <email address hidden>
Date: Friday, September 3, 2010, 5:20 AM

Are both the Windows and Linux machines remote?

--
windows shadowing of local session disconnects immediately, works in linux though
https://bugs.launchpad.net/bugs/605820
You received this bug notification because you are a direct subscriber
of the bug.

Status in FreeNX open source NX Server: New

Bug description:
I'm using freenx-server from freenx-server_0.7.3+teambzr104-0freenxteam1~hardy1_i386.deb

Shadowing local sessions works fine from linux clients, both in the nomachine web application (java applet) and nomachine linux client. However, shadowing local sessions fails on windows clients (tested on windows xp and windows 7), with an immediate disconnect.

I used to use the nomachine free server and it didn't have the problem with shadowing sessions from windows.
Freenx-0.7.3 will authenticate fine from windows, but there is a delay once the local session is clicked on and before the display window is opened, that isn't there when I connect from Linux. As soon as it opens the display window and shows the !M icon, it closes, and gives an error:
The connection with the remote server was shut down.
Please check the state of your network connection.
I am able to shadow existing nx sessions from windows, but not the local session. However, I can shadow the local session from linux.

This happens from both the web application and the desktop application (as expected).

The other weird thing is that when there are more sessions open (shadowing the local session) and you try to select them from the dropdown list in the nomachine connection dialog, it will hop back to the top one in the list (which is not the local session). If I hold down control, and click Attach it will attach but still fail as above.

Here is my package list (from dpkg):
rc  freenx-media                               0.7.3+teambzr104-0freenxteam1~hardy1                 Remote desktop/application/thin-client server media support
ii  freenx-server                              0.7.3+teambzr104-0freenxteam1~hardy1                 Remote desktop/application/thin-client server core features
ri  freenx-session-launcher                    0.7.3+teambzr104-0freenxteam1~hardy1                 Remote desktop/application/thin-client server ConsoleKit helper
ii  libxcompshad3                              3.3.0-2-0freenxteam1~hardy1                          NoMachine NX - NX compression library

See below for my nxserver log. I set logging to 7.
I looked through node.conf but didn't see any particular issues.
If this issue is corrected in new builds and I can fix it by building from source please let me know (or if there are new packages ).

NX> 148 Server capacity: not reached for user: .*
NX> 105 attachsession  --link="modem" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1...

Read more...

Revision history for this message
Jeremy Wilkins (wjeremy) wrote :

So you are referring to shadowing of the X0 local session? I just need to make sure I have all the parameters of this scenario so I can recreate it myself.

Revision history for this message
Jeremy Wilkins (wjeremy) wrote :

For me session shadowing is not working at all, so I need to fix it anyhow apparently.

Revision history for this message
Matt B (mattbecker3240) wrote :

Hi Jeremy,

yes this is shadowing local session only, creating and shadowing nx sessions works fine (for me anyway) from linux and windows.

Revision history for this message
Jeremy Wilkins (wjeremy) wrote :

Ok, now that I have resolved the problems with shadowing any local X0 sessions on Kubuntu 10.04 I can actually get to fixing the problem at hand for windows client shadowing of the local X0 session. The reason I am using the 10.04 version is because i do not have a Hardy system at hand to test on. Also, any new release I will make for Hardy will be based on the 10.04 sources.
Apparently the session caching was killing the local X0 session information, so it would fail to shadow at all. I will test Windows shadowing another day. It is late now.

Revision history for this message
Matt B (mattbecker3240) wrote :
Download full text (6.7 KiB)

Hi Jeremy,

any progress on this as far as the windows shadowing of an ubuntu hardy freenx server local session?

thanks,

Matt

--- On Mon, 10/25/10, Jeremy Wilkins <email address hidden> wrote:

From: Jeremy Wilkins <email address hidden>
Subject: [Bug 605820] Re: windows shadowing of local session disconnects immediately, works in linux though
To: <email address hidden>
Date: Monday, October 25, 2010, 7:49 AM

Ok, now that I have resolved the problems with shadowing any local X0 sessions on Kubuntu 10.04 I can actually get to fixing the problem at hand for windows client shadowing of the local X0 session.  The reason I am using the 10.04 version is because i do not have a Hardy system at hand to test on.  Also, any new release I will make for Hardy will be based on the 10.04 sources.
Apparently the session caching was killing the local X0 session information, so it would fail to shadow at all.  I will test Windows shadowing another day.  It is late now.

--
windows shadowing of local session disconnects immediately, works in linux though
https://bugs.launchpad.net/bugs/605820
You received this bug notification because you are a direct subscriber
of the bug.

Status in FreeNX open source NX Server: New

Bug description:
I'm using freenx-server from freenx-server_0.7.3+teambzr104-0freenxteam1~hardy1_i386.deb

Shadowing local sessions works fine from linux clients, both in the nomachine web application (java applet) and nomachine linux client. However, shadowing local sessions fails on windows clients (tested on windows xp and windows 7), with an immediate disconnect.

I used to use the nomachine free server and it didn't have the problem with shadowing sessions from windows.
Freenx-0.7.3 will authenticate fine from windows, but there is a delay once the local session is clicked on and before the display window is opened, that isn't there when I connect from Linux. As soon as it opens the display window and shows the !M icon, it closes, and gives an error:
The connection with the remote server was shut down.
Please check the state of your network connection.
I am able to shadow existing nx sessions from windows, but not the local session. However, I can shadow the local session from linux.

This happens from both the web application and the desktop application (as expected).

The other weird thing is that when there are more sessions open (shadowing the local session) and you try to select them from the dropdown list in the nomachine connection dialog, it will hop back to the top one in the list (which is not the local session). If I hold down control, and click Attach it will attach but still fail as above.

Here is my package list (from dpkg):
rc  freenx-media                               0.7.3+teambzr104-0freenxteam1~hardy1                 Remote desktop/application/thin-client server media support
ii  freenx-server                              0.7.3+teambzr104-0freenxteam1~hardy1                 Remote desktop/application/thin-client server core features
ri  freenx-session-launcher                    0.7.3+teambzr104-0freenxteam1~hardy1                 Remote desktop/application/thin-client server ConsoleKit helper
ii  libxcompshad3           ...

Read more...

Revision history for this message
Jeremy Wilkins (wjeremy) wrote :

I am getting the same effect when shadowing from Windows on a lucid system as well even after the session shadowing fixes have been implemented for lucid so i suspect this may be an even deeper problem into the core of how the Windows session is being viewed on the remote screen. It seems more like the session itself is crashing. I will continue to trace the issue.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.