Today, I had to deliver a talk on Security features in .NET and IIS and I was going through the www.iis.net website. In the past I had been there for Smooth streaming and other stuff but I stumbled upon the tools, a truck load of them that are very handy utilities while managing a webserver.
- URL Scan
- Site Shell
- Server Defender
and much more related to security at http://www.iis.net/downloads/Security
and with respect to performance http://www.iis.net/downloads/Performance
Ok, and my titbit for this post is that, if you want to use the URL Scan utility on your server running IIS 7, IIS 7.5, you need to enable IIS 6 Metabase Compatibility before configuring the tool.
Here is a write up on the same site to do that at http://learn.iis.net/page.aspx/125/metabase-compatibility-with-iis-7/
Recently, one of the queries I had was on “TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond” while consuming a web service over proxy settings. Setting the UseDefaultWebProxy to true didn’t help with this error.
I had earlier written a post on explicitly setting the proxy in the configuration file for Web Services. The scenario here though was, a WCF Service Client trying to consume the web service.
However, the same work around proved helpful. After setting the proxy explicitly, the web service could be consumed by the WCF Client.
The proxy setting that you want to add to the config file is as below:-
usesystemdefault = "false"
This would go within the <configuration> </configuration> tags. You can read the post written earlier at http://geekswithblogs.net/ranganh/archive/2005/08/29/51474.aspx