headers
Marcelo Taube | 21 Jun 2012 15:28
Picon

The nomachine window dissapears when connecting to freenx from windows 7

Hi
I am trying to connect to my workstation where i installed freenx server. It is a fedora 16.
I open the nomachine client in my windows 7 laptop, configure for shadow session, enter password and select the session from the list, the nx screen pops up displaying the nx symbol and immediately dissapears.
If i do the same from the local linux desktop where freenx is running the nx window works properly and shows my Xsession.
There are no firewalls configured ini any of the computers and they share the same LAN.
It is strange that I get no error message in the windows client, just the window gets hidden. The server continues to insist that the session is established and running (if i try to connect from another client). I see that the nxnode and nxagent processes are up and running and that there is a opened TCP connectiong to the client. As if everything was working properly but i see no window opened.
When i check the nxlogs I don't see much difference between the two connections. The file nxserver.log looks almost the same.
The .nx directory looks pretty ok.
I made real effort to fix this but i was not able to understand what is the problem .
Anyway, I was hoping that someone here could help. I attach log files and outputs in order to make easier on you to help me.
Thanks :)
Marcelo


(notice that in all this logs my domain name and ip address where changed because of privacy issues)

In .nx directory after connecting from windows:
errors file is emptu
options:
nx/nx,keyboard=pc102/en_US,client=winnt,cache=16M,images=64M,link=adsl,nodelay=1,type=shadow,clipboard=both,cleanup=0,product=LFE/None/LFEN/None,shmem=1,backingstore=1,shpix=1,accept=11.21.30.65,cookie=e837a1e993d9a7b058fda822654fb3a8,id=marcelot-fd-2005-B44575C2813A4B3EBA80FDFC53B8B6A8,samba=0,media=0,menu=1:2005

session:
NXAGENT - Version 3.5.0

Copyright (C) 2001, 2011 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Agent running with pid '20265'.
Session: Starting session at 'Thu Jun 21 15:48:47 2012'.
Info: Proxy running in server mode with pid '20265'.
Info: Waiting for connection from '11.21.30.65' on port '6005'.
Info: Accepted connection from '11.21.30.65'.
Info: Connection with remote proxy completed.
Info: Using ADSL link parameters 512/24/1/0.
Info: Using agent parameters 5000/10/50/0/0.
Info: Using cache parameters 4/4096KB/16384KB/16384KB.
Info: Using pack method 'adaptive-7' with session 'shadow'.
Info: Using product 'LFE/None/LFEN/None'.
Info: Using ZLIB data compression 1/1/32.
Info: Using ZLIB stream compression 4/4.
Info: No suitable cache file found.
Info: Listening to X11 connections on display ':2005'.
Info: Established X client connection.
Info: Using shared memory parameters 1/1/0/0K.
Info: Using alpha channel in render extension.
Info: Using local device configuration changes.
Poller::shmInit: WARNING! Couldn't set uid for shm segment.
Session: Session started at 'Thu Jun 21 15:48:52 2012'.
Info: Screen [0] resized to geometry [1920x1200] fullscreen [1].




/var/log/nx/nxserver.log when i succeed (connecting from linux):
-- NX SERVER START: -c /usr/libexec/nx/nxserver - ORIG_COMMAND=
-- NX SERVER START:  - ORIG_COMMAND=
Info: Using fds #4 and #3 for communication with nxnode.
HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
NX> 105 hello NXCLIENT - Version 3.2.0
NX> 134 Accepted protocol: 3.2.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: marcelot
NX> 102 Password: 
NX> 103 Welcome to: marcelot-fd user: marcelot
NX> 105 listsession --type="shadow"
NX> 127 Sessions list of user '.*' for reconnect:

Display Type             Session ID                       Options  Depth Screen         Status      Session Name
------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------
0       Local            679AF1D9781BC7B4AC144FD0EB3564FC --------                      Running     X0 (Local)
2       Local            4E7C5D0D34C902895701B9845D63EF29 --------                      Running     X2 (Local)
2       Local            A644E549A262F52F302853E73AD6A143 --------                      Running     X2 (Local)
0       Local            BE77ED951144F03C3A18C25774D7E3A1 --------                      Running     X0 (Local)


