Tom

[Tom]

Hi Robert,
today I installed on VM Windows 10 Enterprise OS.
I added it to existing Active Directory.
I created a localadmins group in AD with rights to install software.
I created a localadmin user and added it to the localadmins group.
I logged into Windows 10 with the localadmin user and installed NoMachine 8.4.2 from http://www.nomachine.com.
After restarting Windows 10, I can connect to this desktop, I see the NoMachine icon in the tray.
Everything works without a problem.

Your problem seems to be related to your machine configuration or premissions in the GPO.
You should discuss this issue with your company administrators.

Regards,
Tom

[Tom]

Hi Robert,
I understand that you have administrator rights on this computer and can install the software as a domain user?
Do you also have domain administrator rights?
When you are at home, you log in to a domain or local account, e.g. computer-name\localusername?
Do you have antivirus software installed on your laptop?
Any other computer security software?

When installing NoMachine, are you connected via VPN to the company?

The only thing that comes to my mind is to check system files or corrupted files
https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3- 966e85d4094e

Maybe administrators from your company will help with the installation?

Regards,
Tom

[Tom]

Hi Robert,
now the logs are full of information.
From the logs I deduce that your Windows is connected to Active Directory (AD), but has lost connection to Domain Controller (DC).
Run cmd as administrator and with command  nltest/dsgetdc:[domain-name] check if you are connected to DC
[domain-name] replace with your domain eg. test.local
Most likely, after repairing the connection to AD and reinstalling NoMachine, everything will work as it should.

Regards,
Tom

[Tom]

Hi Robert,
log file nomachine_log.zip is corrupted, I can’t unpack it.
Please check it and upload it again.

Regards,
Tom

[Tom]

Hi,
The logs look strange.
Have you set the log level to 7? SessionLogLevel 7 key in InstallationDirectory/NoMachine/etc/server.cfg?

Can you uninstall NoMachine?
Verify that all directories have been deleted, if not delete them manually.
Install NoMachine, set the log level to 7, restart Windows and then collect and upload the logs again.

Before installing NoMachine, follow the Windows repair steps from this link:
https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e

What is the version of Windows home or professional?
Which version is e.g. 22H2?
What type of system is it 64 or 32 bit?
You can find this data in the system tab in the system settings.

Is this a clean install of Windows or is it an upgrade from Windows 7 or 8?
How much memory does the computer have?

Regards,
Tom

[Tom]

Hi Teknicianexpertiz,
I don’t know if such a change will be possible. This is definitely the easiest solution.
When explaining to them what effect you want to achieve, tell them that you need to open a port on your router and forward this port to your local computer.

Regards,
Tom

[Tom]

Hi Wintermute,

I solved it in this way:
Pull down the Apple menu and go to “System Preferences”;
Choose “Dock & Menu Bar” preferences;
Uncheck “Automatically hide and show the menu bar in full screen” so it’s disabled.

I don’t know if you are using two screens ?
For one monitor I set it to “In Full Screen Only” and open NoMachine Client.
For a dual monitor setup I set “On desktop only”.
To set NoMachine Client to full screen mode I use CRL+ALT+F keyboard shortcuts.
You can use page-peel or CTRL+ALT+0 to change NoMachine Client settings.

Regards,
Tom

[Tom]

Hi Teknicianexpertiz,
this unfortunately looks like double NAT.
If you do not have access to the router from 10.11.x.x network, you will not be able to forward the port to your router on the 192.168.2.x network.
Without this, NoMachine will not work.

Can you describe how your network is configured in the place where the computer you want to connect to from the outside is located (NoMachine Server)?
Do you have a router?
Do you have a separate Access Point and is the computer you are trying to connect to (NoMachine Server) connected to it via WiFi?

A solution can be to create a tunnel that will connect the computer to which you want to connect to on the VM on e.g. Amazon AWS. Then the connection that comes to the machine on AWS will be redirected to the NoMachine Server behind the double NAT. Unfortunately, this configuration requires technical knowledge and an account with one of the cloud solutions providers.

Regards,
Tom

[Tom]

Hi Gorkmc,
the installation logs looks OK.
I don’t know what could be causing your problems. Perhaps the NoMachine logs will help.
Please read the article: https://kb.nomachine.com/DT11R00181
Collect logs and upload them.

Regards,
Tom

[Tom]

Hi Gorkmc,

We will need the NoMachine installation logs. You can find the installation logs in the directory C:\ProgramData\NoMachine\var\log
The file name is  nxinstall.log. Please send via attachment on the forum.

Regards,
Tom

[Tom]

Hi Teknicianexpertiz,
run on NoMachine Server command in the console: traceroute whatismyip.com and paste its results on forum.

Remove the last two numbers from all IP addresses e.g. 80.92.83.99 replace with 80.92.x.x

Addresses you don’t have to change
192.168.x.x
10.x.x.x
172.16.x.x – 172.31.x.x

these are private addresses, they do not identify your network.

If you paste something that will not be safe, the moderator will remove it before approving the post.

Regards,
Tom

[Tom]

Hi Gorkmc,

you must first check if the NoMachine server is working properly on computer A (Notebook). You should see the NoMachine icon in the windows tray.

When you move the cursor over it and press the left mouse button, a menu will appear, select “show server status” from it. In the window that will appear you should see a green dot and the words “server running”. This means that the problem is not the NoMachine server not working. What do you see? Can you submit a screenshot of Server status?

Regards,
Tom

[Tom]

Hi Steveatsws,
I tested the “ListenAddress” key on Ubuntu 18.04 and NoMachine 8.4.2. It works as it should.
My Ubuntu has two interfaces which have IP 10.0.136.88 and 10.0.112.202. I can connect to both via NoMachine.

When I set the key in the server.cfg file:

NXdListenAddress "10.0.136.88"

I saved it and restarted the Nomachine server:

sudo /usr/NX/bin/nxserver --restart

I cannot connect to the address 10.0.112.202

Maybe you didn’t restart Nomachine after changing server.cfg?

Regards,
Tom

[Tom]

Hi Manchys,
Just to be sure, I set up NoMachine on a VM with Ubuntu 18.04 and two NICs. I had no problems like you.

Please prepare NoMachine logs according to the article: https://kb.nomachine.com/DT11R00181

At the beginning, we will only need logs from the server.

Start with the situation where you are connected to the NoMachine server via WiFi, disconnect the NoMachine client, connect the ethernet cable, wait two minutes, and try connecting via WiFi again.

Regards,
Tom

[Tom]

Hi Steveatsws,

I installed NoMachine Free
 on my Jetson Ubuntu 20.04.
I have Nvidia Jetson Nano – ARM Cortex A57 4x 1,43 GHz, Nvidia Maxwell
Because it has one built-in card, I installed the second LAN via USB.

I did a test, connected both cards to ethernet cables. I connected from the NoMachine client to the server, first to the IP address of the first card, I disconnected NoMachine client,  then I connected to the IP of the second card. Everything worked.
I disconnected the network cables in the second card and connected to the IP of the first card. Everything was still working.

I don’t know what could be causing your problems. Perhaps the NoMachine logs will help.
Please read the article: https://kb.nomachine.com/DT11R00181

Collect logs and upload them.

P.S. I saw you opened another thread on the forum, maybe we can move the Jetson discussion there?

Regards,
Tom

[Author]

Posts