Forum Replies Created
-
Posts
-
Thank you for explaining.
One last question, when I distribute the public key to the servers, the article mentions to create the authorized.crt in this location: C:\Users\username\.nx\config
Lets say the server is logged on with username John, but the client logging in is user Sam, this does not work. I found that on the client i needed to specify the username John when attempting to connect, where the authorized.crt resides.
What i have done currently is create the authorized.crt under the user nx profile.
Can you confirm that the user logging in from the client should specify the user on the server where the authorized.crt resides? If so, this may not always be known to the client user, therefore I have used nx user instead.
Thanks,
Update: I got it working by specifying the username of where the authorised.crt resides on the server.
Still not ideal. Does this mean we distribute 1 private key amongst our clients and 1 public key amongst the servers? In the first article i posted, it seemed we could specify unique keys in a single hosts file and the clients IP address for added security.
I followed that article, and I get the same error. This time it is asking for username and passphrase, which i entered the passphrase i set and still receive authentication failed.
I had to also revert back EnableNXClientAuthentication back to 0 otherwise it would just timeout trying to connect. Do i need to follow the first article i posted at all? What username should i be entering with the passphrase?
I attempted authenticating using name and password and this still works.
Hi Zaq,
It was missing:
– Act as part of the operating system
– Log on as a service
– Adjust memory quotas for a process
– Replace a process level token
Not using AD, this is just local workgroup for now.
Thanks,