Link to home
Create AccountLog in
Avatar of Mike3066
Mike3066

asked on

Exchange 2010 CAS Proxy

Hi,

On an Exchange 2010 CAS server, I have configured via Powershell:
"Server1/owa (website1)" with internalURL "https://192.168.10.1/owa"
"Server1/owa (website2)" with internalURL "https://192.168.10.2/owa"
"Server2/owa (website1)" with internalURL "https://192.168.10.3/owa"
"Server2/owa (website2)" with internalURL "https://192.168.10.4/owa"

Server1 is in SiteA and Server2 is in SiteB.

When I open a mailbox via OWA (connecting to website1) from SiteA, where

(A) mailbox is from a mailbox server in SiteB, I am proxied to "https://192.168.10.4/owa"

When I open a mailbox via OWA (connecting to website2) from SiteA, where

(B) mailbox is from a mailbox server in SiteB, I am proxied to "https://192.168.10.4/owa"

Question:
(A) is proxied to the wrong internalURL, any ideas how to make it proxy to "https://192.168.10.3/owa" instead?
SOLUTION
Avatar of Busbar
Busbar
Flag of Egypt image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of Mike3066
Mike3066

ASKER

its part of a legacy system that can't be changed and now we're moving to a newer version of Exchange. So any ideas?
as I said remove all of the internal URLs from website 2 on server 2
ASKER CERTIFIED SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
busbar: if i remove all the URLs, the proxy won't work.
e_aravind:
its used to separate OWA features such as one website not being able to download attachments from OWA, etc while the other allows it.
Nothing in event viewer. Bcoz the proxy works (there is no error), but the proxy is proxied to the wrong website. i know its the wrong website bcos the feature is disabled. on the correct website, it is enabled.
The IE URL is not changed. Since no external URL is populated, there is no redirection but proxy. The IE URL is maintained but I can see that the connection has gone to the wrong website - based on feature disabled and netstat from server.
The question was not answered but I will award points for those who attempted to help.
Thats true, that you should have only one website on eachb CAS.

Next Issue ist, that you have to use different IP Adresses für each site. SiteA can't use same IP segment as SiteB. (see also configuring Active Directory Sites)