Forum Replies Created
-
Posts
-
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
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
Hmm interesting. Is the server log in question the server.log found under programdata\nomachine\var\log\? If it is, the log does update, but I can only view it using notepad++ opened in admin mode. If I make a connection, notepad++ will notify me the file updated.
This really does seem like some permission issue and almost like the nx account lacks something. Is there documentation on how to install nomachine on Windows Server and what permissions the nx account needs as well as any policies needing to be set?
The AD and group policy I’m using are the same for what I had configured between v8 and v9, v9 just seems to be particular for some reason
Bumping this. I still have this issue and just submitted logs from the server side with debug level set