Forum Replies Created
-
AuthorPosts
-
Britgirl
KeymasterStill want the logs?
Yes 🙂
I asked the question about new install just to understand if you had seen the exact same error on 8.13 . Send over the logs anyway.Britgirl
KeymasterHi, is this the first time you’ve installed NoMachine, or were you using 8.13 beforehand and the problem was also present?
Are you able to send us the logs from both machines? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243 (steps 1 -3 are for the server, the 4th step is for the client side logs)
Post them here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email.
Britgirl
KeymasterHi, to not see other computers on the LAN go to Player settings > Security > Network browsing and tick the box “Don’t show other computers on this LAN”. That would have to be configured on each of those other computers.
Britgirl
KeymasterCan 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.
October 8, 2024 at 16:52 in reply to: Discovery doesn’t work for MacBook Pro, does for other MacBook #50066Britgirl
KeymasterHi, 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.
Britgirl
KeymasterCan 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!
Britgirl
KeymasterHmm, 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
.Britgirl
KeymasterAnd the instructions in the article also didn’t help?
October 8, 2024 at 09:24 in reply to: Discovery doesn’t work for MacBook Pro, does for other MacBook #50043Britgirl
KeymasterHi, 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!
Britgirl
KeymasterHi, 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
Britgirl
KeymasterSorry for the delay in responding. We weren’t able to reproduce the problem but it looks like uninstall scripts didn’t run properly.
In which way did you uninstall NoMachine:
1) moved NoMachine.app to trash bin,
2) removed /Applications/NoMachine.app dir from terminal,
3) removed /Applications/NoMachine.app dir from SSH session?Did you see message boxes requesting password and administrative
privileges for NoMachine Uninstall?https://forum.nomachine.com/wp-content/uploads/2024/02/PasswordNoMachineUninstall.png
https://forum.nomachine.com/wp-content/uploads/2024/02/AllowNoMachineUninstall.pngDo you still have /Library/Application Support/NoMachine/var/log. If
yes, could you pack the dir and send to forum[at]nomachine[dot]com?Could you send also output from commands:
which bash
ls -l /bin/bash
id nx
Britgirl
KeymasterHi, 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!
October 7, 2024 at 16:24 in reply to: Unable to connect after automatic update prompt raised while screen locked #50029Britgirl
Keymastershould 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 🙂
October 7, 2024 at 15:56 in reply to: Key based authentication for web connections with NX protocol #50027Britgirl
KeymasterIt 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.
Britgirl
KeymasterHi, 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/AR12O00955 -
AuthorPosts