I'm slightly confounded as to if what I'm trying to do is possible, maybe someone can shed some light...
I've got an Exchange Server with Outlook WebAccess secured with an SSL cert for its domain (mail.domain.com). I've got 2 other IIS servers I want to make available publicly, our accounting front-end and a Sharepoint server, and I've configured each one to be available by listening on different port numbers for each, 6000 and 7000 respectively. So mail.domain.com/exchange hits OWA, mail.domain.com:6000 hits accounting, and mail.domain.com:7000 hits Sharepoint. This all works fine without tossing SSL into the ring.
But since our SSL cert is bound to the "mail" subdomain, shouldn't I logically be able to have the other two sites on the other ports SSL secured? I even set the extra two IIS machines to listen on 6001 and 7001 for SSL, but it seems the client-side browser when hitting https://mail.domain.com:6001, I just get a 404, as if IE makes "https" requests automatically via 443, rather than my redefined special port.
Any ideas/enlightenment would be appreciated.