Forum Replies Created
-
Posts
-
Balloon notification should close with over a dozen seconds by itself. We couldn’t reproduce such issue. Is that Ubuntu 16.04 with NoMachine 5.3.12? Is that physical or virtual desktop. If you are able to reproduce problem with not closing notification – can you tar nxclient logs (~/.nx folder) from server side and send them to forum[at]nomachine[dot]com.
If you don’t want to displaying balloon messages on your machine you can uncomment and set “DisplayMonitorNotifications” key to 0 in the node configuration file (/usr/NX/etc/node.cfg).
You have double NAT networking, so NoMachine has to go through two routers. The first one which is facing the internet, and the second, which is on your local network. You need to set up separate port forwarding rules on each device.
Why ip 192.168.200.101?
It looks that is your second router IP and port 24004 is set for UPnP connection. To connect to the machine from external network you need to configure first router. In your case open 24004 port for 192.168.200.101. Now connection to external IP with port 24004 should work.
I mean “Create a new virtual desktop” – point b) on your list.
About H264 problem. Please check if libraries are present on client and server side:
ls -l /usr/NX/lib/ |grep -E "libav.so|libx264.so". Please send also logs from client (tar last R-* folder from ~/.nx directory) and server side (tar all C-* folders from /usr/NX/var/log/node directory) to forum[at]nomachine[dot]com.There was a problem with the screen resolution if the server was restarted while not connected to the monitor. Screen resolution was way off. This problem was solved by using xrandr and adding the modelines to a config file in /etc/X11/xorg.conf.d.
It depends on the OS. NoMachine does not modify the list of available resolutions on the system.
About point v) – is the same situation taking place when you try to “Create a new virtual session”?
…however I’m still stuck with VP8 instead of H.264 even though ffmpeg is installed on the client and NoMachine Workstation should include H.264 encoder.
Do you have the evaluation of Workstation installed or did you purchase a subscription? AVC Pack is not available as evaluation (https://www.nomachine.com/AR10K00706), but installing the libraries and codecs to enable H.264 by hand is possible:
http://www.nomachine.com/AR10K00696 for client side
https://www.nomachine.com/AR09M00863 for server sideCommand:
DefaultDesktopCommand "/etc/X11/Xsession 'gnome-session --session=gnome'"should work in that case.In logs we can see:
nxserver.log:2017-10-10 00:12:53 400.683 24723 NXNODE ERROR! Cannot write to .Xauthority file in /home/diapadion on the local host. Please verify permission attributes for that file.
Can you check permissions of /home/diapadion/.Xauthority file? It should be set to 0600 and user diapadion should be the owner. If not – you need to change permission or eventually – remove the file.
If you are connecting to web-session you need enable WebRTC to add support to h264 codec (https://www.nomachine.com/FR10N03219). If you are using connection via nxplayer – do you have the evaluation of Cloud Server installed or did you purchase a subscription? AVC Pack is not available as evaluation (https://www.nomachine.com/AR10K00706), but installing the libraries and codecs to enable H.264 by hand is possible:
http://www.nomachine.com/AR10K00696 for client side
https://www.nomachine.com/AR09M00863 for server sideIt’s related with Wayland.
Try tip added by Britgirl https://www.nomachine.com/forums/topic/not-able-to-launch-system-tools-fedora-26#post-15336. Disable Wayland in the /etc/gdm3/custom.conf:
WaylandEnable=false
It looks that it could be some system’s session initiation script problem. Can you paste here output of commands:
ls -lt $(whereis gnome-session) ls -lt /etc/X11/Xsession ls -lt /etc/gdm/Xsession ls -lt /etc/X11/xinit/XsessionDid you try to set:
DefaultDesktopCommand "/etc/X11/xinit/Xsession 'gnome-session --session=gnome'"?As workaround you could try to set key with one of four following commands (of course if they exists in the system):
gnome-session /usr/bin/gnome-session /bin/gnome-session /usr/local/bin/gnome-session.For example:
DefaultDesktopCommand "gnome-session".We couldn’t reproduce this problem in our labs – before you check workaround which is written below – can you send logs that we could investigate problem? To do that just pack as root /usr/NX/var/log directory and send it forum[at]nomachine[dot]com. Is it a clean NoMachine installation or there were some configurations before you have installed our program (previous installation?) Is it Ubuntu 14.04 installed without any desktop environment and then you have installed gnome and fluxbox? Can you indicate which command you used to install it?
First search for command starting session:
which gnome-session. Output should be similar to:/usr/bin/gnome-session /bin/gnome-session /usr/local/bin/gnome-sessionNow check available gnome sessions. Output should be similar to:
/usr/share/gnome-session/sessions/gnome.session /usr/share/gnome-session/sessions/gnome-classic.session /usr/share/gnome-session/sessions/gnome-fallback.sessionCheck location of your Xsession scripts. If script are in two places use path to Xsession from top of list:
/etc/X11/Xsession /etc/gdm/Xsession /etc/X11/xinit/XsessionNow you can edit DefaultDesktopCommand key in the node configuration file (/usr/NX/etc/node.cfg) and change value to available session. For example, for gnome-classic:
DefaultDesktopCommand "/etc/X11/Xsession 'gnome-session --session=gnome-classic'"
for gnome3d:
DefaultDesktopCommand "/etc/X11/Xsession 'gnome-session --session=gnome'"Are you sure the formatting you inputted was correct? See my previous reply from October 5th, I edited it to show the exact code properly formatted.
Please write what desktop environment have you installed on this machine?
You need to create new nxs file with connection to the server. To do that open nxplayer and on connection list choose “New” and complete connection configurations (Fig. 2-4 on: https://www.nomachine.com/getting-started-with-nomachine). Save it as you want (default folder with nxs files is ~/Documents/NoMachine).
Now edit ~/.config/autostart/nxplayer.desktop and add full path inside the line:
Exec=/usr/NX/bin/nxplayer --session "path to the NXS file" --exitWhat is your desktop environment? Possible that you have unrecognized by system command in the node configuration file in the DefaultDesktopCommand key. Did you change it before update? Please paste here output of the command
sudo grep DefaultDesktopCommand /usr/NX/etc/node.cfg.If this is the case you need to edit /usr/NX/etc/node.cfg file find and change DefaultDesktopCommand to correct one. On Ubuntu 14.04 with Unity it should be:
DefaultDesktopCommand "/etc/X11/Xsession 'gnome-session --session=ubuntu'"Take a look on tip given by Tor: https://www.nomachine.com/forums/topic/connection-session-at-startup#post-13952. If ~/.config/autostart diretory doesn’t exist, create it.
Yes, we made some changes in the installation scripts. If you have centOS/RHEL 6 nxserver.conf is placed in the /etc/init/. You can check status using for example command:
initctl status nxserver.Running an entire desktop in rootless mode is probably better suited for lightweight desktops such as XFCE or LXDE. For example to start XFCE desktop you can use
startxfce4command. So you should Create a new custom session, choose “Run the following command” and paste there startxfce4 and select “Run the command in floating window”.