BrotherJones
Technical User
Hello all,
question - is there an issue with having an exchange server use two separate ip addresses (specifically in regards to OWA)?
the problem is that I can't enable forms based authentication at all. I've done it on about 10 other production servers without any issue, but on this particular server it still prompts me with the old style logon box. I put the check mark in for using Forms Based Authentication, everything takes without any errors, but no forms access.
I'm not exactly sure how this was setup, but under IIS there are two web sites that have exchange virtual directories under them - 1. The Default Website and 2. An admin created website called NewExchange Site. Both websites have the same exchange virtual directories underneath them - Exchange, Exchweb, Microsoft-Server-ActiveSync, OMA, and Public. BUT only the Default Website has the Exadmin directory under it.
by the way, the there are two ip addresses assigned to the exchange server, with a separate ip address being used for the two exchange website -
Default website = 10.9.2.100
NewExchange Website = 10.9.2.101
My thought is that the former admin copied the default website (after exchange was installed). He then assigned a separate ip address to that site to use for the new website for the secured OWA access.
For OWA and OMA (direct push), all users are using the NewExchange Website (this is where the public cert is applied)
My thought is that the NewExchangeSite (with identical exchange virtual directories to the default website but a separate ip address) may be causing the forms based authentication issue.
My thought is to copy the public cert from NewExchange Website back to the Default Website and turn off the new site (using the default website as the secure website for exchange OWA, hoping that this will allow me to use forms based authentication.
Or should I just swap ip addresses used by the website (ie, giving the NewExchange Website - the main ip address of the
server)?
thanks for any thoughts on this.
question - is there an issue with having an exchange server use two separate ip addresses (specifically in regards to OWA)?
the problem is that I can't enable forms based authentication at all. I've done it on about 10 other production servers without any issue, but on this particular server it still prompts me with the old style logon box. I put the check mark in for using Forms Based Authentication, everything takes without any errors, but no forms access.
I'm not exactly sure how this was setup, but under IIS there are two web sites that have exchange virtual directories under them - 1. The Default Website and 2. An admin created website called NewExchange Site. Both websites have the same exchange virtual directories underneath them - Exchange, Exchweb, Microsoft-Server-ActiveSync, OMA, and Public. BUT only the Default Website has the Exadmin directory under it.
by the way, the there are two ip addresses assigned to the exchange server, with a separate ip address being used for the two exchange website -
Default website = 10.9.2.100
NewExchange Website = 10.9.2.101
My thought is that the former admin copied the default website (after exchange was installed). He then assigned a separate ip address to that site to use for the new website for the secured OWA access.
For OWA and OMA (direct push), all users are using the NewExchange Website (this is where the public cert is applied)
My thought is that the NewExchangeSite (with identical exchange virtual directories to the default website but a separate ip address) may be causing the forms based authentication issue.
My thought is to copy the public cert from NewExchange Website back to the Default Website and turn off the new site (using the default website as the secure website for exchange OWA, hoping that this will allow me to use forms based authentication.
Or should I just swap ip addresses used by the website (ie, giving the NewExchange Website - the main ip address of the
server)?
thanks for any thoughts on this.
