<div dir="ltr"><div>Hey, I tried a few more things, but yet I could not make shadow work. I think I will give up this time.</div><div>I now installed the no machine server free edition and I am working with it. I am not able to invest more hours in this setup.</div>
<div>Still I would the freenx people and particularly Chris that was really helpful.</div><div>I really like open source and I would be glad to provide any info you need to debug this if you want me to.<br>Thanks</div><div>
Marcelo<br><br><div class="gmail_quote">On Fri, Jun 29, 2012 at 10:58 PM, <span dir="ltr"><<a href="mailto:chris@ccburton.com" target="_blank">chris@ccburton.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><tt><font><a href="mailto:freenx-knx-bounces@kde.org" target="_blank">freenx-knx-bounces@kde.org</a> wrote on 28/06/2012 13:51:35:<br>
[SNIP]</font></tt>
<br><div class="im"><tt><font>> </font></tt>
<br><tt><font>> > Any other ideas?<br>
> <br>
> Well . . . <br>
> <br>
> You report no error messages and your window client <br>
> connect fine without shadowing. <br>
> <br>
> You say you managed to get shadowing working from <br>
> Linux, which suggested you know how it works . . . <br>
> <br>
> but <br>
> in your original post you are trying to connect <br>
> to a Local session. </font></tt>
<br><tt><font>> <br>
> 0 Local BE77ED951144F03C3A18C25774D7E3A1 -------- Running X0 (Local)
<br>
</font></tt>
<br><tt><font>> NX Shadowing will only connect to another running
<br>
> NX session. </font></tt>
<br>
<br></div><tt><font> . . . due to a bug in nxserver in some distros
. . .</font></tt>
<br><div class="im">
<br><tt><font>> <br>
> Strange. I connected from linux to my local session by choosing <br>
> shadow and the chossing the :0 from the list of opened sessions. I
<br>
> even opened the nx window inside the local screen and got the nice
<br>
> recursive view of my screen .So if should not be able to connect to
<br>
</font></tt>
<br></div><tt><font>Yup, me too now . . .</font></tt>
<br><div class="im">
<br><tt><font>> the local screenm It surprises me that I managed
to do it somehow.</font></tt>
<br>
<br></div><tt><font> . . . well, I found why I couldn't connect to
(Local) with</font></tt>
<br><tt><font>shadowing.</font></tt>
<br>
<br><tt><font>The patch to stop lots of querying of "sessions_list2
which</font></tt>
<br><tt><font>was using lots of resource stops DESKTOP_SHARING_IDS</font></tt>
<br><tt><font>from being populated.</font></tt>
<br>
<br><tt><font>Redhat didn't adopt it, so fedora still works.</font></tt>
<br>
<br><tt><font>I never really tried to use it, so I didn't miss it.</font></tt>
<br><div class="im">
<br><tt><font>> <br>
> Still I know that vnc server was enabled on that client which could
<br>
> be the cause, but I did not choose vnc server from the connection
<br>
> options of nxclient, i just choose shadow.</font></tt>
<br><tt><font>> </font></tt>
<br><tt><font>> Other relevant facts:</font></tt>
<br><tt><font>> <br>
> Even when I succeed to start a non-shadow session, I am
not able to <br>
> reconnect if I close the nx window. I reopen the connection to <br>
> linux, choose "unix" and not "shadow" my old session
gets displayed <br>
> in the list but It fails to connect to it.</font></tt>
<br>
<br></div><tt><font>You need to look for error messages. Is the nxclient
terminating ??</font></tt>
<br><div class="im">
<br><tt><font>> Two windows eventually pop up, one says "
Could not yet establish <br>
> the connection to the remote proxy. Do you want to terminate the <br>
> current session? " . Later another window pops up saying: "
NX <br>
> client was not able to establish an unencrypted channel with the <br>
> server.</font></tt>
<br>
<br></div><tt><font>Unencrypted sessions should only work if the nxclient
and FreeNX</font></tt>
<br><tt><font>server are on the same subnet . . . .</font></tt>
<br><div class="im">
<br><tt><font>> This could be due to the remote server being
behind a <br>
> firewall. If this is the case you should be able to run your session<br>
> by unchecking the option 'Disable SSL encryption in all traffic' in
<br>
> the configuration dialog" .</font></tt>
<br>
<br></div><tt><font>Did you try this ???</font></tt>
<br><div class="im">
<br><tt><font> <br>
> If i try to connect to the old session with "shadow" after
I close <br>
> the window it does not get listed at all. </font></tt>
<br>
<br></div><tt><font>Maybe it's "Terminating" instead of "Disconnecting".
</font></tt>
<br><div class="im">
<br><tt><font>> When i tryed to connect to that session through
"shadow" before I <br>
> close the window I succeed completely.</font></tt>
<br>
<br></div><tt><font>From windows ??? </font></tt>
<br><div class="im">
<br><tt><font>> <br>
> To summarize I can connect to new unix sessions and shadow sessions
<br>
> while someone is connected.</font></tt>
<br>
<br></div><tt><font>You have (in node.conf)</font></tt>
<br>
<br><tt><font> ENABLE_SESSION_SHADOWING_AUTHORIZATION=0</font></tt>
<br><tt><font> </font></tt>
<br><tt><font>so you should be able to automatically connect to
a suspended</font></tt>
<br><tt><font>session because it doesn't wait for an unconnected
user to</font></tt>
<br><tt><font>authorize the connection.</font></tt>
<br><div class="im">
<br><tt><font>> I cannot connect to my local view from windows
but yes from linux. I<br>
> cannot reconnect to old unix sessions through "unix" option
or <br>
> "shadow" option.</font></tt>
<br>
<br></div><tt><font>Do you see a couple of error message in the nxserver.log</font></tt>
<br>
<br><tt><font> Xlib: connection
to ":0.0" refused by server^</font></tt>
<br><tt><font>and</font></tt>
<br><tt><font> Error: Aborting
session with 'Failed to connect to display ':0''.</font></tt>
<br>
<br><tt><font>I also see </font></tt>
<br>
<br><tt><font> NX Agent exited
with exit status 1 occuring twice.</font></tt>
<br>
<br><tt><font>and</font></tt>
<br>
<br><tt><font>The nxclient screen just closes,</font></tt>
<br>
<br><tt><font>*** which is what you reported ***</font></tt>
<br>
<br>
<br>
<br><tt><font>So</font></tt>
<br>
<br><tt><font>your problem is likely to be .Xauthority based.</font></tt>
<br>
<br><tt><font>Make sure both your Console and FreeNX sessions
use</font></tt>
<br><tt><font>the same one; the default is a good one</font></tt>
<br>
<br><tt><font> ~/.Xauthority</font></tt>
<br>
<br><tt><font>kdm uses this one, but I notice gdm (with KDE) seems
to</font></tt>
<br><tt><font>use one in /tmp/kde-user/xauth-uid-_0 ( for
example )</font></tt>
<br><tt><font>so they can't both see the MIT ccokie</font></tt>
<br>
<br><tt><font>Log in to X on the console, start a terminal and enter
</font></tt>
<br>
<br><tt><font> xauth</font></tt>
<br>
<br><tt><font>It will tell you which file it's using.</font></tt>
<br>
<br><tt><font>Do the same within a FreeNX session and see if</font></tt>
<br><tt><font>they are different.</font></tt>
<br>
<br>
<br><tt><font>NOTE I notice some issues with screen sizeing</font></tt>
<br><tt><font>so if you get a blank "shadow" window try
enlarging</font></tt>
<br><tt><font>it by dragging the corner.</font></tt>
<br>
<br>
<br>
<br>
<br>
<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>
<br>
<a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ" target="_blank">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a><br>
<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>