Forum Replies Created
-
AuthorPosts
-
kroyContributor
Can you check if disabling “Use hardware acceleration for display processing” on the Windows host would help? You can find it in the server preferences (https://www.nomachine.com/AR02L00782). Please logout from the desktop to be sure it takes effect.
Can you also zip logs (it’s in %ProgramData%\NoMachine\var\log directory) and send them to forum[at]nomachine[dot]com?
kroyContributorAre you sure that you’ve enabled core dumps on this machine? Here are the instructions on how to set environment: https://www.nomachine.com/AR09L00810.
kroyContributorWe have not encountered such a problem on Raspberry. By saying OS GUI do you mean Main menu -> Internet -> NoMachine? Did you try also “Show the service status” button in the NoMachine icon on the system tray?
Logs would be useful here. Please tar two directories ~/.nx and /usr/NX/var/log (to tar that second folder you need a sudo privileges) and send to forum[at]nomachine[dot]com.
Can you also attach the output of the command: cat /usr/share/applications/NoMachine-base.desktop?
To launch NoMachine Player from command line execute: /usr/NX/bin/nxplayer. Could you also send the output of executing this command?
kroyContributorWe’re not able to reproduce this problem at all.
Can you enable debug, restart nxserver and reproduce the issue? The logs can be sent to forum[at]nomachine[dot]com. Instructions about debug and collecting logs are available here: https://www.nomachine.com/DT10O00163.
Thanks!
March 2, 2018 at 19:46 in reply to: Authorization required for changing service settings in server preferences #17732kroyContributorAre you sure that you have entered correct password? If desktop owner has sudo privileges it’s expected that you should enter desktop owner password. If he doesn’t – it should show list with users, from which you need to choose root or other user with sudo rights.
March 2, 2018 at 11:44 in reply to: "Lock the physical screen when somebody connects" session disappears #17726kroyContributorThanks for the logs but they didn’t show anything unusual that might point to a problem with lock screen. Can you send also Xorg logs?
sudo tar zcf xorglogs.tar.gz /var/log/Xorg*
February 22, 2018 at 11:33 in reply to: Avoid user prompt when authenticating through private key #17616kroyContributorThere is a trouble report open for this bug: https://www.nomachine.com/TR12N07463 . Please use the notify me tool to know when a fix is available.
It’s possible to find a temporary workaround for your case. You can generate new key with passphrase (or add passphrase to old key) and save it in nxplayer or just edit session.nxs file (in the default is in
~/Documents/NoMachine
directory) and change line:<option key="Remember password" value="false" />
to:
<option key="Remember password" value="true" />
kroyContributorProblem shows only after machine reboot? Please enable debug, restart nxserver (
sudo /usr/NX/bin/nxserver --restart
), reproduce problem and send logs from server side to forum[at]nomachine[dot]com.Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098.
kroyContributorI would like to install NoMachine in the server side, configure it as I wish, and then disable the access to settings, so that no user can modify it. Would that be feasible?
Only user with administrator rights has access to nxserver configurations.
…I want the connections to always be “view only” and I don’t want any user to have the possibility to change it. Any ideas?
Edit as administrator nxserver configuration file (server.cfg) which is placed by default in the “C:\Program Files (x86)\NoMachine\etc\” directory. Find the key PhysicalDesktopMode. Uncomment it and set value to 0.
So, change the line like this:
#PhysicalDesktopMode 2
to:
PhysicalDesktopMode 0
February 19, 2018 at 15:23 in reply to: Having issues with display when connecting client to Linux Server #17569kroyContributorAre you reproducing the problem every time? Which NoMachine package is installed on the server host? Is it a connection to physical or virtual session?
If possible, can you reproduce problem, and then compress
/usr/NX/var/log/node
(you need be root to do this) on the server and~/.nx
from the client side and send them to forum[at]nomachine[dot]com?kroyContributorDid you perhaps change something in the server.cfg file? Please send file list from NoMachine’s etc directory (sudo find /usr/NX/etc/ > list_of_files.txt), server.cfg, logs (please tar /usr/NX/var/log directory as root) and send it to forum[at]nomachine[dot]com.
A restoration of server.cfg could fix the problem. If you didn’t make a backup before changes, you can use default file: /usr/NX/etc/server-debian.cfg.sample.
kroyContributorIf you are using NoMachine to connect inside Local Area Network, port forwarding isn’t required. If you want to connect over the network (WAN), you can enable UPnP port mapping (https://www.nomachine.com/AR11L00827) or open ports manually, which you already started.
As it appears from your entry – there was port conflict because port 4000 was already opened for laptop 1. For laptop 2 you need to open another unoccupied port like 4001. But you need additionally to change NX port on NoMachine server settings on that machine.
There is two methods to do it. Via User Interface (Server preferences -> Network services -> Edit) or the server configuration file (edit /usr/NX/etc/server.cfg file and uncomment “NXPort 4000” line and change 4000 to 4001). After changes you need to restart nxserver (sudo /usr/NX/bin/nxserver –restart). More info you can find there: https://www.nomachine.com/AR01L00770.
kroyContributorAre you using a non-native firewall? Can you send output of
sudo iptables-save
command?Please also enable debug, restart nxserver (
sudo /usr/NX/bin/nxserver --restart
) and reproduce the problem. Send logs from server and client side to forum[at]nomachine[dot]com. Instructions about collecting logs you can find here: https://www.nomachine.com/DT04M00076.January 30, 2018 at 12:14 in reply to: NoMachine on Raspberry Pi3 & redirecting smart card reader to VM #17364kroyContributorWe checked forwarding HID Omnikey 3121 on Ubuntu 16.04 and it works correctly. However on Ubuntu 14.04 the card wasn’t visible. But it also wasn’t after plugging in the smartcard to the machine. So it looks that system doesn’t support this device.
kroyContributorIt looks like you have configured device to boot in the console mode.You need to change setting to start GUI. You can find instruction there: https://www.nomachine.com/tips-on-how-to-set-up-your-raspberry-pi-for-remote-access-via-nomachine in “Enable Raspberry Pi boot to Desktop” section.
-
AuthorPosts