IIS uses a proxy to request webservice. How to stop this?

Question

I have a problem with a small .Net web application that uses Amazon web service. Everything works fine with the integrated Visual Studio web server. But after deploying it to IIS on the same computer, I get the following error message:

Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht ordnungsgemäß reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat 192.168.123.254:8080 

Which roughly translates to "can not connect to 192.168.123.254:8080"

The computer is part of Active Directory. The AD server was installed on a network that uses 192.168.123.254 as a proxy server. Now it is unavailable and should not be used.

How to prevent IIS from using proxies?

I think this has something to do with the policy settings for Internet Explorer. This "old" AD user has this parameter, but the newly created user does not. I checked all the Group Policy settings and there is no proxy specified anywhere.

The web server runs in the context of an anonymous Internet user account on the local computer. Do local users have settings from AD? If so, how can I change this setting if I cannot log in as this user?

What should I do, where else can I check?

Answer 1

Using a proxy server can be configured in the web.config file. The system.net/defaultProxy element allows you to specify whether a proxy server is used by default or to provide a crawl list.

For more details see: http://msdn.microsoft.com/en-us/library/kd3cf2ex.aspx

Answer 2

Some group policy settings that may be relevant:

Root \ Local computer policy \ Computer configuration \ Administrative templates \ Windows components \ Internet Explorer \ Make proxy settings for each computer - this is disabled by default, which means that individual users on the server have proxy settings configured.

Root \ Local Computer Policy \ User Configuration \ Windows Settings \ Internet Explorer Maintenance \ Connection. In the "Automatically configure the browser" value, "Automatically detect configuration settings" - you can turn off this process to prevent the proxy server from automatically detecting settings.

However, using the defaultProxy parameter, as shown in the hwiechers answer, would be the best way to do this without affecting other processes or users on the machine.

Answer 3

IIS is the destination. The configuration problem is what the call is doing (acting as a client). If you use the built-in .Net communication methods, you will need to configure inside ... Wait ... Internet Explorer.

Oops! This little bugger bit me more times than I remember. I used to have to switch proxy settings in IE 5 or 6 times a day when I switched between internal and external servers. Newer versions of IE have a much better set of "do not use proxy server" rules.

- Clarification - It appears that the user ID used by IIS uses this parameter, you may have to look in the registry where proxy information is stored for each user ID and / or default.