NX> 148 Server capacity: not reached for user: .*
NX> 105 attachsession  --link="adsl" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" --session="marcelot" --type="shadow" --client="linux" --keyboard="pc105/us" --id="BE77ED951144F03C3A18C25774D7E3A1" --display="0"

NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
NX> 700 Session id: marcelot-fd-2005-07B578C6467D56E783F010E8A40024DC
NX> 705 Session display: 2005
NX> 703 Session type: shadow
NX> 701 Proxy cookie: 815c12877f87c251cce1730b11533ac4
NX> 702 Proxy IP: 11.21.20.46
NX> 706 Agent cookie: 815c12877f87c251cce1730b11533ac4
NX> 704 Session cache: shadow
NX> 707 SSL tunneling: 1
NX> 1009 Session status: starting
NX> 710 Session status: running
NX> 1002 Commit
NX> 1006 Session status: running
NX> 105 bye
Bye
NX> 999 Bye
NX> 1009 Session status: terminating
Info: Closing connection to slave with pid 18644.
1001 Bye.
NX> 1006 Session status: closed
NX> 1001 Bye.
Info: Closing connection to slave with pid 18644.

/var/log/nx/nxserver.log when i succeed (connecting from windows):

Info: Using fds #4 and #3 for communication with nxnode.
HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
NX> 105 hello NXCLIENT - Version 3.2.0
NX> 134 Accepted protocol: 3.2.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: marcelot
NX> 102 Password:
NX> 103 Welcome to: marcelot-fd user: marcelot
NX> 105 listsession --type="shadow"
NX> 127 Sessions list of user '.*' for reconnect:

Display Type             Session ID                       Options  Depth Screen         Status      Session Name
------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------
0       Local            679AF1D9781BC7B4AC144FD0EB3564FC --------                      Running     X0 (Local)
2       Local            4E7C5D0D34C902895701B9845D63EF29 --------                      Running     X2 (Local)
2       Local            A644E549A262F52F302853E73AD6A143 --------                      Running     X2 (Local)
0       Local            BE77ED951144F03C3A18C25774D7E3A1 --------                      Running     X0 (Local)


NX> 148 Server capacity: not reached for user: .*
NX> 105 attachsession  --link="adsl" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" --session="marcelot" --type="shadow" --client="linux" --keyboard="pc105/us" --id="BE77ED951144F03C3A18C25774D7E3A1" --display="0"

NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
NX> 700 Session id: marcelot-fd-2005-07B578C6467D56E783F010E8A40024DC
NX> 705 Session display: 2005
NX> 703 Session type: shadow
NX> 701 Proxy cookie: 815c12877f87c251cce1730b11533ac4
NX> 702 Proxy IP: 11.21.20.46
NX> 706 Agent cookie: 815c12877f87c251cce1730b11533ac4
NX> 704 Session cache: shadow
NX> 707 SSL tunneling: 1
NX> 1009 Session status: starting
NX> 710 Session status: running
NX> 1002 Commit
NX> 1006 Session status: running
NX> 105 bye
Bye
NX> 999 Bye
NX> 1009 Session status: terminating
Info: Closing connection to slave with pid 18644.
1001 Bye.
NX> 1006 Session status: closed
NX> 1001 Bye.
Info: Closing connection to slave with pid 18644.


