Вопросы: 30
Привет,
Несколько возможных решений проблемы:
- Обновите .Net до последней версии
- Если у Вас есть Load balancer перед Exchange'м, то проверьте, что он настроен на SSL Bridging. Также проверьте, что TLS настроен правилно с .Net 4x
- The issue is related to NTLMv1. You must disable NTLMv1 and use NTLMv2. It's located in registry HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa Registry value: LmCompatibilityLevel It must be set to at least 3 or higher (best practice is to set it to 5 which is: Send NTLMv2 response only. Refuse LM & NTLM). It's also possible to delete this value to enforce the system default. If it's not set, we treat it as if it is set to 3 (on Windows Server 2008 R2 and later) which is: Send NTLMv2 response only. If you want to manage the setting centrally, you can do so via Group Policy: Policy location: Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options I set mine via GPO "Send NTLMv2 Response only. Refuse LM & NTLM" which is equal to number 5 which is best practice. https://microsoft.github.io/CSS-Exchange/Security/Extended-Protection/#ntlmv1-is-not-supported-when-extended-protection-is-enabled https://microsoft.github.io/CSS-Exchange/Security/Extended-Protection/
- Firewall With https scanning Enable? I Had The Same Problem With our Sophos xg. I have add an exception for the internal Exchange DNS Name (https check, certificate check) and the Problem is gone.
Если Вам помог ответ, то пожалуйста помечайте его как "Ответ". Заранее спасибо!