Error 108 after installing Active Directory on WinS2k12

[geekabit]

Hi,

I cant figure out why after installing roles and features – active directory domain feature – I cannot connect to the server via nomachine. All i get is error 108. Please help me. I did open port 4000 manualy and it didn’t help.

Kind regards

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

[octopus42]

I would get this error too on Windows Server 2025 with AD. I made a post about it but going back and forth with logs I ultimately gave up. The issue for me started the moment my old v8 release was upgraded to v9. And every release after that, I could never get past error 108. The nx user has the right permissions, added to the correct services but it just wouldn’t work.

Luckily I had the installer for the older v8.16.1 release and that just works, every time. Upgrade to any v9, it breaks, go back to v8.16.1, it works. So for my homelab, I decided to keep server 2025 locked at 8.16.1.

I’d be curious if you go to a v8 version if it works

[Britgirl]

We are investigating. Thanks for the additional information about v8 working well. Are you able to submit those logs to us anyway? They would be useful to us because so far we’ve been unable to reproduce the problem. Please enable debug (level 9) on the NoMachine server host, restart, then reproduce the issue. Also, you mentioned earlier that you install roles and features, can you give us some more information about that? Are you using default roles or are you creating user permission groups and adding some users automatically there? 

[octopus42]

Do you want logs from both a connections when the server is v8 and v9? Or just the v8?

Hope I answer this correctly; For features, what I have that’s probably most relevant is, Active Directory Domain Services, DNS Server, Group Policy Management. There’s things like WSL, etc that I can’t see being an issue.

In Active Directory, I do have a custom OU where all my systems sit as well as created users. I also have custom groups defined that point back to default groups like Domain Admins and Domain Users. The nx user is in the default Users OU and not my custom Users OU.

And in the local security policy for the domain, the nx user is apart of the following user rights assignments:

• SeServiceLogonRight
• SeDenyInteractiveLogonRight
• SeTcbPrivilege
• SeAssignPrimaryTokenPrivilege
• SeIncreaseQuotaPrivilege

[Britgirl]

Sorry for not specifying. Logs from a server with version 9 installed, please.

[Author]

Posts