Forum Replies Created
-
Posts
-
By default NoMachine is connecting to physical session running on display :0. If your session is working on different display please adjust ‘DisplayDefault’ key in node.cfg to correct value.
How to start secondary X server is explained in multiple articles, please take a look for example at these:
You can run X server on DISPLAY :1 and start on it whatever you like (Gnome, KDE).
There is no need to use Xvfb in that case.
Remember to adjust ‘DisplayDefault’ key in node.cfg to ‘1’We just verified procedure from AR10K00710 on OpenSUSE 13.1 and it works correctly.
Your logs suggests that there is something wrong with authorization cookie.
Please execute following commands to assure that cookie is correct and equal in both cases:
xauth -f ~/Xvfb-0.auth list :0
xauth list :0We are still investigating issue with ‘CGSServiceForDisplayNumber: Invalid Display 0x41dc9d03’ flood.
4 nxserver.bin and 2 nxnode.bin instances is OK when someone is connected to that machine.
To check you software version please open NoMachine Player application, go to ‘Preferences’ then to ‘Updates’.
As far we know it’s not possible to upgrade Fedora 16 to Fedora 20 automatically.
You should backup your NoMachine configuration and restore on newly installed system after updating.
What exactly have to be moved depends on configuration you’re using.
All *.cfg and *.lic files and etc/keys directory are essential and have
to be moved.Then all *.db files you use, for example users.db if you use User DB, passwords.db if you use Passwords DB and so on.
Steps are written here:
Logs can be useful. You can gather them as explained in https://www.nomachine.com/AR07K00677 and send to forum[at]nomachine[dot]com.
Thank you.
Presently it’s not possible to prepare set of predefined sessions on server side.
However you can prepare custom sessions config files and distribute them among your users or
make them available on web.NX port should be higher then 1024. Ports below 1024 are reserved for applications run as root. NX daemon instead works as unprivileged nx user. If you really need to access NX on port 80 you can always start as root a port forwarding application to forward port 80 to 4000.
Unfortunately currently there is no way to migrate running sessions between nodes.
This can be archived with help of virtualization hypervisor by migrating virtual systems between physical machines.With NoMachine for Mac it’s not possible to have two users connect to a remote host: one on the physical console and another via NoMachine.
This is because NoMachine doesn’t currently support virtual sessions on Mac. It’s not related to how you’ve set up your sandbox. There are things that are trivial to do on Linux that are not as easy on OSX, especially when you are dealing with an OS where what you can do and what you cannot do is written in the EULA. But it is definitely something we would like to have as a feature in the future.
Can you please send server side logs to us?
%PROGRAMDATA%\NoMachine\var\log on Windows Vista, 7 and 8.
Please compress this folder and send to forum[at]nomachine[dot]com.