There are three, count ‘em three ways to create multiple websites on IIS 4 and 5. First way is to use an unique IP for each site. This is ideal but if you haven’t looked around lately, IP addresses can be sorta scarce (that is of course unless your Harley Davidson or Apple both of whom own a Class A address).

The second way allows you to create multiple IP’s on one address by designating a non-standard TCP port number for the designated web to use. This is the way the Administrative website winds up on the same installation as the default website and both can be accessed. However, you have to designate the unique port number in the URL when accessing it. So instead of www.myvirtualsite.com, it becomes www.myvirtualsite.com:6160 or some other number. You can include the port number in a url so it’s really not problem for web pages to reference port designated web sites. The problem is that you can’s specify a port in a DNS server so if users want to lookup your website, they won’t be able to get to it.

Thus we come the next best thing, host headers.

The good news is this is relatively easy to do in IIS and it works very well. There is virtually no performance penalty and it works with most every browser in use today (browsers must be HTTP 1.1 compliant). You can use DNS to point to the website so internet users can find your host header designate site with no problems. You do have to pay attention to the details however or it won’t work. The biggest downside is that you compromised using SSL. (Microsoft KB Article: Q187504 – IIS: HTTP 1.1 Host Headers Not Supported When Using SSL)

read more »

O SSL (Secure Sockets Layer) é um conjunto de tecnologias criptográficas que fornece autenticação, confidencialidade e integridade de dados. O SSL é mais comumente usado entre navegadores da Web e servidores Web para criar um canal de comunicação seguro. Ele também pode ser usado para fornecer segurança às comunicações entre aplicativos cliente e serviços da Web.

Para dar suporte a comunicações SSL, um servidor Web deve ser configurado com um certificado SSL. Este módulo descreve como obter um certificado SSL e como configurar o Microsoft® Internet Information Services (IIS) para dar suporte a comunicações seguras com navegadores da Web e outros tipos de aplicativos cliente usando o SSL.

fonte

read more »

You can administer your server remotely by running IIS on an intranet or the Internet. You can use the following tools for this purpose:

• IIS Manager: You can use IIS Manager on your server to remotely connect to and administer an intranet server running IIS 5.0, IIS 5.1, or IIS 6.0 (IIS 3.0 and IIS 4.0 are not supported).
• Terminal Services: Terminal Services does not require you to install IIS Manager on the remote client computer because, once connected to the server running IIS, you use IIS Manager on the Web server as if you are logged on to the server locally.
• Remote Administration (HTML) Tool: You can use the Remote Administration (HTML) tool to administer your IIS Web server from any Web browser on your intranet. This version of the Remote Administration (HTML) tool is supported only on servers running Windows Server 2003 with IIS 6.0.

main info em:
www.microsoft.com/technet/
http://support.microsoft.com/kb/324282

O windows XP não foi feito para servir de servidor, mas sim como máquina cliente. non entanto é frequente que se faça uso do windows XP durante o processo de desenvolvimento, então muitas vezes precisamos que o windows XP tenha um comportamento um pouco mais parecido com o de um servidor.

O IIS do windows XP vem configurado por padrão para um limite de no máximo 10 conexões simultâneas. Para algumas actividades de desenvolvimento isso pode ser prejudicial.

Podemos alterar esse limite de conexões simultâneas até um limite máximo de 40 conexões, limite definido pelo sistema operativo.

Para fazer essa alteração aceda o directório adminScripts que estará dentro do diretório do IIS (por default é c:\inetpub) e execute a seguinte instrução, via prompt :

adsutil set w3svc/MaxConnections 40

With Integrated Windows authentication (formerly called NTLM, and also known as Windows NT Challenge/Response authentication), the user name and password (credentials) are hashed before being sent across the network. When you enable Integrated Windows authentication, the client browser proves its knowledge of the password through a cryptographic exchange with your Web server, involving hashing.