If the DNS lookup is unsuccessful, this causes the request to fail and generate the "Host Not Found (11001)" error message.У меня была та же проблема, и я написал это. Referencesįor more information about the change to the exception logic for HTTPS Inspection, click the following article number to go to the article in the Microsoft Knowledge Base:Ģ619991 FIX: An application that uses port 443 to connect to a remote web server no longer works after HTTPSi is enabled in a Forefront Threat Management Gateway 2010 environmentThe new exception logic performs a DNS name resolution on the target's fully qualified domain name (FQDN) to determine whether it is part of the destination exception list. Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. To resolve this problem, install the hotfix package that is described in the following Microsoft Knowledge Base article:Ģ735208 Rollup 3 for Forefront Threat Management Gateway (TMG) 2010 Service Pack 2 This problem occurs because of a change to the HTTPS Inspection exception logic that was made in Forefront TMG 2010 Service Pack 2. In this scenario, when the TMG server is used to access an SSL site, a "Host Not Found (11001)" error message is generated. HTTPS Inspection is enabled on the TMG server. Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 2 was applied to the TMG server.Įxternal DNS resolution is not configured on the TMG server. Less SymptomsĪ server is implemented as a downstream proxy server in a Microsoft Forefront Threat Management Gateway (TMG) 2010 environment. Microsoft Forefront Threat Management Gateway 2010 Service Pack 2 Forefront Threat Management Gateway 2010 Enterprise Forefront Threat Management Gateway 2010 Standard Microsoft Forefront Threat Management Gateway 2010 Service Pack 2 Forefront Threat Management Gateway 2010 Enterprise Forefront Threat Management Gateway 2010 Standard More.
0 kommentar(er)