Open processes in server after connecting from windows:
# ps ax | grep nx
17260 ?        Ss     0:00 sshd: nx [priv]     
17262 ?        S      0:00 sshd: nx <at> notty      
17263 ?        Ss     0:00 /bin/bash /usr/libexec/nx/nxserver
19437 ?        Ss     0:00 sshd: nx [priv]     
19439 ?        S      0:00 sshd: nx <at> notty      
19440 ?        Ss     0:00 /bin/bash /usr/libexec/nx/nxserver
19587 ?        S      0:00 /bin/bash /usr/libexec/nx/nxserver
19588 ?        S      0:00 /usr/bin/expect /usr/libexec/nx/nxnode-login -- ssh marcelot 22 /usr/libexec/nx/nxnode --slave
19589 pts/20   Ss+    0:00 ssh -2 -x -l marcelot 127.0.0.1 -o NumberOfPasswordPrompts 1 -p 22 /usr/libexec/nx/nxnode --slave
19597 ?        Ss     0:00 /bin/bash /usr/libexec/nx/nxnode --slave
19995 ?        S      0:00 /bin/bash /usr/libexec/nx/nxserver
19998 ?        S      0:00 /bin/bash /usr/libexec/nx/nxserver
19999 ?        S      0:00 /bin/bash /usr/libexec/nx/nxserver
20014 ?        S      0:00 /bin/bash /usr/libexec/nx/nxserver
20015 ?        S      0:00 tee -a /var/log/nx/nxserver.log
20016 ?        S      0:00 /bin/bash /usr/libexec/nx/nxnode --slave
20018 ?        S      0:00 /bin/bash /usr/libexec/nx/nxnode --startsession
20255 ?        S      0:00 /bin/bash /usr/libexec/nx/nxnode --startsession
20258 ?        S      0:00 /bin/bash /usr/libexec/nx/nxnode --startsession
20259 ?        S      0:00 tee /home/marcelot/.nx/C-marcelot-fd-2005-B44575C2813A4B3EBA80FDFC53B8B6A8/session
20260 ?        S      0:00 /bin/bash /usr/libexec/nx/nxnode --startsession
20265 ?        S      0:22 /usr/libexec/nx/nxagent -nopersistent -S -shadow :0 -shadowmode 1 -name NX - marcelot <at> marcelot-fd:2005 - marcelo (GPL Edition) -option /home/marcelot/.nx/C-marcelot-fd-2005-B44575C2813A4B3EBA80FDFC53B8B6A8/options -nolisten tcp :2005

Open connectiongs in server after connecting from windows:
# lsof -i | grep nx
sshd      17262       nx    3u  IPv4 2311801      0t0  TCP 11.21.20.46:ssh->netsrv.mydomain.com:54273 (ESTABLISHED)
sshd      17262       nx    9u  IPv6 2311835      0t0  TCP localhost:x11-ssh-offset (LISTEN)
sshd      17262       nx   10u  IPv4 2311836      0t0  TCP localhost:x11-ssh-offset (LISTEN)
sshd      19439       nx    3u  IPv4 2340061      0t0  TCP 11.21.20.46:ssh->11.21.30.65:54458 (ESTABLISHED)
sshd      19439       nx    9u  IPv6 2340081      0t0  TCP localhost:6012 (LISTEN)
sshd      19439       nx   10u  IPv4 2340082      0t0  TCP localhost:6012 (LISTEN)
ssh       19589       nx    3u  IPv4 2335584      0t0  TCP localhost:34930->localhost:ssh (ESTABLISHED)
nxagent   20265 marcelot    9u  IPv4 2340335      0t0  TCP 11.21.20.46:6005->11.21.30.65:54462 (ESTABLISHED)

Attachment (node.conf): application/octet-stream, 22 KiB
________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
Permalink | Reply | 9 comments |
headers
chris | 25 Jun 2012 10:53
Favicon

Re: The nomachine window dissapears when connecting to freenx from windows 7


freenx-knx-bounces <at> kde.org wrote on 21/06/2012 14:28:39:

> Hi
> I am trying to connect to my workstation where i installed freenx
> server. It is a fedora 16.
> I open the nomachine client in my windows 7 laptop,

There are/were a few potential issues with win7 eg. 8.3 namespace . . .

> configure for shadow session, enter password and select
> the session from the list,

This shows that you can actually connect to FreeNX . . .


Did you try without shadowing or reconnecting ??


> the nx screen pops up displaying the nx symbol and
> immediately dissapears.

Is the client (nxssh) still running on windows after this ???

What's in the client session log on windows ???

> If i do the same from the local linux desktop where freenx
> is running the nx window works properly and shows my Xsession.

