Well, I don’t know if it has always been there but there’s two ways to switch between the remote desktop session and your local session when using NX

You can switch between full-screen and your original desktop by clicking on the ‘Magic Pixel’ on the top-right corner of your screen. Just move to the top right corner of the screen and left-click.

If, for any reason, your remote session is not responding, you can switch by pressing the sequence ctrl+alt+shift+esc.

Hope this helps..

Technorati Tags: freenx, nomachine, remote desktop

Powered by ScribeFire.

Last week, we had:

1. Mindquarry 1.1 released
2. TinyERP released a web client and a new version
3. OpenBravo 2.30 released

and while it’s not truly open source, NoMachine released V3 of their NX server and finally, they have introduced

Now, if your an admin, it’s a no-brainer to set it up – you can either do it from NX Manager (make sure you have V3 also) or you can edit /usr/NX/etc/server.cnf

You can checkout all the directives from the Admin guide at this link.

And here’s what the Administrator’s Guide says:
The desktop sharing and session shadowing functionalities are enabled in the default configuration of the server. Desktop sharing allows the sharing of any of the native displays on the node, while session shadowing allows the sharing of any of the NX sessions running on the node. By default, it is up to the owner of the native display or of the master session to accept/deny the user’s request to attach to the display/session.

Now, here’s the $20,000 question – how the hell do we mirror a session or grab a console? I have both the Windows Client AND the Linux client and nowhere is there any option to shadow a session or grab a console.

If I try and login to an existing session, it logs off the original user and logs in the one trying to login.. so wtf?

I have read the docs – oh, I had to google for the page that lists all the docs, so here they are.

Additionally, I personally think the US $750 for the Small Business Server is a little too high as an entry point – or at least expand the free server beyond 2 licenses..

Even a 5 user (+ pay-per-incident support) for $300 would likely make NX a more palatable option for young startups or those wanting to offer a SAAS setup.

At the moment, I am just keen to find out how to test the mirroring or grabbing a console… anyone??

OK, I worked this out:

Then, when you start the session, it will display the sessions that are available to connect to – the default setting is to prompt the user to authenticate you. To change this, edit using:

vi /usr/NX/etc/server.cfg

and change on Line 563 from:

EnableSessionShadowingAuthorization = “1″

to

EnableSessionShadowingAuthorization = “0″

Save it and exit [esc]x! or [esc]wq! in vim

I restarted the nxserver daemon just in case, which will disconnect your NX session if you are connected already.

/etc/init.d/nxserver restart

BUT – the problem I had is that my remote screen resolution is 1440×900 and my local screen resolution is 1280×1024 – so when I try and connect to my local console, NX fits the width in the 1280px by squashing up the 1440 remote image, which presents a barely readable screen – and it makes the height 900px leaving a gap (which is no big deal). It also seemed much slower than a regular nx session.

I will keep playing around but I will probably stick with my current: pkill <program> setup.

Technorati Tags: nomachine, nx, remote desktop, thin client

Powered by ScribeFire.

Anyway, the ‘answer’ to this problem by most people is to tunnely VNC through NX.. Look, go try it if it suits you but it’s, well if I wanted VNC, I would have just used VNC. NX is just another level all together.

This is a real downer, as I use RDP everyday at work and remote control sessions, login via the console etc – a bit of a downer for NX.

Anyway, while it’s not the best solution this is what I do, which suits my situation. Generally, it’s just me connecting from a remote location. Sometimes from work or from a friend’s house.

1. Connect as myself, even though the console is logged in. This creates 2 users logged in under the same name.
2. I run gnome saved sessions which kick off Evolution, Opera and Skype

I then have this in my .profile for my login (don’t run it in your .bashrc or else it will kill evolution each time you open a new shell):

for i in `pgrep evolution`;do kill -9 $i; done;
for i in `pgrep opera`;do kill -9 $i; done;
for i in `pgrep skype`;do kill -9 $i; done;

This kills the three applications, so I can then open them in my NX session. Yes, there’s some bloody repetition there but it’s a one liner I knew, it took 5 minutes and doesn’t make a difference to the time or speed of the login.

Some applications will function running under two simultaneous logins but most won’t. Anyway, pgrep is a nice little Linux utility that’s not available on HP-UX or Solaris –

The ‘almost’ equivalent for that is: ps -ef | grep ‘process_name’

Just don’t go doing any funny shit as root like:

for i in `pgrep ini`;do kill -9 $i; done;
for i in `pgrep at`;do kill -9 $i; done;

;)

Powered by ScribeFire.