This guide is very useful for setting up IP restrictions on IIS7. Thanks to Craig Tucker for providing this.

Thanks to Mitch Tulloch for providing this starter guide for creating websites in IIS 6.0 running on Windows Server 2003.

Click here

Very useful feature to host several websites under one IP address in IIS, these directions are for IIS 6.0 only:

Reference

1. Increase the 10 concurrent connection limit
   
   Are you getting 403.9 "Access Forbidden: Too many users are connected" errors on an XP Pro website? You're limited by default to 10 concurrent connections by design, but this can be increased. First, make sure your default windows script host is set to the console (cscript.exe) one.

     cscript //h:cscript

Next, let's increase the connection limit to 40.

C:\Inetpub\AdminScripts\adsutil set w3svc/MaxConnections 40

Note that this is a hard-coded limit; it can't be increased any further unless you like patching windows system files. You can, however, make the IIS connection timeout more aggressive so connections don't last as long.

1. Run more than one root website
   
   IIS 5.1 only allows one root website. This is fine if your websites run under subfolders:

     http://localhost/MyWebsite1

     http://localhost/MyWebsite2

But it's kind of a pain if your websites must run as root, or need to be tested when running as root:

http://MyWebsite1/

http://MyWebsite2/

In that case, you'd have to edit your hosts file, and switch the default home directory for the default website. But there's a better way. You can hack up multiple web sites in IIS 5.1 via command line tricks, or you can use this nifty little GUI utility which automates that for you. It works great-- you'll even see multiple websites show up in the IIS manager. But bear in mind that, unlike the server versions of IIS, only one website can be active at any given time.

REFERENCE:

http://www.codinghorror.com/blog/archives/000329.html

Spent this morning trying to configure SMTP on IIS. Took some notes that may help to save you some time.

Before you begin it is best to check that the SMTP server is open for connections on the required port (usually 25):

Try this command: "o myISPsmtpServer 25", this will tell you straight away if it is open?

If the port is open you can then proceed to configure SMTP on IIS to relay via your ISP's SMTP Server.

1. Go to the Properties for the SMTP Service and go to Delivery -> Advanced
2. Put the name of your ISP's SMTP server in the "Smart host" field (for example myISPsmtpServer)
3. Save that
4. Back on the Delivery tab, click on the Outbound Security tab
5. Click on "basic authentication" and specify the username and password you use to access your email.

It is possible to test SMTP on an IIS server by creating an email in .txt file and then pasting it into the C:\Inetpub\mailroot\Pickup\ folder.

The text file should contain something similar to this:

to:tbill@externaldomainname.com
from:testuser@internaldomain.com
subject:This is a test.

this is a test.

Make sure there are no spaces between each colon and the text afterwards or it will end up in the badmail folder. If the email is picked up without error it will  be in theC:\Inetpub\mailroot\Queue\ folder.

Reference:http://support.microsoft.com/?id=297700