Forum Replies Created
-
Posts
-
We were able to reproduce the problem. We will try to fix it as soon as possible. In the meantime, please try changing the protocol to SSH to connect to the remote host.
Is it possible to run applications from a mounted device?
Sure.
Also is it possible to mount individual directories rather than the whole drive?
Yes. You need to change DiskSharingList key in the node.cfg (
/usr/NX/etc/node.cfg) on server host which you want to connect. Uncomment key and change value from “all” to path which you want to mount. For example:
DiskSharingList "$(HOME)/Public"
More information you can find there: https://www.nomachine.com/DT07M00090#12.1.Is this mount functionality in NoMachine for file transfers only?
You can use it like normal mounted drives.
Please try solution from that article: https://www.nomachine.com/AR09L00814.
It looks like some gnome configuration problem. Please enable Xvfb script again, edit it to start gnome-session without involving Xsession script . To do that change last line your script to:
DISPLAY=:0 nohup /usr/bin/gnome-session &(make sure that gnome-session path is correct, you can verify it with commandwhereis gnome-session). Then reboot system and try again to connect.If that doesn’t help. You need to check system logs to find the reason why gnome-session couldn’t start. You could consider also to reinstall GUI environment.
The problem is that – on your machine a physical session is running without GUI environment. Whilst that is still running NoMachine will be connecting there.
If you want to connect via NoMachine to gnome-session on that machine, you need to shutdown that existing session without GUI. Then restart nxserver.
There is two options. First: disable the startup script which runs Xvfb and reboot the system. Second: kill Xvfb process and restart nxserver (
sudo /usr/NX/bin/nxserver --restart).In both cases if you connect to that server you should see: “Cannot detect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?” in the nxplayer window. Then click on “Yes” and that should start the session, which you have set in the DefaultDesktopCommand key (in your case: “/etc/gdm/Xsession gnome-session”).
NoMachine is capturing audio in loopback mode from system mix. So if you want to get sound from VBAudio on the client – you need to set e.g. Microsoft sound mapper as the output device in the PowerSDR.
It’s looks like it is a system issue. For some reason gnome-session cannot start on the display. Please note that your screenshot is what you can see on display with xvfb server. NoMachine is just connecting there.
Did you try solution with disabled xvfb server and allow NoMachine to create the desktop? Is there shows the same messagebox? Can you check if there is no .xsession-error file in home directory? Can you attach it here?
What desktop environment do you use? Is it a clean Ubuntu 16.04 with Unity or did you install GUI manually?
It looks like you have wrong DefaultDesktopCommand key value in the /usr/NX/etc/node.cfg. Can you show output of the command:
sudo grep DefaultDesktopCommand /usr/NX/etc/node.cfg?On Ubuntu installation with Unity line should look like this:
DefaultDesktopCommand "/etc/X11/Xsession 'gnome-session --session=ubuntu'". Please take a look on this forum thread: https://forums.nomachine.com/topic/cannot-create-a-new-display-please-contact-your-system-administrator maybe it would help.Since version 5 there is no need to create a display manually. A new desktop should be created automatically if there is no physical display (https://www.nomachine.com/FR10L02842).
It looks like the main problem is a wrong installation of the graphical environment. Please refer to https://www.nomachine.com/accessing-your-remote-linux-desktop-on-amazon-elastic-compute-cloud-via-NoMachine. There is “Getting the VM desktop environment ready” paragraph with useful commands to install GUI. You can find there full instruction how to use NoMachine on headless machine.
As we can see you are starting xvfb server. NoMachine supports such kind of sessions, but you need to run GUI environment in that xvfb server if you want to see the desktop.
There should be two solutions:
1. Start gnome session on display with xvfb and connect again with NoMachine.
2. Kill xvfb session and restart nxserver. Then you should be able to connect with NoMachine session.We couldn’t reproduce problem on centos 6.9 with Gnome. Are there any crashes in the home directory on that Linux machine?
Can you enable debug, restart nxserver (
sudo /usr/NX/bin/nxserver --restart) and reproduce problem? Please collect server side logs and send them to forum[at]nomachine[dot]com. Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098.Are you sure that username and password is correct? What error shows exactly when you cannot connect?
Which desktop environment do you have installed on that CentOS? You can check it with command
ls /usr/share/xsessions. If there are some files – search for line started with “Exec=”. There should be a command to start a new session. That command you can put in to theDefaultDesktopCommand ""key which is in the /usr/NX/etc/node.cfg.Example:
ls /usr/share/xsessions Output: fluxbox.desktop grep Exec /usr/share/xsessions/fluxbox.desktop Output: Exec=startfluxboxNow edit /usr/NX/etc/node.cfg file. And uncomment DefaultDesktopCommand and add there “startfluxbox” so in that case all line should looks like this:
DefaultDesktopCommand "startfluxbox".Hi.
USB forwarding between Windows 10 and Ubuntu 16.04 should work fine if modules are installed correctly.
Is the security boot disabled on Linux machine? Instructions on how to self-sign the NoMachine USB module or disable secure boot you can find here: https://www.nomachine.com/AR05O00929.
Maybe the problem is on the server side. Can you check
"C:\Program Files (x86)\NoMachine\bin\nxservice64.exe" --status allcommand on the CMD if nxusb status shows “Running”?