jcneil4
asked on
Publishing multiple OWA sites thru ISA 2004
Ok- I have OWA working fine for a long time using FBA. It is published via ISA 2004 and works internally as well as externally. This was set up using the recommended method (web publishing rule with a listener configured to use FBA). The listener is configured to use a wildcard cert that is installed on the ISA as well as the Exchange 2003 server. No problem.
I recently installed a new Exchange 2003 server and now have two. I installed the same wildcard cert on it and FBA is enabled. I can access OWA using FBA on the new box just fine internally. I copied the old OWA publishing rule and changed the public name and the internal server appropriately. (the public name resolves to same IP address of OWA-FBA listener). It is setup identical to the original. From an external browser- When I type https://oldserver.domain.com/exchange and supply a new user I am redirected to https://newserver.domian.com/exchange just like expected.
What I get is at this point is:
Error Code 10061: Connection refused
Background: When the gateway or proxy server contacted the upstream (Web) server, the connection was refused. This usually results from trying to connect to a service that is inactive on the upstream server.
It is very likely that I missed something obvious but I am stumped...
I recently installed a new Exchange 2003 server and now have two. I installed the same wildcard cert on it and FBA is enabled. I can access OWA using FBA on the new box just fine internally. I copied the old OWA publishing rule and changed the public name and the internal server appropriately. (the public name resolves to same IP address of OWA-FBA listener). It is setup identical to the original. From an external browser- When I type https://oldserver.domain.com/exchange and supply a new user I am redirected to https://newserver.domian.com/exchange just like expected.
What I get is at this point is:
Error Code 10061: Connection refused
Background: When the gateway or proxy server contacted the upstream (Web) server, the connection was refused. This usually results from trying to connect to a service that is inactive on the upstream server.
It is very likely that I missed something obvious but I am stumped...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Any further info you need?
ASKER
Sorry for the delay- I was sidetracked. I followed your lead and that led me to the answer! While reviewing the monitoring data I noticed that ISA was trying to connect to the firewall external address instead of the internal Exchange server address. I added the local address of the exchange server in the ISA hosts file and bingo.
Thanks
Thanks
Your welcome, and thanks :)