From: "Kym Kovan" <[EMAIL PROTECTED]> > You cannot have two different SSL sites n the same IP address as > everything is encrypted by the SSL, even the hostname in the initial > connection, so IIS cannot work out what site is being connected to. You > need to use differing IP addresses.
Actually, I got it working! Somehow, "Integrated Windows Authentication" got checked along with "Basic Authentication" for both sites. Removing the first check, fixed the problem. One thing I did not mention, which I discovered from Microsoft's web site, is that when using host headers on multiple sites running on the same IP where SSL is required, setting the secure bindings must be done as well as using the wildcard certificate with the common name set to (*.domain.com). Set the secure bindings using the following: cscript.exe adsutil.vbs set /w3svc/<website identifier>/SecureBindings ":443:www.domain.com" and cscript.exe adsutil.vbs set /w3svc/<website identifier>/SecureBindings ":443:site2.domain.com" This only applies to Windows Server 2003 running IIS 6.0. There is a whole slew of other steps when dealing with Windows Server 2000. Anyway, its all running fine now. Mike ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:259728 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
