Forum Replies Created
-
Posts
-
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?
When I run the script from the command line, it works, but it doesn’t when it is run from the nomachine’s UserScriptAfterSessionStart.
Can you show us the script?
Web-based access is available in the enterprise-oriented products. You can install, for example, Enterprise Desktop for your operating system on the machine you want to connect to. See the tutorial here:
https://www.nomachine.com/getting-started-with-web-based-remote-access
You will need an account on the remote computer. By selecting ‘Save this password’ that you can see in Fig. 2, the next time you connect you won’t need to re-enter the credentials. Try the evaluation package which you can find here: https://www.nomachine.com/download-enterprise#NoMachine-Enterprise-Desktop
Is the remote server running Wayland? The file didn’t contain agent logs which would have told us this, probably because you cleaned them before submitting.
We have had similar question already in the forums, so please look at https://forums.nomachine.com/topic/error-is-54-connection-reset-by-peer-4.
Then go to the article in our knowledge base:
Connecting to a Wayland-based desktop running in a Linux virtual machine
https://knowledgebase.nomachine.com/AR04R01083