We'd love to hear about it! Click here to go to the product suggestion community
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?
Can you please DM me the reverseproxy.log and the remote support access code of the UTM to verify the configurations.
Did anyone found a way to do NTLM Passtrough via Reverse Proxy?
As stated here: 33277 [9.2] Add support for passthrough NTLM connection
Even with Reverse Authentication disabled, it's breaking the NTLM authentication.
UTM Version: 9.700-5
Thanks in advance
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.