Forum Replies Created
-
Posts
-
Hi, thanks for following up. So that we can understand better, can you confirm if the server side machine is Windows or is it another OS? If so, which one?
Hi, thanks for the attachments. We need the server-side logs as well. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Hi, thanks for taking the time to report it. We’re currently investigating a similar behaviour. For now, can you try enabling “Always show remote cursor pointer” in the Input settings menu? When you’ve enabled that, check whether the local and the remote cursor are in the same position when you click on the tabs. A brief video would be useful as well.
Hi, can you send those multiple attachments as a zip (here)?
Out of interest have you tried connecting from the Windows machine to your Mac?
Are you using the latest NoMachine software both client and server sides? Can you try disable Wayland and tell us if that helps? If not, are you able to send us the server-side logs so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Update: user communicated separately that the problem was fixed. TS was not running on both devices.
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 😉