This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

NTLM passthrough broken

Hello,

recently I stumbled into an issue, that new clients would not connect to our RDWeb server through RemoteApp- and desktop connections.

As they are able to connect using the internal FQDN, but not using the external domain name throwing an 401.2 error, it seems that the reverse proxy breaks the NTLM authentication with the remote desktop webserver although I'm not using reverse authentiaction.

Are you having these issues, too?

This thread was automatically locked due to age.

Parents

0 JoaoSoares over 5 years ago

Did anyone found a way to do NTLM Passtrough via Reverse Proxy?

As stated here: 33277 [9.2] Add support for passthrough NTLM connection

https://news.sophos.com/en-us/2014/11/27/utm-up2date-9-209-released-2/

Even with Reverse Authentication disabled, it's breaking the NTLM authentication.

UTM Version: 9.700-5

Thanks in advance
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 JoaoSoares over 5 years ago

Did anyone found a way to do NTLM Passtrough via Reverse Proxy?

As stated here: 33277 [9.2] Add support for passthrough NTLM connection

https://news.sophos.com/en-us/2014/11/27/utm-up2date-9-209-released-2/

Even with Reverse Authentication disabled, it's breaking the NTLM authentication.

UTM Version: 9.700-5

Thanks in advance
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 DouglasFoster over 5 years ago in reply to JoaoSoares

Why would you send traffic through UTM Reverse Proxy if both client and server are in the same Active Directory domain? If your client is infected, you have bigger problems than blocking an attack on a specific webserver.
Cancel
Vote Up 0 Vote Down

Cancel