Forum Discussion

Chris_R_17943's avatar
Chris_R_17943
Icon for Nimbostratus rankNimbostratus
Sep 07, 2008

Problem is IIS Setup

I will try and be as descriptive as possible here.

 

 

One VMWare virtual server hosting multiple QA IIS sites.

 

One IIS Site in particular called 'stores'. Within stores there are multiple host headers such as:

 

 

10.10.10.1 store1.qa.stores.com

 

10.10.10.1 store2.qa.stores.com

 

10.10.10.1 store3.qa.stores.com

 

 

In DNS we have A records pointing to each entry to the external ip (example 65.64.188.55). In the firewall we have the external ip NAT'ing to 10.10.101.1. We have a virtual server setup and the profile resource is assigned the 10.10.101.1 address. When we try an access the sites they are not coming up. We have other IIS sites on this same server using the same IP of 10.10.10.1 that are working fine going through the big ip. The difference seems to be the number of Host Headers we have for this particular IIS setup.
config
design

1 Reply

Sort By
  • hooleylist's avatar
    hooleylist
    Icon for Cirrostratus rankCirrostratus
    Sep 08, 2008
    It sounds like the servers are configured via host headers to only answer for their specific host name. If you could modify this to the hostname which resolves to the virtual server IP address, then you wouldn't need to make any changes on LTM. So you could have stores.qa.stores.com resolve to the external IP 65.x.y.z. That public IP would be NAT'd to the virtual server IP, 10.10.10.1. Each of the servers would be configured to answer for stores.qa.stores.com.

     

     

    If that's not an option, you could use an iRule to set the hostname based on the selected server. nmenant posted an example in this post (Click here).

     

    Aaron