- This topic has 2 replies, 2 voices, and was last updated 3 years, 5 months ago by
.
-
Posts
-
I’m trying to use NoMachine on a Windows AD set of computers. Trying it out with a Windows 10 machine and the Windows 2019 server machine which is AD DC. The NM clients detect the machines and it gets listed. But connecting doesn’t work. I get “Session Negotiation Failed”.
Port is forwarded correctly, port 4001….port 4000 wouldn’t work for some reason.
I looked in the session log but it doesn’t say anything more than the message I posted.
I’m using the latest free version of NM on both machines.
Hello diana12,
Does the failure occur before or after authentication dialog? If it’s after authentication, what authentication method did you use?
Does the problem persist if you use local account instead of domain account? Please, reproduce the issue and gather server-side logs following these instructions:
https://knowledgebase.nomachine.com/DT11R00181#1.4
Send them to forum[at]nomachine[dot]com, referencing the topic in email subject. Thanks!OK this is now fixed. I’ll explain….
The problem was the nx user directory. On Windows server machines, the NoMachine installer needs to create an nx user directory in the profiles folder. When I first installed it, it couldn’t create it, and that was the reason why I couldn’t connect the machines to each other.
Then, I reinstalled using Admin elevation (even though the account already was admin) and this time I didn’t get an error regarding the installer couldn’t create nx directory. After that, everything works fine.
This topic was marked as solved, you can't post.