Britgirl

[Britgirl]

You need to forward port 4000 to the local IP of the first Mac and 4001 to the second Mac’s local IP 🙂

[Britgirl]

This is not currently possible, but is planned for a future release.

In the current version, when the user has multiple monitors on the client, it is possible to choose if the NoMachine virtual Linux desktop session has to be spanned on all monitors so that the virtual desktop sees this as one giant monitor, or if each monitor can be treated as an individual monitor. The difference is in the first case when you for example maximize a window, it spans on all monitors. In the second case separate monitors let you drag windows between monitors. Maximized applications only span one monitor.

[Britgirl]

We haven’t been able to reproduce this behaviour, so we ask users who were encountering this issue to update to the latest 8 and open a new topic if the problem is still there, so that we can start a new investigation. This topic is going to be closed.

[Britgirl]

Seems like a permissions issue on the Mac machine.  This TR was fixed in the 8.1.2 release, but it requires that you set the accessibility permissions correctly, after which it will no longer be necessary.

Cannot connect to physical desktop on macOS after a system update
https://www.nomachine.com/TR10S10377

 

[Britgirl]

You could try attaching a dongle if you don’t want the monitor on, so essentially making it a headless Windows machine.

How to solve black screen problem on Windows headless machines
https://kb.nomachine.com/AR05S01124

[Britgirl]

We recently discovered a similar issue but only when using Linux Mint in a VM. Please edit /usr/NX/etc/node.cfg and set following key:

DisplayServerExtraOptions "-eventdelay 0"

and restart nxserver:

sudo /etc/NX/nxserver --restart

Does it help?

[Britgirl]

Zatoichi, thanks for contributing to the thread. As I reported in an earlier reply, our investigations showed a similar issue which we saw on version 7 which was related to how X server “goes offscreen”, not caused by the NoMachine software itself. In all of these cases, the server side was running Linux and X.org was crashing.  See the original thread here:

https://forums.nomachine.com/topic/lock-the-physical-screen-when-somebody-connects-session-disappears

To check what’s happening in your set-ups, and if it’s indeed the same as others have reported, we would need the same information that I asked before. Choose one of the distributions to use where you know you can reproduce the issue. I would suggest we start a new thread at this point, so when you do submit them, I will split this to a new topic and add the details of the environment, including distro version and desktop environment.

1) NoMachine server side logs (see the document here for complete instructions, https://kb.nomachine.com/DT07S00243)

2) the file /etc/X11/Xorg.0.log.old  if its present

3) output of 'sudo journalctl -b'

4) any core files after debugging with https://kb.nomachine.com/AR09L00810

You can send all this information directly to forum[at]nomachine[dot]com. Please use the title of this title of this topic as the subject of your email.

Thanks!

Thanks.

[Britgirl]

The proxy is a NoMachine setting that you enable on the Player side (the machine you connect from), not the server side. You are enabling “Manual proxy configuration” but the message shows that “Failed getting proxy settings” which suggests there is nothing configured in the panel (see attached).

Please show us what you have configured on the Player (open !M on the player, go to settings, select Player, select Security, enable Proxy and then select your preference. You must indicate to NoMachine the details of your proxy server here.)

Attachments:

1. 

   proxy.png
   

[Britgirl]

Ah re-reading I now understand what you were asking. Sorry for the mix-up 🙂 There is no x server running at all on the system you are connecting from, so you are not running XWayland. If this is the case, you are right, the message is not very clear and we decided to change it to something like this:

The NoMachine Player cannot connect to X server
This can be because no X server is running or you didn’t set the DISPLAY environment.
Or it can be because you are running this desktop on Wayland.
The NoMachine Player doesn’t support the Wayland environment without X.
Be sure you run XWayland instead.

We’re working on supporting Wayland, natively without XWayland, but it’s not a priority at the moment, so don’t expect this very soon.

[Britgirl]

The Fn key being stuck is a system bug that was fixed when we moved to the latest macOS API. For the old API it cannot be fixed unfortunately.

[Britgirl]

NoMachine supports desktops running on Wayland. It installs out-of-the-box just like it does on X.org.

Make sure you always include the “What to include” list that we provide when you are submitting a topic or reply 🙂 What did you install on the server side? I.e the computer you want to connect to. NoMachine Free Edition or maybe NoMachine Workstation?

NoMachine needs a desktop environment running on the machine you want to install it one. What DE are you using? What Linux distro is it, and what version?

[Britgirl]

Hi thanks for those. After analysis of the logs, it seems no connection is occurring. At this point we need to look at the player side logs. So you should tick the box “Don’t delete log files on exit” in the Player settings (Security), reproduce and then share the .nx folder with us. Thanks!

[Britgirl]

Hi, Ventura is supported and installs out-of-the-box with default settings exactly the same as other macOS versions 😉

Can’t connect.

To understand why you can’t connect, it would help if knew the error that you are seeing. Can you show us the screenshot of the error that is showing? Or copy and paste the error here.

[Britgirl]

Our current design supports keys 1:1, so if you want Control on the server-side, you have to press Control on the client as well. We’re currently evaluating ways to customize key bindings by mapping some pre-defined system shortcuts (like Command + C on Mac and Control + C on Windows).

[Britgirl]

Hi Fritz, sorry I realised that in my reply the -- are not showing in the command.

In any case, you need to use the full path to the nxserver e.g

/etc/NX/nxserver/Applications/NoMachine.app/Contents/Frameworks/bin/nxserver --debug --enable all

reproduce problem and then collect logs

sudo /etc/NX/nxserver/Applications/NoMachine.app/Contents/Frameworks/bin/nxserver --debug --collect

then disable

sudo /etc/NX/nxserver/Applications/NoMachine.app/Contents/Frameworks/bin/nxserver --debug --disable all

[Author]

Posts