Cisco TMS IIS single IP with multiple 443 port issue

[Chi Fai Leung]

Hi All Experts,

I deployed the TMS 14.4.1 on the Windows Server 2012 (Ms SQL server 2012 and IIS 8) with Microsoft Exchange Server 2013 and Microsoft CA Server.

Exchange 2013    localhost    443
CA Server            localhost    443
TMS                    localhost     443

It was fail to access multiple https websites with single IP address.

I made some research to solve the multiple SSL 443 of one IIS:
http://blogs.msdn.com/b/varunm/archive/2013/06/18/bind-multiple-sites-on-same-ip-address-and-port-in-ssl.aspx

http://www.iis.net/learn/get-started/whats-new-in-iis-8/iis-80-server-name-indication-sni-ssl-scalability

http://blogs.msdn.com/b/kaushal/archive/2012/09/04/server-name-indication-sni-in-iis-8-windows-server-2012.aspx

I made the wildcard mask cert to push in the Default Website and make the different host names for the different websites, that should use the different hostnames + the wildcard mask certs to make the 443 SSL request, so I can use one IP for multiple websites 443 SSL requests?

But I still got the TMS https://localhost/tms <-- Service Resource Fail ... Actually, I set the different Application Pool already.

[Patrick Sparkman]

I'd highly recommend you put TMS on it's own server.

You can't use multiple website with the same IP and port, it will fail like you're seeing.  You can assign multiple IPs to the server, then go into IIS and set which website will use what IP.  That way each website will have it's own dedicated IP, and will not interfere with each other.

[Chi Fai Leung]

Thanks for yr remind ... I created one more network leg for the Windows server and assign the second IP address to test again .... thx~

[Chi Fai Leung]

Hi,

It was fail for me to separate the other network of the other IP address, but it still fail ... I saw the TMS Application Pool is stop, when I access the https://TMS FQDN/tms

[Patrick Sparkman]

I suspect one of the other applications that you have installed on the server along side TMS is causing some issues then.  I've never attempted anything such as running TMS on any server other than itself, even in our own lab environment, we have it on it's own separate server to be as close to production as possible to replicate issues and for testing.

[Martin Koch]

Its not only a recommendation, its also a requirement that TMS is running on a stand alone server.

[Chi Fai Leung]

I see ... but this is the lab environment, so I don't want to spend one more Windows Server and SQL Server for TMS only.

[Martin Koch]

I would not want to rule out that you could manage to get it up and running with some

virtual directory mappings and merging the two sites, but I have not tried that and

I would also not recommend it.

Just set up a new virtual session with (a demo version of windows) and use TMS on that,

TMS installs its own SQL database, so that should not be a problem neither.