If you have problems remote debugging then make sure you check all the boxes in the Control Panel\All Control Panel Items\Windows Firewall\Allowed Programs screen.
You may or may not have two entries, I don’t know what causes this.
We recently needed to make sure that anonymous authentication was enabled (at the IIS level) for an application, regardless of the defaults or configuration of the server the application was being installed on.
To do this you can add the following (as a sibling of <system.web>) in the Web.config to make the required IIS authentication settings explicit:
<system.webServer> <security> <authentication> <anonymousAuthentication enabled="true" /> </authentication> </security> </system.webServer>
This will override any settings made in the IIS Manager and the applicationHost.config file.
Whilst on this subject, it’s worth mentioning that you can also configure IIS on the command line using something like this:
appcmd.exe set config "Contoso" -section:system.webServer/security/authentication/windowsAuthentication /enabled:"True" /commit:apphost
There is lots more inforomation about the various settings here:
However, we hit a slight snag with this.
Although we can put the setting in the web.config, the default IIS permissions prevent this particular set of settings from being modifed in the web.config unless you explicitly enable these settings to be delegated to the web.config.
Given that anonymous authentication is enabled by default (unless we’ve changed it as part of the machine image) then for this particular case we felt that it would be simplest just to assume that IIS is set up correctly. We would soon notice if this wasn’t the case.
The better long-term solution would be to make sure that we set up the IIS delegation permissions as part of machine/image setup – to allow us to configure this setting and others in the web.config. This can be done via the command line so could be part of a server setup script.