headers
Marco Passerini | 1 Apr 2011 08:59
Picon
Picon
Favicon

Problem with Nx, Fluxbox and suspended sessions

Hi,

I have set up an NX box with the following setup:

NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: not detected)
Fluxbox 1.0.0 : (c) 2001-2007 Fluxbox Team
Red Hat Enterprise Linux Server release 5.6 (Tikanga)

I noticed that when I start a new session everything works fine , I can 
create new windows etc.
However, whenever I recover a suspended session, I can continue to work 
on the existing windows but I am not able to create any new ones. 
Whenever I try, for example, to create a new terminal, nothing happens 
(just the focus moves to one of the existing windows).

Has anyone experienced this problem?

Marco
________________________________________________________________
     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
(Continue reading)

Permalink | Reply | 17 comments |
headers
Tim Rice | 1 Apr 2011 23:45
Picon
Favicon

Using NX with VNC

I have a particular architecture I’m trying to work within. I’m looking for help in working with this
VNC Server and using it to get an NX Desktop and SFTP interface.

-	These 3 nodes are on separate LANs somewhere in separate locations around the world.
-	They are connected on separate VPNs with the VNC-Server being the common inter-connect.
-	Node-L  requests application from VNC-Server for Telnet, FTP, Desktop on Node-R

+------------+                                 +-----------------+                              +------------+
+  Node-L  +     <= VPN-A =>    +  VNC-Server  +    <= VPN-B =>   +  Node-R  +
+------------+                                 +-----------------+                              +------------+

The Telnet and FTP apps perform well enough but the X Windows Desktop you get on Node-L for Node-R is just too
slow to be usable.

I can’t really make a change to the VNC-Server as it’s a bit of a Corporate Deity used by many and a change
there would be in that act of GOD category.

I’m looking primarily for a way to increase the Desktop GUI performance. I was able use FreeNX tools on the
2 end nodes with a direct connection between them to see that the performance is good. 

Any ideas on how to get it to work through this VNC-Server?

Thanks,
-Tim

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

Permalink | Reply | 1 comment |
headers
Stefan Baur | 2 Apr 2011 12:09
Picon
Favicon

Re: Using NX with VNC (Tim Rice)

Hi Tim,

