Britgirl

[Britgirl]

Hi, can you confirm that the check box “Start the server at system startup” is showing as enabled? Go to ‘Server setting’ on the affected computer, open NoMachine and proceed to Server settings -> Status -> just below “Restart the server” there is the checkbox.

[Britgirl]

Logs show multiple lines like:

mount.c:68): Messages from underlying mount program:
(mount.c:72): mount error(13): Permission denied
(mount.c:72): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
(pam_mount.c:522): mount of Programme failed
(mount.c:68): Messages from underlying mount program:
(mount.c:72): mount error(13): Permission denied
(mount.c:72): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
(pam_mount.c:522): mount of iso-images failed

Why this is happening, we can’t say. It indicates problems with your system, and not NoMachine, given that on your other server, everything is working without any issues.

[Britgirl]

Hi,

Enterprise Desktop (on all supported platforms) is for accessing the physical display of the computer you want to access. On Mac and Windows it cannot create virtual displays. The exception is on Linux.

In the case of Linux, when connecting to the physical desktop which doesn’t have an X server running (e.g. it’s a headless machine), NoMachine is able to use its own display service (which is an embedded X server) to let users connect seamlessly to a physical desktop running in the background on the remote machine, what we call a “virtual display” or “virtual desktop”.

Enterprise Desktop cannot create multiple virtual displays on Linux. To do that, you need one of the products from the NoMachine Terminal Server for Linux suite e.g Workstation. Workstation can run up to 4 “nomachine virtual desktops” on the same host.

Further references:
https://www.nomachine.com/terminal-server-family
https://www.nomachine.com/product&p=NoMachine%20Workstation

[Britgirl]

A more elegant solution is using DDNS. Then you could use a domain such as mynomachine.ddns.net, but for that you need to configure a DDNS service on the server side.

I don’t see a solution other than changing the entry in the connection configuration file on client side.

[Britgirl]

To know where a user is connecting from, you can look in the nxd log which shows for example “Info: Connection from 192.168.68.192 port 46684 process 22708 started on Fri Nov 18 05:50:37 2022.”.

 

/usr/NX/var/log/ on Linux
%PROGRAMDATA%\NoMachine\var\log\ on Windows
/Library/Application Support/NoMachine/var/log/ on macOS.

[Britgirl]

The logs don’t indicate any issue with NoMachine software. Rather there are multiple reconnects which would indicate problems with your network. Statistics show high latency which also indicates network issues. We can see “268 ms latency 5s, 221 ms latency 30s”.

For 5 seconds there was an average of 268 ms latency and for 30 seconds there was an average of 221 ms latency, so you should looking in to your network conditions. It might not even neccessarily be a bandwidth problem, but maybe some other bottlenecks like router, switch, or network card even. Maybe you could do a ping and traceroute and monitor them when you’re reproducing the problem.

[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.

[Author]

Posts