Today while rearranging some IIS websites I came across a particularly frustrating challenge.
The work that was carried out involved adding an additional IP (and NIC) to our web server. Host headers were not an option because the sites use SSL. After applying all the necessary NIC and firewall settings, the pre-existing website, when assigned to this new IP address, would not start. It came back with the message stating that there was a potential conflict using the same ports.
Interestingly, I was able to create a new site which would start. I created this site with the ip from the setup wizard. So what seems to have happened here is the metabase did not get updated appropriately for the pre-existing site. rather than utilise a tool such as httpconfig in this situation, it was far quicker to simply create the new site. If the websites were many, or were part of a cluster, then using the httpconfig windows support tool would have almost been needed.
No comments:
Post a Comment