Forum Replies Created
-
Posts
-
Hi, it could be a permissions issue? Has something changed between the session working and then trying to connect again, like a system update or similar?
To check if it’s permissions, open macOS Settings -> Security & Privacy -> Privacy and add ‘nxnode’ to the list of applications allowed in the accessibility list. If nxnode is already listed, remove and re-add it.
If that doesn’t help, please tell us your macOS version and confirm the version of the NoMachine software that you have installed there.
Hi, strange that you didn’t receive the link. That happened the first time as well :-/ (I will get this checked out). We can of course send it again but we will need to rebuild the debug package for the current 7.9.2 🙂
Hi,
Works fine in NX Mobile (even using proxy)
I assume you mean the NoMachine app? And you confirm you can connect to the Windows server without problems. Are you able to ping the Linux host?
Client itself does not generate any logs
Did you select “Don’t delete log files on exit” (Settings -> Player -> Security) and then start the session? (more info here: https://knowledgebase.nomachine.com/DT11R00181#2)
When connecting to a Linux desktop and after having inserted the login details in the NoMachine’s authentication dialog, NoMachine does one of the following two things.
1) it detects that a physical display is running on the Linux computer and it connects you to its login window. The display manager dialog requires you to insert your username and password and you are then connected.
2) it DOESN’T detect a display running (e.g it might be headless) and NoMachine then asks “Cannot detect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?”. You then click “yes” and you are connected to a virtual desktop which does NOT require further authentication.
In your case you are experiencing both these cases. After a restart NoMachine is not detecting the display and therefore if you have saved your username and password in the NoMachine login dialog, you won’t be prompted to insert them again i.e the display manager does not issue a login dialog. Other times you connect, NoMachine detects that a physical display exists and therefore connects you to it. You are presented with a login dialog by your Linux Mint system.
That’s the explanation and it is happening because your local Linux session is probably still starting when you try to connect with NoMachine 🙂
Perhaps you could give a few more seconds to your system after a reboot before connecting with NoMachine? For example, when NoMachine tells you “Cannot detect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?”, select ‘No’ and try connecting again.
To Brokewood and sam302psu. The information that we received was not enough to understand why you are encountering the issue. We will be preparing a test package and be in touch once it’s ready with further instructions. Thanks for your patience.
Hi
we have no idea why that would be happening and aren’t aware of NoMachine creating issues with VPN connections.
Can you open CMD and execute command:
route printin four cases:1) with nxserver in running status and when you cannot connect though VPN
2) with nxserver in running status and when you can connect though VPN but you cannot ping (as you mention: “Sometimes the VPN connection completes, but I cant ping anything on my employer’s network.”)
3) with nxserver shutdown and you are not connected to VPN
4) with nxserver shutdown and you are connected to VPNPlease copy output to connection files and send via email to forum[at]nomachine[dot]com.
Hi dg, please check your inbox for an email from us. It includes a link to a patched package for macOS 🙂
Thanks for reporting. We reproduced a similar behaviour and will be opening a Trouble Report for this. I’ll update the thread when I have more information.
Hi, we are checking this and will update our knowledge base material soon with the correct procedure.
Quick edit:
How to manage the NoMachine software via Jamf
https://kb.nomachine.com/AR04S01120It looks like this Trouble Report: https://knowledgebase.nomachine.com/TR04T10515. This will be fixed in the next released.
Please confirm the version of NoMachine on the Windows and Ubuntu machines. Also what’s the version of Ubuntu OS?
NoMachine on Windows 11 is tested well in our labs and we aren’t aware of any issues with not being able to connect. Did you reboot after installation?
Also, you mention you also tried on your local network. Was the Windows 11 computer visible in the Player’s Machines panel when connecting from either the iMac or the Win10 computers?
Please submit a screenshot of the dialog message that appears when you try to connect to the Windows 11 computer. Logs from the Windows 11 host would also be useful. You can extract them using the instructions here and sending them to forum[at]nomachine[dot]com. https://knowledgebase.nomachine.com/DT11R00182
Can you tell us how you did the remapping on all the machines?
When I am directly connected to all of those machinesWhat do you mean by “directly connected”?
What version of NoMachine is on the two computers, the Mac and Raspberry machines?
Question: How can I configure NoMachine to set the X font path by default to catalogue:/etc/X11/fontpath.d?
The option DisplayServerExtraOptions accepts X server options, so set the font path using DisplayServerExtraOptions “-fp string”.
maybe the hardware client side settings to disable them didn’t apply until I rebooted?
No, restarting the machine wouldn’t make a difference for hardware decoding, so it is very likely unrelated to hw decoding
As far as I understand, the problem appears only with one application?
Googling I found this: https://support.xilinx.com/s/question/0D52E00006hprh2SAA/vivado-20201-display-problem?language=en_US. Is this similar to your issue?