- This topic has 1 reply, 2 voices, and was last updated 4 years, 4 months ago by
.
-
Posts
-
I have successfully installed NoMachine on multiple VMs in my homelab. However I’m unable to get it to work on my two Server 2016 domain controllers at the same time. I can install on one and it will work, but when I install on the 2nd, it breaks the first. This goes back and forth and I’ve come to the conclusion that I cannot install it on both at the same time. I believe this is related to the domain controllers having no local users and both trying to share the same NX account in the domain. I think it’s changing the password or security connection with each subsequent install so the previous install’s server no longer runs. Anyone ever experienced similar or have any thoughts on fixing it? Thanks!
Hello whiterussiansp,
It’s necessary to have separate nx user account on each host for NoMachine to work correctly. When you install NM on one of the domain controllers, nx account is created as domain account. This will make it impossible to install NoMachine on the second domain controller. Currently we are not aware of any workaround which would allow to create local nx account on Windows domain controller host.
This topic was marked as solved, you can't post.