you wrote:
> I can't really make a change to the VNC-Server as it's a bit of a Corporate Deity used by many and a change
there would be in that act of GOD category.
If you can install FreeNX on another machine in the same subnet (and 
preferably the same physical location), you should be all set:
1. connect via NXClient to this machine
2. from this machine, run VNCviewer (or use the built-in VNC connect 
option of the NXclient, if that works for you - I've seen it work, and 
I've seen it fail) to connect to the VNC-Server.

That way, the FreeNX server will act as a proxy for your VNC session, 
and you should see a speed/performance improvement.
(VNC works reasonably well when used in the same local area network, 
it's the small-bandwidth connections where NX *really* makes a difference)

Kind Regards,
Stefan
________________________________________________________________
     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
(Continue reading)

Permalink | Reply | 0 comments |
headers
chris | 3 Apr 2011 13:36
Favicon

Re: Using NX with VNC


Tim Rice <harleyvrodred <at> yahoo.com> wrote on 01/04/2011 22:45:47:
[SNIP]
>Node-L <= VPN-A => VNC-Server <= VPN-B => Node-R
[SNIP]
>
> The Telnet and FTP apps perform well enough but the X Windows
> Desktop you get on Node-L for Node-R is just too slow to be usable.
>
You don't really tell us enough about your VPNs . . .

If you can't connect directly from "Node-L" to "Node-R" I guess not,
but are you sure ??
but
if you can:-
        ssh "VNC-Server" from "Node-L" (check in case
they've changed the port from 22 to something else)
then
you can try telling ssh to conect a tunnel to "Node-R"
i.e
on "Node-L" try (all on one line)
        ssh -f -N -p ssh-port-on-VNC-Server-default-is-22
        -L 1010:Node-R:ssh-port-on-Node-R-default-is-22
        ssh-user-on-VNC-server <at> VNC-server
(NOTE WELL The "Node-R" needs to be resolveable from
"VNC-Server" not "Node-L" )
and
see if it sets up forwarding from port 1010 on "Node-L"
to port 22 (or whatever) on "Node-R"
(test with ssh -p1010 ssh-user-on-Node-R <at> localhost
assuming sshd is actually running on "Node-R")

If that tunnels through (over the original VPNs) then you can
install FreeNX on "Node-R" andconnect from "Node-L" by
running nxclient and pointing the session at localhost:1010
else
If VPN-A only gives you VNC to "VNC-Server" (probable senario)
then
see if you can install nxclient on "VNC-Server" (guess not)
or
on another machine with with access to "Node-R" via VPN-2
which will allow you to NX half the link anyway.

You may find you need NX end-to-end, even if the links individualy
are quick, because it may well prove to be too slow over both with
a protocol change in the middle.

[SNIP]
> Thanks,
> -Tim
________________________________________________________________
     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 |
headers
Yang Zhang | 4 Apr 2011 05:34
Picon
Gravatar

Ubuntu PPA package broken?

Hi, the Ubuntu 10.04 package of freenx from the PPA seems to have a
syntax error on line 13 of the Upstart conf. Is something wrong with
my installation? Thanks in advance.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 10.04.2 LTS
Release:        10.04
Codename:       lucid

$ apt-cache policy freenx
freenx:
  Installed: 0.7.3.git100327.e224628-0~ppa7~lucid
  Candidate: 0.7.3.git100327.e224628-0~ppa7~lucid
  Version table:
 *** 0.7.3.git100327.e224628-0~ppa7~lucid 0
        500 http://ppa.launchpad.net/freenx-team/ppa/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

$ sudo service freenx-server status
start: Unknown job: freenx-server

$ sudo initctl reload-configuration

$ tail -1 /var/log/syslog
Apr  3 20:26:45 zs init: /etc/init/freenx-server.conf:13: Unknown stanza

$ cat /etc/init/freenx-server.conf
# apport - automatic crash report generation
#
# While this job is active, core dumps will captured by apport and
# used to generate automatic crash reports.

description     "automatic crash report generation"

start on runlevel [2345]
stop on runlevel [!2345]

env enabled=1

PATH_BIN=/usr/lib/nx

pre-start script
    if [ ! -e "/var/run/freenx-server" ]; then
        [ ! -d "/tmp/.X11-unix" ] && mkdir -m1755 /tmp/.X11-unix/
        $PATH_BIN/nxserver --cleanup
        $PATH_BIN/nxserver --start
        touch "/var/run/freenx-server";
    else
        echo "Not starting freenx-server, it's already started."
    fi
end script

post-stop script
    $PATH_BIN/nxserver --stop
    $PATH_BIN/nxserver --cleanup
    rm -f /var/run/freenx-server
end script

--

-- 
Yang Zhang
http://yz.mit.edu/
________________________________________________________________
     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 | 2 comments |
headers
Franklin Reyes | 3 Apr 2011 05:48
Picon

Ubuntu 10.10 FreeNX

When I login using FreeNX, I get a box with two sessions. Either session ends up giving me an error:

 

NX> 203 NXSSH running with pid: 5200

NX> 285 Enabling check on switch command

NX> 285 Enabling skip of SSH config files

NX> 285 Setting the preferred NX options

NX> 200 Connected to address: 192.168.2.105 on port: 22

NX> 202 Authenticating user: nx

NX> 208 Using auth method: publickey

Linux frank-desktop 2.6.35-28-generic #49-Ubuntu SMP Tue Mar 1 14:40:58 UTC 2011 i686 GNU/Linux

Ubuntu 10.10

 

Welcome to Ubuntu!

* Documentation:  https://help.ubuntu.com/

 

Your CPU appears to be lacking expected security protections.

Please check your BIOS settings, or for more information, run:

  /usr/bin/check-bios-nx --verbose

 

HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.4.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: frank

NX> 102 Password:

NX> 103 Welcome to: frank-desktop user: frank

NX> 105 listsession --user="frank" --status="suspended,running" --geometry="1024x768x32+render" --type="vnc"

NX> 127 Sessions list of user 'frank' for reconnect:

 

Display Type             Session ID                       Options  Depth Screen         Status      Session Name

------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------

0       Local            78C5EC90F809BA244E2459D98B4DC478 --------       1024x768       Running     X0 (Local)

0       Local            9F087FF5EF6881F6BA92053E3B61F4AD --------       1024x768       Running     X0 (Local)

 

 

NX> 148 Server capacity: not reached for user: frank

NX> 105 listsession --user="frank" --status="suspended,running" --geometry="1024x768x32+render" --type="vnc"

NX> 127 Sessions list of user 'frank' for reconnect:

 

Display Type             Session ID                       Options  Depth Screen         Status      Session Name

------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------

0       Local            D5187F4A93C6ADB0184D85B8ABF80958 --------       1024x768       Running     X0 (Local)

0       Local            8439A32D19EB93F8185A58EF143E1343 --------       1024x768       Running     X0 (Local)

 

 

NX> 148 Server capacity: not reached for user: frank

NX> 105 restoresession  --link="lan" --backingstore="1" --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --composite="1" --media="0" --session="X0%20(Local)" --type="vnc" --agent_server="192.168.2.105%3A0" agent_password="******" --geometry="1024x768" --client="winnt" --kbload="pc102/en_US" --keyboard="pc102/en_US" --aux="1" --id="9F087FF5EF6881F6BA92053E3B61F4AD" --resize="1"

 

NX> 596 Could not find shadowed session 9F087FF5EF6881F6BA92053E3B61F4AD. Session failed.

NX> 596 Sharing:

NX> 105 NX> 280 Exiting on signal: 15

 

Terminating does nothing. Creating new opens a black screen that closes soon after.

 

I don’t think my x configuration has anything to do with it but I have it setup with an EDID for headless solution to the nVidia problem:

 

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid

    Identifier     "Monitor0"

    VendorName     "Unknown"

    ModelName      "Sampo/STAC KDS VS-7p"

    HorizSync       30.0 - 72.0

    VertRefresh     50.0 - 160.0

    Option         "DPMS"

EndSection

 

Section "Device"

    Identifier     "Device0"

    Driver         "nvidia"

    VendorName     "NVIDIA Corporation"

    BoardName      "GeForce 7900 GS"

    Option         "CustomEDID" "CRT-0:/etc/X11/edid.bin

EndSection

 

Any help is greatly appreciated.

________________________________________________________________
     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 | 1 comment |
headers
chris | 4 Apr 2011 11:31
Favicon

Re: Ubuntu 10.10 FreeNX


"Franklin Reyes" <watisup <at> gmail.com> wrote on 03/04/2011 04:48:34:

[SNIP]
> NX> 103 Welcome to: frank-desktop user: frank
> NX> 105 listsession --user="frank" --status="suspended,running" --
> geometry="1024x768x32+render" --type="vnc"

connect to "suspended" and "VNC" . . .


> NX> 127 Sessions list of user 'frank' for reconnect:
>  
> Display Type             Session ID                       Options  
> Depth Screen         Status      Session Name
> ------- ---------------- -------------------------------- --------
> ----- -------------- ----------- ------------------------------
> 0       Local            78C5EC90F809BA244E2459D98B4DC478 --------  
> 1024x768       Running     X0 (Local)
> 0       Local            9F087FF5EF6881F6BA92053E3B61F4AD --------  
> 1024x768       Running     X0 (Local)

Running,.Local,X0  . . . no vnc so you can't connect to this

(it always shows these)

[SNIP]
> NX> 148 Server capacity: not reached for user: frank
> NX> 105 restoresession  --link="lan" --backingstore="1" --
> encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1"
> --strict="0" --composite="1" --media="0" --session="X0%20(Local)" --
> type="vnc" --agent_server="192.168.2.105%3A0"
> agent_password="******" --geometry="1024x768" --client="winnt" --
> kbload="pc102/en_US" --keyboard="pc102/en_US" --aux="1" --
> id="9F087FF5EF6881F6BA92053E3B61F4AD" --resize="1"
>  
> NX> 596 Could not find shadowed session

No shadowed sessions to conect to . . .


> 9F087FF5EF6881F6BA92053E3B61F4AD. Session failed.
> NX> 596 Sharing:
> NX> 105 NX> 280 Exiting on signal: 15

So I'll give up !!

>  
> Terminating does nothing. Creating new opens a black screen that
> closes soon after.
>  
> I don’t think my x configuration has anything to do with it but I
> have it setup with an EDID for headless solution to the nVidia problem:

So you can . .

Start a fresh session (by changing what you ask for in nxclient)
then
run vncserver on it and it will then appear in the list when you
try to VNC a running NX session.


If you are hoping to VNC connect to the console then you need
x11vnc running on the console . . .

[SNIP]
> Any help is greatly appreciated.
________________________________________________________________
     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 |
headers
chris | 4 Apr 2011 11:50
Favicon

Re: Ubuntu PPA package broken?


Yang Zhang <yanghatespam <at> gmail.com> wrote on 04/04/2011 04:34:08:

> Hi, the Ubuntu 10.04 package of freenx from the PPA seems to have a
> syntax error on line 13 of the Upstart conf. Is something wrong with
> my installation? Thanks in advance.
>
> $ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description:    Ubuntu 10.04.2 LTS
> Release:        10.04
> Codename:       lucid
>
> $ apt-cache policy freenx
> freenx:
>   Installed: 0.7.3.git100327.e224628-0~ppa7~lucid
>   Candidate: 0.7.3.git100327.e224628-0~ppa7~lucid
>   Version table:
>  *** 0.7.3.git100327.e224628-0~ppa7~lucid 0
>         500 http://ppa.launchpad.net/freenx-team/ppa/ubuntu/
> lucid/main Packages
>         100 /var/lib/dpkg/status
>
> $ sudo service freenx-server status
> start: Unknown job: freenx-server

That doesn't look right to me . . .
. . .  but then I don't know much about ubuntu

Try
sudo service freenx-server start

and see if it still gives "unknown job"

or there is

start freenx-server

>
> $ sudo initctl reload-configuration
>
> $ tail -1 /var/log/syslog
> Apr  3 20:26:45 zs init: /etc/init/freenx-server.conf:13: Unknown stanza

Yup

>
> $ cat /etc/init/freenx-server.conf
> # apport - automatic crash report generation
> #
> # While this job is active, core dumps will captured by apport and
> # used to generate automatic crash reports.
>
> description     "automatic crash report generation"
>
> start on runlevel [2345]
> stop on runlevel [!2345]
>
> env enabled=1
>
> PATH_BIN=/usr/lib/nx

PATH_BIN is not an upstart stanza. Try putting env (which
is an upstart stanza) in front of it, (see line 11) and see
if any errors go away  . . .

>
> pre-start script
>     if [ ! -e "/var/run/freenx-server" ]; then
>         [ ! -d "/tmp/.X11-unix" ] && mkdir -m1755 /tmp/.X11-unix/
>         $PATH_BIN/nxserver --cleanup
>         $PATH_BIN/nxserver --start
>         touch "/var/run/freenx-server";
>     else
>         echo "Not starting freenx-server, it's already started."
>     fi
> end script
>
> post-stop script
>     $PATH_BIN/nxserver --stop
>     $PATH_BIN/nxserver --cleanup
>     rm -f /var/run/freenx-server
> end script
>
> --
> Yang Zhang
> http://yz.mit.edu/ 
________________________________________________________________
     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 | 1 comment |
headers
Yang Zhang | 4 Apr 2011 18:11
Picon
Gravatar

Re: Ubuntu PPA package broken?

On Mon, Apr 4, 2011 at 2:50 AM,  <chris <at> ccburton.com> wrote:
>
> Yang Zhang <yanghatespam <at> gmail.com> wrote on 04/04/2011 04:34:08:
>
>> Hi, the Ubuntu 10.04 package of freenx from the PPA seems to have a
>> syntax error on line 13 of the Upstart conf. Is something wrong with
>> my installation? Thanks in advance.
>>
>> $ lsb_release -a
>> No LSB modules are available.
>> Distributor ID: Ubuntu
>> Description:    Ubuntu 10.04.2 LTS
>> Release:        10.04
>> Codename:       lucid
>>
>> $ apt-cache policy freenx
>> freenx:
>>   Installed: 0.7.3.git100327.e224628-0~ppa7~lucid
>>   Candidate: 0.7.3.git100327.e224628-0~ppa7~lucid
>>   Version table:
>>  *** 0.7.3.git100327.e224628-0~ppa7~lucid 0
>>         500
> http://ppa.launchpad.net/freenx-team/ppa/ubuntu/
>> lucid/main Packages
>>         100 /var/lib/dpkg/status
>>
>> $ sudo service freenx-server status
>> start: Unknown job: freenx-server
>
> That doesn't look right to me . . .
> . . .  but then I don't know much about ubuntu
>
> Try
> sudo service freenx-server start
>
> and see if it still gives "unknown job"
>
> or there is
>
> start freenx-server
>
>>
>> $ sudo initctl reload-configuration
>>
>> $ tail -1 /var/log/syslog
>> Apr  3 20:26:45 zs init: /etc/init/freenx-server.conf:13: Unknown stanza
>
> Yup
>
>>
>> $ cat /etc/init/freenx-server.conf
>> # apport - automatic crash report generation
>> #
>> # While this job is active, core dumps will captured by apport and
>> # used to generate automatic crash reports.
>>
>> description     "automatic crash report generation"
>>
>> start on runlevel [2345]
>> stop on runlevel [!2345]
>>
>> env enabled=1
>>
>> PATH_BIN=/usr/lib/nx
>
> PATH_BIN is not an upstart stanza. Try putting env (which
> is an upstart stanza) in front of it, (see line 11) and see
> if any errors go away  . . .

Yep, that's what I already did to get past this error on my box, but I
figured I'd report it here, and also even after doing that, other
things seem broken. Haven't looked into those, just figured it was a
sign of the general state of the package:

$ sudo service freenx-server start
start: Job failed to start

$ tail /var/log/syslog
...
Apr  4 09:09:32 zs init: freenx-server pre-start process (4704)
terminated with status 1
Apr  4 09:09:33 zs init: freenx-server post-stop process (4775)
terminated with status 1

--

-- 
Yang Zhang
http://yz.mit.edu/
________________________________________________________________
     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 |
headers
Stargazer | 10 Apr 2011 23:14
Picon
Favicon

Fedora 14 - Windows nomachine client tmes out after "negotiating link parameters"

Hi list, this is my first post but I've been using the nomachine client 
with Fedora for years.
I have a problem with one Fed 14 server in that after going through all 
the usual authentication stages it always times out with that message. I 
know its not my client because I can connec from home into the office to 
another Fed 14 server, running FreeNX, fine. The setups of both are 
almost identical and I can SSH into both fine from Putty. The server 
with the problem did work until 2 things were changed, but changed in a 
way I'd hoped would have no effect and in fact haven't impacted anything 
else (and so might not be relevant). First, the hosts file was changed - 
it now looks like this, with example.com being replaced with the real 
domain:

127.0.0.1 localhost sabbath.example.com
::1 sabbath localhost6.localdomain6 localhost6

192.168.62.25  zeppelin zeppelin.example.com

Sabbath is the problem machine, Zeppelin is fine. Zeppelin's hosts file 
looks the same with the names and IP's updated. It was changed from the 
default setup because its cron email from addresses were using the 
horrible localhost.localdomain syntax fedora still insists on putting in 
as the default.

The second change, and I think this is different to Zeppelin, is there 
were 3 entries in the network cards list, this is because it was 
initially setup on a hdd in a caddy in another machine, then used in 
Sabbath, hence when the network started it found the local eth device 
and created a new entry. I used networkmanager to point to the eth 
device - in the first config it was using the device but not 
networkmanager. Clearly, that part all works as I can SSH in and in fact 
as I said FreeNX authenticates fine.

These might seem irrelevant but they really are the only things changed 
from a working system. Can anyone spot what I should be looking for to 
fix this please?

Thanks
________________________________________________________________
     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 | 12 comments |

Gmane