So it's probably a windows/nxclient issue (or shadowing)

[SNIP]

NOTE
If the connection is still up you will see an associated:-
         netcat 127.0.0.1 port
spawned by an nx owned nxserver process

So

Try without shadowing.
Try starting NEW session from windows and see if that works.
Check if the nxclient nxssh is sill running on windows
        after your connect attempts fail.
Have a look for a helpful error message in the windows
         session log.

Look in the nomachine knowledgebase for nxclient/windows7
        and ensure you haven't signed up for a known issue.

http://www.nomachine.com/ar/index.php?search_adv=2&src=1&pattern=windows+7&applies_to=NX+Client+Products&filter=0&date=all_date&src=1&x=0&y=0 





________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
Permalink | Reply | 8 comments |
headers
Marcelo Taube | 27 Jun 2012 14:31
Picon

Re: The nomachine window dissapears when connecting to freenx from windows 7


Hi,
Thanks Chris for providing some options. Have some answers following.
Good day

 
Did you try without shadowing or reconnecting ??


I now have tried without shadowing and succeeded. It seems that the last time i tried without shadow the system was unable to load the window manager, now tried with gnome and seems all right. Still I would like to connect using shadow

 

> the nx screen pops up displaying the nx symbol and
> immediately dissapears.

Is the client (nxssh) still running on windows after this ???

Yep, i see "nxxssh.exe *32" cpu 01% mem 18,616 K (and rising) in the task manager at pid 6008

 
What's in the client session log on windows ???

Here is the session file on windows:
Info: Display running with pid '5840' and handler '0x8031e'.

NXPROXY - Version 3.5.0

Copyright (C) 2001, 2011 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Proxy running in client mode with pid '6008'.
Session: Starting session at 'Wed Jun 27 14:58:19 2012'.
Info: Connecting to remote host '11.21.20.46:6006'.
Info: Connection to remote proxy '11.21.20.46:6006' established.
Info: Connection with remote proxy completed.
Info: Using ADSL link parameters 512/24/1/0.
Info: Using cache parameters 4/4096KB/131072KB/131072KB.
Info: Using pack method 'adaptive-7' with session 'shadow'.
Info: Using ZLIB data compression 1/1/32.
Info: Using ZLIB stream compression 4/4.
Info: Using cache file 'd:\Users\marcelot\NXC495~1/cache-shadow/S-FA0BEEA94F91AD92742BA43135E7E631'.
Info: Forwarding X11 connections to display ':0'.
Info: Listening to font server connections on port '12006'.
Session: Session started at 'Wed Jun 27 14:58:20 2012'.
Info: Established X server connection.
Info: Using shared memory parameters 0/0K.


I also tried reconnecting as you recommended, attaching to session 2006 brings a new nx client window that this time does not dissapear but it looks completely black and never updates.

If I kill all the nx processes in windows and reconnect, the session 2006 gets unlisted and then I can try to shadow the original :0 X server but with the same luck that I had before.

Checked the knowledge base but found almost nothing. There was nothing mentioning windows 7 in this way. Someone mentioned that black screen  might happen if the server does not support shared memory. Do you think it might be the problem?

Any other ideas?
________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
Permalink | Reply | 7 comments |
headers
chris | 28 Jun 2012 11:55
Favicon

Re: The nomachine window dissapears when connecting to freenx from windows 7


freenx-knx-bounces <at> kde.org wrote on 27/06/2012 13:31:55:

> Hi,
[SNIP]
> I now have tried without shadowing and succeeded. It seems that the

OK so, sounds like it's just shadowing not windows . . .

> last time i tried without shadow the system was unable to load the
> window manager, now tried with gnome and seems all right. Still I

This sounds like a Linux issue. Was there an error message??
Did the same configuration work without an NX involvement??

