Aaron,<br>
<br>
The rpms that I have on my server are:<br>
nx-1.5.0-4.FC1.1<br>
freenx-0.4.4-2.rh.0<br>
<br>
I tried updating nxnode with the backingstore that you mentioned.<br>
But, I am still getting this error:<br>
NX> 704 Session cache: unix-gnome<br>
NX> 707 SSL tunneling: 0<br>
/usr/bin/nxserver: line 1041: 22076
Terminated
( sleep $AGENT_STARTUP_TIMEOUT; exit 1 )<br>
NX> 105 NX> 504 Session startup failed.<br>
NX> 1004 Error: nxagent failed to start with: Unrecognized option: 1<br>
NX> 1001 Bye.<br>
Killed by signal 15.<br>
<br>
I will update my install with the latest freenx 0.5.0 and nx 2.0, and then try these out.<br>
<br>
Thanks<br>
Tom<br><br><div><span class="gmail_quote">On 10/6/06, <b class="gmail_sendername">Aaron Feldman</b> <<a href="mailto:aaronmfeld@yahoo.com">aaronmfeld@yahoo.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Tom check this out:<br><br><a href="http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ/Problem_Solving" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ/Problem_Solving
</a><br><br>From the above source is the following:<br><h3> Solutions for NX Clients versions 2.0.0 and FreeNX 0.4.x and 0.5.0. </h3> <div>
If you have problem connecting with new NX Client ver. 2.0.0, there are
2 patch, which working for me with NX Client ver. 2.0.0-93: </div><div> <strong> 'fake cookie authentication problem': </strong> </div><div>
Some new clients uses 1.4.0 as proto version. You have to make sure
that 'fake cookie authentication' is working on the server. Look at
nxnode and search for that string in 'node_startsession()' function and
edit it. </div><div> For freenx 0.4.x nxnode in function 'node_startsession()' </div><pre> if [ "$ENABLE_1_5_0_BACKEND" = "1" -a "$clientproto" = "1.5.0" ] || [ "$ENABLE_1_5_0_BACKEND" = "1" -a "$clientproto" = "
1.4.0" ]<br> then<br> <br> # enable fake cookie authentication<br> cookie=$proxy_cookie<br> fi<br></pre><div> For freenx 0.5.0 nxnode in function 'node_startsession()' </div><pre> if [ "$clientproto" = "
1.5.0" ] || [ "$clientproto" = "1.4.0" ]<br> then<br> # enable fake cookie authentication<br> cookie=$proxy_cookie<br> fi<br></pre><div>
Pre 1.5 clients will face trouble in this case, though - but works for
me (no users with old clients). As I see in comunnication with client
ver. 2.0.0-93, it use 1.5.0 proto version, so this is for older 2.0.0
clients. </div><div> <strong> 'Backingstore problem': </strong> </div><div>Thorsten
Sandfuchs found some issues concerning backingstore. Problem arouse as
you try to connect to a 0.5.0 installation with no 2.0.0 backend
support and a 2.0.0-client. As Nomachine changed the behaviour of the
backingstore-option. In 1.5.0-clients the client sends "always,
when_requested" et all and freenx just passed this string to the
nxagent-call. The new client now sends "backingstore=1" and the
1.5.0-nxagent issues a warning and an error with "no argument requiered
for -bs" or with "Error: NX Agent exited with exit status 1.". You can
read all his message here: <a href="http://permalink.gmane.org/gmane.network.freenx.general/3839" title="http://permalink.gmane.org/gmane.network.freenx.general/3839" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Backingstore or 2.0.0-client and 1.5.0 backend and freenx-0.5</a> </div><div> Look at nxnode and in function 'node_start_agent()' after this line </div><pre> [ -n "$backingstore" ] && B="-bs $backingstore"
<br></pre>add this lines: <pre> # backingstore = { "when_requested", "always", ... }<br> [ -n "$backingstore" -a "$ENABLE_2_0_0_BACKEND" != "1" -a "$backingstore" != "1" ] && B="-bs $backingstore"
<br> # backingstore = 1 (new nxclient 2.0.0 doesn't send any strings in the option-string for backingstore anymore)<br> [ -n "$backingstore" -a "$ENABLE_2_0_0_BACKEND" != "1" -a "$backingstore" =
<br> "1" ] && B="+bs"<br> # backingstore = 1 and 2.0.0-Backend EXPERIMENTAL<br> [ -n "$backingstore" -a "$ENABLE_2_0_0_BACKEND" = "1" ] && B="-bs $backingstore"
<br></pre><div> This works using nxclient version 2.0.0-98. </div><span class="ad"><br><p>
</p><hr size="1">Yahoo! Messenger with Voice. <a href="http://us.rd.yahoo.com/mail_us/taglines/postman1/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Make PC-to-Phone Calls</a> to the US (and 30+ countries) for 2¢/min or less.
<p></p></span><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 onclick="return top.js.OpenExtLink(window,event,this)" 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 onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.nomachine.com/kb/" target="_blank">
http://www.nomachine.com/kb/</a><br><br>________________________________________________________________<br> FreeNX-kNX mailing list --- <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:FreeNX-kNX@kde.org">
FreeNX-kNX@kde.org</a><br> <a onclick="return top.js.OpenExtLink(window,event,this)" href="https://mail.kde.org/mailman/listinfo/freenx-knx" target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br>________________________________________________________________
<br><br></blockquote></div><br>