Guro

[Guro]

Sorry forgot to mention, please ensure that nxservice is running in the system tray on the target Windows machine.

[Guro]

Hello

We’d need to see the server.log and service.log files from the target Windows machine. To extract full logs from the NoMachine Windows server, please go to the Settings > Server > Security and scroll down and click Take logs. You can attach them here or send direct to forum[at]nomachine[dot]com.

The following article https://kb.nomachine.com/AR06W01291 may also be useful to ensure that MS policy is not dropping permissions for NoMachine.

[Guro]

Hello,

please tell us what Windows version you use for server side host. Check if NoMachine is started and present in tray bar. If not, open console as admin and run the following command:

net start nxservice

and check the result.

Please ensure that the nx user is not registered in the AD users list. What could be happening is that the nx user is registered in the AD users list and is conflicting with a locally created nx user on another host.

Also take a look at case 2 in the following article, it might be useful if the NoMachine service does not start.

Troubleshooting NoMachine in a Active Directory Domain
https://kb.nomachine.com/AR04O00925

NoMachine client side and server-side logs would be useful as well. You can extract them using the instructions here:https://kb.nomachine.com/DT08U00298

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Guro]

hello

If you plan group some users in same rules and not connected to AD, then yes.

thanks

[Guro]

Hello dorkvader,

In reply to your last message, When NoMachine (server) is installed on an Active Directory Domain controller, the nxserver doesn’t start when the machine is rebooted. A symptom of this is that the !M icon is not present in the system tray.

This problem occurs when the nxservice starts before the Active Domain controller service and therefore NoMachine is unable to correctly impersonate the nx user.

To avoid that nxservice is started before the AD service
1)open the registry editor as administrator (redegit.exe in Power Shell). 2) Find this key:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nxservice
3) and add the following string key:
Name: DependOnService
Value: NTDS
4)Save and restart windows.

[Guro]

Hello,

It’s a bit strange as no any issue relates to the nx processes.

Please try the following commands, maybe it will show some NoMachine related processes errors :

Get-WinEvent -LogName “Application” | Where-Object { $_.LevelDisplayName -eq “Error” -and $_.Message -like “*nx*“}

Get-WinEvent -LogName “System” | Where-Object { $_.LevelDisplayName -eq “Error” -and $_.Message -like “*nx*“}

thanks

[Guro]

Please check the Windows event viewer in the Application and System section. The events we are interested in are those which start with nx*, in particular nxexec.exe, nxservice.exe, nxserver.exe, nxlsa.dll.

You can use the following powershell command:

Get-WinEvent -LogName Application -FilterXPath “*[System[(EventID=1000 or EventID=1026 or EventID=1002)]]” -MaxEvents 500

to search faster and scan output data on nx* apps present.

Can you export this output and send us the file?

Thanks

[Guro]

Hello,

Could you take a look at the following article

How to restore proper permissions for nxservice on Windows
http://nomachine.com/AR04V01228

and tell us if the steps there help in restoring permissions?

Thanks

[Guro]

hello

Could you please open the powershell terminal as administrator and run the command:

`net start nxservice`

Then, wait 3-5 seconds and check if the server starts and the NoMachine tray bar appears.

Thank you

[Guro]

Hello,

Please check the folder “C:\ProgramData\NoMachine\var\log”. Is this folder empty?

In addition, please gather the logs and send them to forum[at]nomachine[dot]com, making sure to reference the topic as the subject of the email.

To collect the debug logs please refer to the following article: https://kb.nomachine.com/DT07S00243

Thank you in advance.

[Guro]

Hello

please check Windows event logs if there are critical logs related to nxlsa.exe, nxexec.exe, nxservice.exe apps.

It is possible that some critical info present in Windows logs does not appear in NoMachine logs.

Examples for powershell:

Get-WinEvent -LogName Application  |   Where-Object { $_.Message -like “nxexec.exe” }

Get-WinEvent -LogName Application  |   Where-Object { $_.Message -like “nxservice.exe” }

Get-WinEvent -LogName System  |   Where-Object { $_.Message -like “nxlsa.exe” }

Please check https://www.nomachine.com/AR06W01291

It might help if “nx user” lost permissions due to local policy restrictions.

Thanks

[Guro]

Hello

by default NoMachine does not create user groups in internal cache, just for save ruled. Please provide more detailed information of your using scenario.

NoMachine can set rules on AD group, also it is able to create private group and add users to it. For domain users and how to apply profile rules correctly, take a look at: https://kb.nomachine.com/AR04U01198

 

[Guro]

Hello

please login as use m*****o, open command line window and run command
whoami /priv

It will print user privileges and send to us (via email to forum[at]nomachine[dot]com) so that we can compare for testing.

We suspect that some privileges might be disabled which prevent you from correctly using the NoMachine service.

thanks

[Guro]

Hello

we sent you a link to a debug package. Were you able to install and extract the logs?

Thanks

[Guro]

Hello
The Log Error message indicated that nx user account is invalid. Please ensure that nx user is not registered as ad domain user and has only local profile.

Please open powershell windows as admin and run the following command:
Get-LocalUser -Name “nx”

It might show as local user status.

Thanks

[Author]

Posts