[SNIP
> What's in the client session log on windows ???
[SNIP]

No windows error messages . . .

[SNIP]
> Checked the knowledge base but found almost nothing.
> There was nothing mentioning windows 7 in this way.
> Someone mentioned that black screen  might happen if the
> server does not support shared memory.
> Do you think it might be the problem?

Well do you see :-
 
Xlib:  extension "MIT-SHM" missing on display ":XXXX.0".

. . .in your logs ?? Are you running an old nxclient ??

http://www.nomachine.com/tr/view.php?id=TR08G02256


> Any other ideas?

Well . . .

You report no error messages and your window client
connect fine without shadowing.

You say you managed to get shadowing working from
Linux, which suggested you know how it works . . .

but
in your original post you are trying to connect
to a Local session.

0 Local BE77ED951144F03C3A18C25774D7E3A1 -------- Running X0 (Local)

NX Shadowing will only connect to another running
NX session.

If you want to connect to your Local session instead,
you need to run a vncserver in your Local session,
select VNC (not Shadow) in nxclient and point it at
the vncserver port.

NX will then speed up your VNC session.

I couldn't say why your Win7 nxclient window is
vanishing, you should just get the black window. 










________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
Permalink | Reply | 6 comments |
headers
Marcelo Taube | 28 Jun 2012 14:51
Picon

Re: The nomachine window dissapears when connecting to freenx from windows 7


> last time i tried without shadow the system was unable to load the
> window manager, now tried with gnome and seems all right. Still I

This sounds like a Linux issue. Was there an error message??
Did the same configuration work without an NX involvement??
Dont worry about this one, gnome is ok, I am sure the window manager issue is probably a misconfiguration and it is more important to get the shadowing working.
I see an interesting line at the first logs i sent you in this mail thread:
Poller::shmInit: WARNING! Couldn't set uid for shm segment
Its on the server side and I see it is related to shared memory. 

> Checked the knowledge base but found almost nothing.
> There was nothing mentioning windows 7 in this way.
> Someone mentioned that black screen  might happen if the
> server does not support shared memory.
> Do you think it might be the problem?

Well do you see :-
 
Xlib:  extension "MIT-SHM" missing on display ":XXXX.0".

. . .in your logs ??

Which logs do you mean? Its not in the .nx directory in linux neither in the .nx directory on windows and not in /var/log/nx.

 
Are you running an old nxclient ??

http://www.nomachine.com/tr/view.php?id=TR08G02256

Its nxclient 3.5.0-9 here, I think it is the up to date version.

 
> Any other ideas?

Well . . .

You report no error messages and your window client
connect fine without shadowing.

You say you managed to get shadowing working from
Linux, which suggested you know how it works . . .

but
in your original post you are trying to connect
to a Local session.

0 Local BE77ED951144F03C3A18C25774D7E3A1 -------- Running X0 (Local)

NX Shadowing will only connect to another running
NX session.

Strange. I connected from linux to my local session by choosing shadow and the chossing the :0 from the list of opened sessions. I even opened the nx window inside the local screen and got the nice recursive view of my screen .So if should not be able to connect to the local screenm It surprises me that I managed to do it somehow.

Still I know that vnc server was enabled on that client which could be the cause, but I did not choose vnc server from the connection options of nxclient, i just choose shadow.
 
Other relevant facts:

Even when I succeed to start a non-shadow session, I am not able to reconnect if I close the nx window. I reopen the connection to linux, choose "unix" and not "shadow" my old session gets displayed in the list but It fails to connect to it.
Two windows eventually pop up, one says " Could not yet establish the connection to the remote proxy. Do you want to terminate the current session? " . Later another window pops up saying: " 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 unchecking the option 'Disable SSL encryption in all traffic' in the configuration dialog" .

If i try to connect to the old session with "shadow" after I close the window it does not get listed at all. 
When i tryed to connect to that session through "shadow" before I close the window I succeed completely.

To summarize I can connect to new unix sessions and shadow sessions while someone is connected.
I cannot connect to my local view from windows but yes from linux. I cannot reconnect to old unix sessions through "unix" option or "shadow" option.

________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
Permalink | Reply | 5 comments |
headers
chris | 29 Jun 2012 21:58
Favicon

Re: The nomachine window dissapears when connecting to freenx from windows 7


freenx-knx-bounces <at> kde.org wrote on 28/06/2012 13:51:35:
[SNIP]
>  
> > Any other ideas?
>
> Well . . .
>
> You report no error messages and your window client
> connect fine without shadowing.
>
> You say you managed to get shadowing working from
> Linux, which suggested you know how it works . . .
>
> but
> in your original post you are trying to connect
> to a Local session.
>
> 0 Local BE77ED951144F03C3A18C25774D7E3A1 -------- Running X0 (Local)

> NX Shadowing will only connect to another running
> NX session.

 . . . due to a bug in nxserver in some distros . . .

>
> Strange. I connected from linux to my local session by choosing
> shadow and the chossing the :0 from the list of opened sessions. I
> even opened the nx window inside the local screen and got the nice
> recursive view of my screen .So if should not be able to connect to

Yup, me too now . . .

> the local screenm It surprises me that I managed to do it somehow.

 . . . well, I found why I couldn't connect to (Local) with
shadowing.

The patch to stop lots of querying of "sessions_list2 which
was using lots of resource stops DESKTOP_SHARING_IDS
from being populated.

Redhat didn't adopt it, so fedora still works.

I never really tried to use it, so I didn't miss it.

>
> Still I know that vnc server was enabled on that client which could
> be the cause, but I did not choose vnc server from the connection
> options of nxclient, i just choose shadow.
>  
> Other relevant facts:
>
> Even when I succeed to start a non-shadow session, I am not able to
> reconnect if I close the nx window. I reopen the connection to
> linux, choose "unix" and not "shadow" my old session gets displayed
> in the list but It fails to connect to it.

You need to look for error messages. Is the nxclient terminating ??

> Two windows eventually pop up, one says " Could not yet establish
> the connection to the remote proxy. Do you want to terminate the
> current session? " . Later another window pops up saying: " NX
> client was not able to establish an unencrypted channel with the
> server.

Unencrypted sessions should only work if the nxclient and FreeNX
server are on the same subnet . . . .

> 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 unchecking the option 'Disable SSL encryption in all traffic' in
> the configuration dialog" .

Did you try this ???

 
> If i try to connect to the old session with "shadow" after I close
> the window it does not get listed at all. 

Maybe it's "Terminating" instead of "Disconnecting".

> When i tryed to connect to that session through "shadow" before I
> close the window I succeed completely.

From windows ???

>
> To summarize I can connect to new unix sessions and shadow sessions
> while someone is connected.

You have (in node.conf)

        ENABLE_SESSION_SHADOWING_AUTHORIZATION=0
 
so you should be able to automatically connect to a suspended
session because it doesn't wait for an unconnected user to
authorize the connection.

> I cannot connect to my local view from windows but yes from linux. I
> cannot reconnect to old unix sessions through "unix" option or
> "shadow" option.

Do you see a couple of error message in the nxserver.log

        Xlib: connection to ":0.0" refused by server^
and
        Error: Aborting session with 'Failed to connect to display ':0''.

I also see

        NX Agent exited with exit status 1 occuring twice.

and

The nxclient screen just closes,

*** which is what you reported ***



So

your problem is likely to be .Xauthority based.

Make sure both your Console and FreeNX  sessions use
the same one; the default is a good one

         ~/.Xauthority

kdm uses this one, but I notice gdm (with KDE) seems to
use one in /tmp/kde-user/xauth-uid-_0  ( for example )
so they can't both see the MIT ccokie

Log in to X on the console, start a terminal and enter

        xauth

It will tell you which file it's using.

Do the same within a FreeNX session and see if
they are different.


NOTE I notice some issues with screen sizeing
so if you get a blank "shadow" window try enlarging
it by dragging the corner. 







________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
Permalink | Reply | 4 comments |
headers
hp | 30 Jun 2012 00:45
Picon
Favicon

(no subject)

________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ

         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/

________________________________________________________________
       FreeNX-kNX mailing list --- FreeNX-kNX <at> kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
Permalink | Reply | 0 comments |

Gmane