Forum Replies Created
-
Posts
-
We’ve checked that NoMachine works with this particular software out-of-the-box. Make sure that the TS is running on both your devices (see this other topic for brief steps https://forum.nomachine.com/topic/after-restart-can-no-longer-connect#post-46487).
One thing to bear in mind, SSH connections are not possible if you are using the free NoMachine product. For SSH connections, you could try, for example, Enterprise Desktop, it’s available to download and provides 30 days evaluation.
Can you submit a screenshot of what you see when you try to connect with NoMachine when TS is enabled?
Hi,
can you tell us what formats the usernames have that you are using? Take a look at the section for Windows here: https://kb.nomachine.com/AR03S01118, to see what I mean.
Can you show us a screenshot of the dialog that NoMachine shows when you attempt to login?
Ah now I understand. You submitted a topic with the same problem a while back
and in that reply Fra81 replied that “NoMachine doesn’t load the keymaps from the system path (/usr/share/X11/xkb), but it ships its own keyboard config files in /usr/NX/share/X11/xkb. “
The recurring Redis errors like Failed opening .rdb for saving: Bad file descriptor suggest that Redis is unable to write to its dump file (.rdb). This could be due to insufficient permissions, disk space issues, or problems with the file system within the Docker container. Here are some steps to troubleshoot:
i) Check Disk Space: Ensure there’s enough disk space in the Docker container.
ii) Check /usr/NX/etc directory permissions and ownership. Make sure this path is accessible and writable by user nx.
Hi,
what products and version from NoMachine have you installed on the Win 10 desktop and on the Windows 11 laptop? You can check this on each machine by opening the NoMachine application -> Settings -> Updates and see what is written there.
It doesn’t even load a new screen on my laptop.
When you try to connect to the Win 11 laptop from your Win 10 computer, what do you see exactly? Please show us a screenshot(s).
Are you connecting to the physical display and are you running ‘setxkbmap sygi’ in a terminal running on the server?
Hi, this is a known bug and you can find the Trouble Report here:
Enabling EGL capture makes the Gnome Shell freeze when Wayland is used
https://www.nomachine.com/TR01V11053Your workaround of taking out LD_PRELOAD from the Gnome script is the equivalent of our workaround
$ sudo /usr/NX/bin/nxserver --eglcapture no(--eglcapture yesadds LD_PRELOAD to the script). There are no drawbacks related to drivers. The only small drawback of either of the workarounds is that sessions to the physical display might not be possible. Virtual desktop sessions are ok. The patch will be released in the next maintenance of version 8 😉Hi,
on the Linux machine can you follow the instructions in this article?
How to use Intel H.264 HW encoder with NoMachine
https://kb.nomachine.com/AR09O00938Thanks for the additional info. So it seems to be a problem on the Player side related to the drivers installed there. Please disable HW decoding. To do that, follow the instructions here:
How to disable hardware decoding on the client side
https://kb.nomachine.com/AR07U01202Does that help?
Hi, sorry for the delay. The logs are not complete unfortunately. We also need the agent logs and these were missing. You should follow the instructions here and then send again. Please use the title of the topic as the subject of your email. Thanks!
Hello, I’m not sure what the image you pasted into the reply was showing. Please attach it to any reply instead of pasting.
If the external IP and port don’t appear in the UI, it most likely means that the NoMachine’s internal automatic port forwarding was not possible. You will have to configure port-forwarding manually. Take a look at the following article for instructions on how to do that:
How to connect over the internet to NoMachine behind a NAT router
https://kb.nomachine.com/AR04S01122Please also take a look at my response for the following topic https://forum.nomachine.com/topic/nomachine-unable-to-connect-to-windows-machine-over-internet#post-46677.
Hi, please check 2.3. Troubleshooting of the following article How to connect over the internet to NoMachine behind a NAT router https://kb.nomachine.com/AR04S01122.
When we release NoMachine Network, the external IP address (in order to connect over the Internet) won’t be required. Please also take a look at my response for the following topic https://forum.nomachine.com/topic/nomachine-unable-to-connect-to-windows-machine-over-internet#post-46677.
Hello, when the NoMachine (server) computer is behind a NAT router or a firewall, NoMachine tries to use the UPnP or NAT-PMP protocol depending on what is supported by the router. This is to retrieve the public or external IP of the host machine where it’s installed and configure the router to allow a NoMachine client to connect from outside of the private network (port mapping). This port mapping service can work efficiently only when it’s enabled in the server configuration (check that this is the case) and that the router supports UPnP or NAT-PMP and can also accept commands for automatic port forwarding. In some cases port-forwarding must be manually configured.
There is an article with instructions on how to connect to NoMachine when the server is behind a NAT router or a firewall https://www.nomachine.com/AR04S01122. Please check this and follow the steps. It also explains how to enable port-mapping.
In the upcoming version major NoMachine 9, which is not that far off, we will release NoMachine Network. This will permit you to connect to your remote computer without having to do any of the above. You can see more about this here: https://www.nomachine.com/network.
Hi Ade, thanks for letting us know and good to know that everything is working correctly now. If you need help again, let us know here or start a new topic 🙂
Hi,
the steps work for us in our environment.
Please tell us:
– on which machine you generated the key
– which openssh version is installed there
– the exact command you used to generate that key
Last thing to check on the server side (I understand from what you write that you are connecting to a Windows machine) is whether the .nx/config/authorized.crt file is correctly named, has the correct permissions (needs to be readable for All) and that the key is added correctly.