klapas1

[klapas1]

Hi,

Thank you for the update. Given that the nx user exists both locally and in the domain, the best course of action is to uninstall NoMachine from the domain controller.

1. Uninstall NoMachine from the domain controller.
2. Verify that the nx user account has been removed from the domain using commands that I sent you before.
3. Install NoMachine locally on your target servers instead.

This ensures that the application is running on the appropriate machines without impacting your domain services.

Regards,

Klaudiusz

[klapas1]

Hi,

Is it possible that NoMachine was installed on a domain controller?
If so, you can check whether the user nx exists using the following commands:

net user "nx" /domain – checks if the user exists in the domain
net user "nx" – checks if the user exists locally or in the domain

If the nx user is part of the domain, please install NoMachine locally on the target servers instead of the domain controller.

Additionally, please refer to the article regarding known issues with NoMachine in Active Directory domain environments.
https://kb.nomachine.com/AR04O00925

Regards,

Klaudiusz

[klapas1]

Hi.

A fix for this issue will be included in the next released version. In the meantime, please try the workaround described below.

NoMachine – Unable To Mute HDMI (IEC958) Audio Output Via NoMachine Player Interface On Linux – Knowledge Base

Regards,

Klaudiusz

[Author]

Posts