Jump to content

NTLM Blocking breaks Remote Session Launcher

Recommended Posts


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

  • 4 weeks later...

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...