fisherman

[fisherman]

Perfect, I am glad that it helped.

[fisherman]

I understand you in relation with the price of Cloud server, but i would recommend that you try its functionalities.

When we want to speak about NoMachine servers behind NAT, basically you are going to be able to use any NoMachine server products behind firewall, but in order to use and control them from public network, you will need to setup port forwarding of different public port to the specific internal machine. For ex:

publicIP:24000 --> IP1:4000
publicIP:34000 --> IP2:4000

[fisherman]

As from the error message you mentioned in NoMachine “Authentication failed.” it looks that you did user wrong host username and password.

Please see following article Username formats supported to log-in to NoMachine by password authentication.

[fisherman]

I feel that issue is more related to gnome-terminal and its implementation. I found some articles that speaks about problem https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/194.

I noticed additionally when I dont have any user logged on physical display this command worked for me, but i tried on Ubuntu 21.04.
DISPLAY=:1002 dbus-launch gnome-terminal

[fisherman]

I am happy that my information helped you.

[fisherman]

I would recommend that you try NoMachine Cloud server evaluation NoMachine Cloud Server and setup multi node environment by connecting your local network machines to Cloud Server. Here are some information on how to setup Cloud Server based on your needs AR05R01090 – How to choose the most appropriate Cloud Server setup and configure it to allow access to NoMachine Servers.

[fisherman]

I am not sure that I clearly understood what is your problem with crontab and NoMachine. I tried simple command to start application to desired virtual or physical desktop and application did show on required display.

Here is the command I used:
user=fisherman
XAUTHORITY=/home/$user/.Xauthority DISPLAY=:1002 firefox

[fisherman]

Your used resolution are very likely related to the out of memory issue described in following FR – FR09Q03870 – Providing NoMachine Windows packages at 64bit.

[fisherman]

Install output does not say clear information what happened with some files. As I noticed you are installing 32bit package, please can you verify that you are using 32bit OS?

You can check that by executing uname -m

[fisherman]

I need to say yes, you cannot enforce that behavior as NoMachine would still send all displays until that feature is implemented.

Despite this FR05N03113 – Creating a separate video stream for each monitor would be beneficial in your setup, I think what you really need is FR09Q03870 – Providing NoMachine Windows packages at 64bit
since I think that your issue is due to an out of memory problem of 32bit application.

On that regard, please can you tell about resolutions you are using on remote screen.

[fisherman]

Thanks for letting us know. I might not get to New Jersey in the near future, but I can happily accept a virtual beer or coffee 🙂

[fisherman]

I am thinking that you are have selected “Resize remote screen” (see screenshot). For remote resolution to stay the same please use “Enable viewport mode” or “Scale to window”. Please find more information in the article Some tips about resize and scaling options for NoMachine client version 4 or later.

Attachments:

1. 

   Screenshot_resize.png
   

[fisherman]

I think workaround for your case is to call sudo /etc/NX/nxserver --restart just after [removed] start.

[fisherman]

You can create connection files by clicking the Add button in the client top menu, and use them through the Machines User Interface or by directly accessing the NXS files in ~/Documents/NoMachine folder.

More details here:
https://www.nomachine.com/getting-started-with-nomachine

[fisherman]

Possibly DaVinci Resolve is now configured to use PipeWire and you need to select PulseAudio. Can you check possibly if you can select PulseAudio in DaVinci Resolve Preferences > Video and Audio I/O.

[Author]

Posts