fisherman

[fisherman]

Possibly easiest way to do it is to open NoMachine user Interface and edit port with enabling Gateway port. See more information at following article https://knowledgebase.nomachine.com/DT11R00177 in section #3.2.

 

Attachments:

1. 

   Gateway_port.png
   

[fisherman]

Please enable debug, I understood that server host is Windows. Easiest way to enable logs on windows could be to run CMD as Administrator and then execute
"C:\Program Files (x86)\NoMachine\bin\nxserver" --debug --enable all

Then please restart NoMachine server and reproduce problem.
"C:\Program Files (x86)\NoMachine\bin\nxserver" --restart

and after reproducing error please send us created zip archive to forum[at]nomachine[dot]com and then disable debug.

"C:\Program Files (x86)\NoMachine\bin\nxserver" --debug --disable all

More information about enabling debug and collecting logs can be found here: Collect server side logs automatically

[fisherman]

About connecting to the NoMachine from external network I could ask you to check following article: How to connect to NoMachine when the server is behind a NAT router or a firewall.

For easier access, NoMachine has open feature request that will help in your case, you can see more information at FR07J02731 – Creating the NoMachine Network service to let people connect to each other’s computers.

[fisherman]

I did not noticed any issue with using NoMachine with Azure.

What I am thinking is that possibly you are not using correct login form when connecting to the domain user ( user@DOMAIN or DOMAIN\user ).

Additionally can you verify typed password on Windows login screen by using reveal button.

[fisherman]

Please check following article for compiling drivers: What to do if USB support is disabled on Linux with NoMachine 6 or later installed

[fisherman]

I would propose that after selecting desired resolution, you should disable “Resize remote Display” and uncheck ‘Ask the desktop resolution upon connecting’.

Please see following article for additional details Changing how you view the remote host.

[fisherman]

We think that possibly nxfs.kext is not loaded. Please can you check following article: How to allow audio, device sharing and USB forwarding on macOS (‘System Extension Blocked’ since macOS 10.13).

[fisherman]

NoMachine already offers some information for monitoring and performing some administration tasks when using Cloud Server and multi server environment {LINK to CS} in the version 7. Following version 8 Cloud Server will provide much more admin tasks of the connected servers.

In the same time if you are preffer to stay with version 6, maybe you can use some of the monitoring tools by configuring them to monitor some processes or commands.

I can present one simple script that can show number of connected user and if some of the services are disabled :

#!/bin/bash

usersConnected=<code>sudo /etc/NX/nxserver --history | grep -c Connected</code>
echo "INFO: Number of connected users on this server is: $usersConnected"

sudo /etc/NX/nxserver --status | grep -i 'Failed\|Stopped\|Disabled' ; nxstatus=$?
if [ $nxstatus -eq 0 ]; then
   echo "INFO: NoMachine has problem"
else 
   echo "INFO: NoMachine all services are operational"
fi

[fisherman]

Issue of physical desktop not detected could be issue with server configuration where local server is not running. Can you check if the local Xorg/Wayland service is running?

[fisherman]

Currently it is not possible to disable audio mute on the server side. We have opened the following feature request that will solve that situation Giving the possibility to mute/unmute audio on server side.

[fisherman]

One of the connected user can enable remote cursor pointer. It can be done by opening Menu panel -> Input -> selecting “Show remote cursor pointer”.

More information about menu panel you can find in the following document Guide to the Functionality in the Menu Panel.

[fisherman]

Possibly you can edit following key and set it to PhysicalDesktopMode 1 in the server.cfg.

# 1: Restricted. User connected to the physical desktop can
#    interact with the desktop except for resize operations.

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

[Author]

Posts