Forum Replies Created
-
Posts
-
Can you try to run the ‘xev’ utility in the remote desktop, send the Ctrl key to it through the NoMachine remote session and show us what is reported in the output? I would start with sending any other key first, just to check if everything is set up correctly and the keys are reported in the output. Then you can type just the Ctrl key, to see if it is sent through. Finally, you can try with the problematic Ctrl-<key> combinations and show us the xev output.
We have been unsuccessful at reproducing the issue. Knowing the desktop environment you are connecting to on the Fedora host would be useful, and whether this happens in all applications or specific applications. Copying and pasting to and from an editor, for example, works fine in our tests.
Hi, logs show that that NoMachine is broadcasting correctly. So, we need to understand why your client is not receiving from the problematic Macbook. Either the Macbook 2017 server is not on the same LAN as the client (they must not be subnets), so verify this. And check that the firewall of the 2017 MacBook Pro is not filtering the traffic. You can do that by temporarily turning it off.
Can you send us the logs from the Mac? Follow the instructions here: https://kb.nomachine.com/DT07S00243 Enable debug first, then reproduce the problem, zip and send. You can attach them here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Hmm, can you try installing from the command line with
nomachine-packageName_packageVersion.exe /usbinstall="0"? This should disable USB from the onset and set in node.cfg:EnableUSBSharing none.Hi, can you enable debug and send us the server-side logs of the affected Macbook, so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Attach them here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Hi, it could be related to permissions. Can you check in Accessibility, Screen Recording and Full Disk Access that NoMachine and nxnode (a component of NoMachine) have been correctly added in the Privacy panel? Remove and add again if necessary. This article shows the panels to check: https://kb.nomachine.com/AR11Q01061
Hi, can you enable debug and gather logs from the Windows machine? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. Enable debug, connect from Mac to the Windows server to reproduce the problem and then extract the logs.
Attach them here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
should NoMachine even be able to connect through a VPN on the router where the IP is on a separate subnet while the mac is in standby
NoMachine’s WOL won’t be effective in that case.
So we can close the topic. I only suggested to gather logs if the problem of not being able to connect persisted. But this seems to be solved 🙂
It could be that you are encountering this known issue:
Cannot use 4096 bit RSA keys for key-based authentication in web sessions
https://kb.nomachine.com/TR08Q09394Please try the available workaround.
Hi, can you tell us what Windows OS version it is? Did you try clicking “update driver” in the Windows dialog (left of image)? Are you using a USB hub maybe?
In the meantime you could trying disabling the NoMachine drivers and see if that helps.
How to disable or uninstall NoMachine USB drivers on Windows
https://kb.nomachine.com/AR12O00955Hi, what deb distribution are you running, Cinnamon or XFCE? We’ve heavily tested both and don’t have any issues. A “wrong deb package” such as 32-bit instead of 64-bit or vice-versa would still open.
Can you try starting player from the command line ( /usr/NX/bin/nxplayer)? What is the output?
It would also be useful to check the NoMachine logs and even the system logs of the affected installation.
Hi, it’s not clear to us what you tried doing. Can you send us the NoMachine logs of both the Windows (client) and the Sonoma (server) machines? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. There are 4 steps to follow. The fourth step is for the device you are connecting from.
Attach them here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
In any case, perhaps the separate network timeout when in standby is something that should have been reported and investigated before now.
We’ve not seen any issues with 1) the automatic software update dialog blocking remote access for NoMachine and 2) nor interfering with other applications in our tests. No other users have reported similar issues.
Please confirm: are you able to connect with NoMachine now? Are you also able to connect with NoMachine when the Mac has gone to sleep? Next time, if you have problems when connecting with NoMachine, the best thing to do is to zip up the entire .nx home directory on the Mac server and send it over, and we can take a look. If you encounter a problem which is reproducible, then in that case, enable debug first, reproduce the problem and send us the logs. The steps to reproduce the problem would also be useful to us. Here is the link to the instructions in case you need them next time: https://kb.nomachine.com/DT07S00243.