I have ISA and IIS on the same server. IIS hosts 7 websites. Only one site needs SSL and the others are not using the 443 port. Some day I would like to separate IIS and ISA but for today I cannot. The sites are using the same IP address. I am not using host headers. I have valid DNS entries for all my sites. I have destination sets for each of the websites mapping from the external IP to the internal port of each respective site. For SSL I have a server publishing rule ( I am not sure if this is needed) mapping the external address to the internal and using a mapped https server protocol. I have individual listeners set. The one that needs SSL has SSL enabled, I have checked Use a server certificate to authenticate to web clients, integrated checked, and Secure channel checked. When I try to browse to the site using http I have no problem. When I use https I get an error from IE stating a error code 500 (network login failed). At one point this worked fine. In the event viewer I do get a better error.

This is the error but I x'd out my IP address's.

Server publishing rule [HTTPS] that maps 192.xxx.xxx.xxx:443 TCP to 204.xxx.xxx.xxx:443 for protocol [HTTPS Server] failed because the port on the external interface is being used by another application. The Firewall service failed to bind socket for the server on the firewall since another process is using the same port. Check for any other process using the same port and terminate if necessary.

I am not sure if thats the problem though.

I cannot see what else is using 443 so I am at a loss. If you can point out what I am doing wrong or if you think you have an idea please let me know. Thank you for your help in advance.

Mark Moore

Try disabling SSL on the Incoming Web Requests listener and using only your server publishing rule for SSL. The conflict is from both the listener and the server publishing rule both trying to listen on TCP 443, and that won't work.

HTH,
Tom

------------------
http://www.isaserver.org/shinder/

Get It Here!