Article ID: 318140 - View products that this article applies to.
This article was previously published under Q318140
Note The following .NET Framework Class Library namespace is referenced in this article:
When you use a .NET client to consume a Web service through an HTTP proxy server, you may receive the following error message:
The underlying connection was closed: The remote name could not be resolved.
An HTTP proxy server exists between the Web service and the .NET client, and the proper proxy settings have not been configured.
To resolve this problem, supply the proper proxy configuration settings to the .NET client.
The following are the default settings in the Machine.config file:
If the default settings do not automatically detect the proxy server settings, set usessystemdefault to false, and then explicitly designate the proxy server. To designate the proxy server explicitly, use either the Machine.config or Web.config file, or specify the server programmatically.
To specify the proxy server, set the Machine.config or Web.config file settings as follows:
To change the settings programmatically by using a WebProxy object, use the following sample code:
Proxy servers that require NTLM authenticationTo set NTML authentication for the proxy server, use the following sample code:
You can also use system-wide proxy as default. To do this, use the following settings in the configuration file:
For more information, see the following Microsoft Developer Network (MSDN) Web sites:
IWebProxy InterfaceFor additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/307220/ )How to configure an XML Web service client by using the .NET Framework to work with a proxy server
Article ID: 318140 - Last Review: June 18, 2012 - Revision: 5.0