Forum Replies Created
-
Posts
-
We reproduced it 🙂
Here is the link to the Trouble Report: https://kb.nomachine.com/TR01U10748The workaround is to enter the connection menu Ctrl-Alt-0 and add from there.
1. Forwarding mouse and keyboard from client side:
session settings -> devices -> connect a USB device -> forward local mouse and keyboard
2. Activating remote cursor:
session settings -> input -> keyboard and mouse -> check option “always show remote cursor pointer”
Majkl,
Thanks for the logs. They were useful but why it’s happening is still not clear. We’re still trying to reproduce your issue.
In the meantime, could you send us the contents of C:\Program Files\NoMachine\etc\nxdb? Just zip up and send like you did the logs. Thanks!
On another note, you asked about NoMachine and how data travels between client and server. Please see our articles here for more about this:
Default ports used by NoMachine 4 or later – https://kb.nomachine.com/AR01L00770
NX and the use of UDP protocol https://kb.nomachine.com/AR10T01174Hi, we seem to be going round in circles a little bit with this topic. Here’s what we know so far:
On your Mac host with NX Server installed, you have a VPN client running to connect to a VPN server and route all outgoing traffic via this VPN server. In this scenario it’s normal that it’s impossible to connect from outside to that host. It’s impossible because in that case that host cannot answer to incoming traffic. Data cannot be sent anywhere except to the VPN server.
But, you said earlier that you can add exceptions to this VPN configuration so that data to some IPs can be sent directly to the Mac host, without going through VPN server. If that’s the case, then NX should work as well. But this is the problem and the reason for this topic 🙂
You say that all services can connect to this Mac server except for NX. But this doesn’t include SSH because in another post you mentioned that SSH connections are disabled. You say that SSH works, but you tested this whilst on the same LAN, which is not quite the same thing. Additionally, you can also connect with NoMachine to the Mac server when connecting from LAN.
In a test Tom requested, he asked you to temporarily enable SSH connections from outside. We want you to do this test again. Enable SSH connections on your Mac host, enable the VPN there as well, and from an external computer, open a terminal and run
ssh user@whatever.xxx.net. Can you connect? If not, then NoMachine won’t be able to connect either, our debug stops here, and you should check your VPN configuration carefully. If you can, then we need you to make a further test.Install Enterprise Desktop evaluation on your Mac (it supports SSH connections) reboot etc. Enable debug logs by executing
$ sudo /etc/NX/nxserver –debug –enable all
from a terminal on the Mac server, restart the server in Server settings. Make sure the VPN is enabled. On the Player machine, enable the checkbox “Don’t delete logs on exit”. From outside the LAN, start a NoMachine SSH connection to your NoMachine Mac server. Can you connect? If not, we need logs of that session, from both Player and Server sides (so two sets of logs). To gather the server side logs run
$ sudo /etc/NX/nxserver –debug –collect
Send server and player logs to forum[at]nomachine[dot]com and we will check them.
If you can connect via SSH move on to the next test. With NoMachine, try connecting with NX protocol again. We will need both sets of logs of that failed session. So to sum up please try:
1) pure ssh connection from outside the LAN. If it doesn’t work, we can’t proceed. If it works, go to point 2)
2) NoMachine SSH connection from outside. If it doesn’t work, send us the logs. If it works, go to point 3)
3) NoMachine NX connection from outside. If it fails, send us the logs.
How to disconnect a user from the host machine when the option to blank physical screen is enabled?
Remember that screen-blanking is a privacy feature. It’s there to stop users in the vicinity of the computer seeing sensitive information that the remote user (presumably the session owner) doesn’t want to show. Currently, there isn’t a local key combination to permit a local user to unblank the screen to be able to disconnect the user connected from remote.
Can you tell us what the error is that appears when you try to connect to the Windows NoMachine server? Have I understood right that when you connect from the mobile app you can connect to this Windows server?
Hi,
The update is coming. If the final testing phase goes well, the update will be released in the next few weeks. Thanks for your patience so far.
Britgirl
The update is coming. If the final testing phase goes well, the update will be released in the next few weeks. Thanks for your patience so far.
Britgirl
The update is coming. If the final testing phase goes well, the update will be released in the next few weeks. Thanks for your patience so far.
Britgirl
Hi, NoMachine supports the following Linux distributions: RedHat, Centos, Fedora, OpenSuse/Suse, Debian/Ubuntu, and although ALMA is based on Red Hat, we don’t officially support it. However, that doesn’t mean that it should not work, so we tested the latest version on the fly. We reproduced the same problem. A possible workaround is to use Wayland as your display server instead of X.org. With Wayland we were able to start a physical desktop session with NoMachine.
Hi, can you check the permissions in Accessibility? In version we fixed a problem that meant that the user had to add NoMachine or nxnode (it depends on the version of NoMachine you have installed) to the list of allowed programs in System Preferences. Users will be required, after updating to v8, to add nxnode to the list one last time. Please see the TR for details.
https://kb.nomachine.com/TR10S10377
Does that fix it?
Sounds strange indeed. Could it be possible that the key release gets grabbed by another application and for this reason it’s not reaching the remote desktop? Since it only happens with the Right Ctrl, can you check whether there is a software or configuration using that key?
In any case, it would be useful to know which version of Windows, which Linux distro, what desktop environment on that Linux distro. I also assume you have the latest 8.2 on both client and server machines.
Are you in charge of the server or is someone else? Is it possible that some setting has changed since you last connected? I assume you are using the latest version 8 packages on both Windows and Linux sides. The error looks like that the server has been configured to not allow users who are not NX users.
Can you check how the following keys are set in server.cfg? Is it set to 0 or 1? 0 is the default setting when you install.
#
# Enable or disable NX users DB:
#
# 1: Enabled. Only users listed in NX users DB can login to the NX
#Â Â Â server.
#
# 0: Disabled. All the authenticated users can login.
#
# If the NX user DB is disabled, any user providing a valid password
# from local DB or through SSHD authentication, can connect to the NX
# system. This is likely to be the default when SSHD authentication
# with PAM is enabled.
#
#EnableUserDB 0