Forum Replies Created
-
AuthorPosts
-
Bilbotine
ParticipantHi mivang078,
Blanking remote screen during connection is a feature that will be implemented soon. In the meantime, you have the possibility to start a separate X server (Xvfb) and attaching to it, instead of X display connected to monitor.
The article “How to use NoMachine 4 on a headless Linux server” (here: https://www.nomachine.com/AR10K00710) will give you some tips about Xvfb.
In your case, you will have to start it on display other then :0, and adjust DisplayDefault key in node.cfg.
Best regards,
Bilbotine
Bilbotine
ParticipantHi imn,
%PROGRAMDATA%/NoMachine/var/log path is valid for logs obtained on server side, as it is explained in the article “How to gather debug logs for support requests” (https://www.nomachine.com/AR07K00677), section “How to gather server side logs”.
If you want to help us with debugging this issue, you have to follow the procedure explained in the “How to gather client side logs” section of the same article on the computer on which you installed NoMachine Enterprise Client and the procedure of “How to gather client side logs” on the server where you are connecting.
Please send us the logs to issues[at]nomachine[dot]com, and make sure you reference your topic title.
Thank you.
August 14, 2014 at 14:09 in reply to: First connection good, log off hung, no longer able to connect #4493Bilbotine
ParticipantHi wbsimey,
Logs (compressed /usr/NX/var/log and /var/log directories) would be useful. Please follow the instructions here on how to enable and extract them: https://www.nomachine.com/AR07K00677.
You can submit here, or if they are too big, then you will need to send them to issues[at]nomachine[dot]com. Make sure you reference your topic
title.Best regards,
Bilbotine
Bilbotine
ParticipantHi josandres,
For client-only machines you have to use the NoMachine Enterprise Client (https://www.nomachine.com/product&p=NoMachine%20Enterprise%20Client). It’s a client-only installation.
For server-only machines you have to install one from the normal packages and manually remove nxplayer binary.
There is no other option currently.
Best regards,
Bilbotine
Bilbotine
ParticipantHi RHELuser,
Currently Gnome 3 (default desktop in RHEL7) doesn’t work in virtual sessions.
A workaround is provided in the article “Supporting the default Gnome 3 on Fedora 15 or later with NoMachine” (https://www.nomachine.com/AR06L00806)
NoMachine 5.0 will enable Gnome 3 and Unity in virtual sessions.
Bilbotine
ParticipantHello mlsrar,
NoMachine doesn’t currently support virtual desktops (terminals) on Windows or on Mac; only the connection to the physical desktop is possible.
However this development is planned. We’ll keep you updated via the forums.
-
AuthorPosts