If you have tried to create a web or a http request to an external resource using asp.net or SharePoint (for example in a webpart or a timerjob) you might get a nice error message like this:
“The remote name could not be resolved”
So if you are running your request with the host account or network service account and trying to request an external resource like google api or other web applications inside your company, you might not get the proxy settings.
A good explanation can be found here written by Rick Strahl.
He suggests to add the following to the web.config file of your application:
<proxy bypassonlocal=”true” usesystemdefault=”false” />
This disables the automatic use of the proxy. For more information please look also at this support article from Microsoft.
There is still another option which might work as well. Please look into the proxy settings of the Internet Explorer and check if they are configured right.
This solution worked for me fine.
..:: I LIKE SHAREPOINT ::..The article or information provided here represents completely my own personal view & thought. It is recommended to test the content or scripts of the site in the lab, before making use in the production environment & use it completely at your own risk. The articles, scripts, suggestions or tricks published on the site are provided AS-IS with no warranties or guarantees and confers no rights.
He is Consultant for SharePoint Solutions for collaboration, communication and business processes. He provides his customers applications based on standard features as well as development or combining the power of several microsoft tools like Dynamics CRM. In his free time he tries to collect tipps and worthy experience in this blog.