Forum Replies Created
-
Posts
-
In our labs the NoMachine on Centos 7 with Mate desktop works correctly. Please reproduce issue and if you would be able to it – please zip up the folder with nxclient logs and send to forum[at]nomachine[dot]com. Folder should start with M-* in the /home/<username>/.nx directory.
Does your username or hostname contain non-latin symbols? If yes it could be the case: https://www.nomachine.com/TR12M06315. Until NoMachine version 6 comes out sessions of users with non-latin characters might not work correctly.
AVC software encoding should work out of the box. Are you using a higher resolution then 1920×1080 on the server side? If yes please try change value to “false” on “Switch to software decoding on Windows if resolution is bigger than 1920×1080” player configuration key. To do that edit file player.cfg which is in the %USERPROFILE%\.nx\config on client side machine.
If the resolution of the remote monitor is higher than 1920×1080 – H.264 hardware-accelerated decoding won’t be use on Windows clients by default (reference you can find there: https://www.nomachine.com/AR09L00811).
If this is not the case – please gather the logs during connection to the session. To do that zip .nx folder on the client machine and %PROGRAMDATA%\NoMachine\var\log\node on the server machine (submit to forum[at]nomachine[dot]com making sure to reference your topic.
We need to repeat the test with complete set of logs if you are still able to reproduce problem.
Before testing please set in the NoMachine Player to not remove logs after quitting. To do that – open NoMachine Player -> navigate to “Settings” -> click on “Privacy” -> and check “Don’t delete log files on exit”.
Second thing is to paste here also output of the command:
cat /usr/NX/etc/server.cfg | grep UpdateFrequency.Now reproduce the problem and list all the NoMachine processes that appear using
ps aux | grep nx >> nx_processes_list.txt. Repeat the grep at one minute intervals for three minutes, so we can compare the lists.Send created file with the three outputs to forum[at]nomachine[dot]com. Please zip and send also .nx folder.
Are you sure that you are trying to connect using the correct IP? Can you ping the server machine from the Windows machine and see the result? If you are sure that the VPN settings are okay and you can reach the host for example through SSH using PuTTY, please verify if nxserver is started on this Mac and if it is possible to connect there locally via NoMachine.
If problem still appears, please send the logs from client and server sides to forum[at]nomachine[dot]com. Before, make sure to enable debug on Mac and restart nxserver (
sudo /etc/NX/nxserver --restart). Instructions about debug and collecting logs can be found here: https://www.nomachine.com/DT07M00098.You need to try to start the custom session specifying “Run the default X client script on the server” and “Run the command in a virtual desktop”.
Option “Run the command in a floating window” won’t work because it looks that your version of Gnome uses Composite Extension which is not available in the rootless session.
You need to open port 4000. Information of defaults ports used by NoMachine you can find there: https://www.nomachine.com/AR01L00770.
After some time of idleness, the operating system is closing down non-active connections. It depends on the OS.
Can you try keeping an application window (e.g. Firefox) in the background? Please let us know if it helps.
It looks, that some update process is working in background. We weren’t able to reproduce it on the same OS.
Can you zip .nx folder (it’s in the home directory) and execute a stack /usr/NX/bin/nxclient –update process (you can use gdb, for example:
pid=$(ps aux | grep [n]xclient | grep update | awk '{print $2}'); sudo gdb -p $pid -ex "set logging on" -ex "set pagination off" -ex "thread app all bt" -ex "set logging off" -ex quitit will create gdb.txt file with stack) from that OpenSUSE? Please do also screenshot that “update window” with greyed out “Check Now” button. All three files please send to forum[at]nomachine[dot]com.
As a workaround you can download NoMachine Workstation from your customer area (if you have a subscription) and update manually inside console:
sudo rpm -U <package_name>.Are you sure that you are connecting to physical session and authenticated user is other then desktop owner during such connection from external network? Is that local user, or some kind of network user (on ldap environment or etc)? We weren’t able to reproduce the problem. Can you enable debug and restart nxserver (
sudo /usr/NX/bin/nxserver --restart)? If you were able to reproduce issue please collect logs (all from server side and .nx folder from client side) and send them to forum[at]nomachine[dot]com. Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098.Logs will be necessary. Please remove .xsession-error (in home directory user a_garrth, if you are trying on the same user), enable logs and restart nxserver (
sudo /usr/NX/bin/nxserver --restart). If you are able to reproduce problem with not working custom session, collect 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.Which desktop environment do you have installed on the machine (you can check output of command:
ls -l /etc/X11/Xsession)?If you don’t have any DE on the host you need to install such (for example
sudo dpkg -i ubuntu-desktopfor install Unity) .After that remove completely NoMachine (
sudo dpkg --purge nomachine && sudo rm -rf /usr/NX) and install again.Thanks for the report. We will try to fix problem as soon as it’s possible.
About your question with the custom session in your previous post you wrote “When opening a new custom session (in client resolution) or connecting to physical desktop, this is possible”.
Can you point to exactly which option in nxplayer you used during the creation of a new custom session that you have possibility to activate “unlock” button inside?
If you are trying to connect from external network you need to connect to the external IP and correct port. If the router on the server side supports UPnP commands you just need to enable UPnP in server configuration (check “Enabling UPnP/NAT-PMP port mapping” section on: https://www.nomachine.com/AR11L00827).
The correct IP and port you can find on NoMachine “Welcome screen” (example you can find on Fig. 8 on: https://www.nomachine.com/getting-started-with-nomachine).
creating a “new virtual desktop” works but there seems to be the issue that “user elevation” does not work.
It’s not an issue. User which is not in the sudo group shouldn’t be allowed to change system settings. Are you sure that custom session was ran as user which wasn’t belong to sudo group? If yes – can you paste here command which was executed to start that custom session?
Excuse my mistake. I wrote wrong key in previous post. It should be DefaultXSession. Can you paste here output of command:
grep DefaultXSession /usr/NX/etc/node.cfg? It looks that there is changed value to some not working command. Thats why “Run the default X client script on the server” fails.