RobertRo Posted March 14 Share Posted March 14 Hello, i'm implementing Passwordstate in a customer environment which is hardened. specifically, the security setting: Local Policies\Security Options\Network security: Restrict NTLM: Incoming NTLM traffic is set to "Deny All Accounts" on all servers. This breaks the Remote Session Launcher: "The authentication Username or Password appears to be incorrect, or the Host is not available. This window will now close when you click the "OK" button, and you will need to correct your login credentials." Switching this setting to "Allow All" immediately makes the launcher work, but this is not desired in this environment. Any chance the gateway can be told to talk kerberos correctly? Link to comment Share on other sites More sharing options...
support Posted March 14 Share Posted March 14 Hello Robert, Yes, we have information in the following manual - just search for kerberos - https://www.clickstudios.com.au/downloads/version9/Passwordstate_Remote_Session_Management_Manual.pdf Regards Click Studios RobertRo 1 Link to comment Share on other sites More sharing options...
RobertRo Posted April 11 Author Share Posted April 11 sorry for my late reply. just wanted to check back that your solution from the documentation works perfectly fine. customer is happy (and me too many thanks, great product! Link to comment Share on other sites More sharing options...
support Posted April 11 Share Posted April 11 Thanks Robert Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now