exchange, IIS, AUTODISCOVER, OWA
we have exchange 2007 server
Right now we have reverse proxy squid server in front of exchange server where OWA URL is configured and set to mail.domain.com/owa squid proxy server directs OWA, active sync traffic to our exchange server
Where we have set the internal url of OWA, active sync which is FQDN of exchange server that is 2k7mail.domain-mail.lan /owa and external URL is null so users get owa url from reverse proxy server
We are putting one load balancer in same place as reverse proxy squid server and we are populating external OWA url in exchange as mail2.domain.com/owa and leaving internal url OWA url as s it is
We want now users to use new load balancer to pick mail2.domain.com/owa which is external url in owa of our CAS server
We have set external and internal dns records for mail2.domain.com/owa
We just tried to test new load balancer But instead it directs us to internal URL of exchange that is 2k7mail.domain-mail.lan /owa which is internal url of exchange server.
Why it is not pulling the external OWA url which is mail2.domain.com/owa
I see autodiscover url is 2k7mail.domain-mail.lan/au
I am getting very confusing answer by following people in earlier replies:
adam brown says: The Internal/External OWA URLs configured in Exchange don't actually do anything functional.
You're probably getting the SCP referral for autodiscover if you're getting a .lan address. To fix that, run this:
get-clientaccessserver | set-clientaccessserver -autodiscoverserviceintern
this will allow outlook to talk to load balancer
then adam says make internal and external owa url the same. then do I need to change autodiscover internal uri? I never got answer
amit another expert says-owa depends upon iis in CAS , so do I need to change redirection in IIS to blank as it is set for fqdn of exchange
if I need to change to blank then do I need to still run autodiscover internal uri ??
Right now we have reverse proxy squid server in front of exchange server where OWA URL is configured and set to mail.domain.com/owa squid proxy server directs OWA, active sync traffic to our exchange server
Where we have set the internal url of OWA, active sync which is FQDN of exchange server that is 2k7mail.domain-mail.lan /owa and external URL is null so users get owa url from reverse proxy server
We are putting one load balancer in same place as reverse proxy squid server and we are populating external OWA url in exchange as mail2.domain.com/owa and leaving internal url OWA url as s it is
We want now users to use new load balancer to pick mail2.domain.com/owa which is external url in owa of our CAS server
We have set external and internal dns records for mail2.domain.com/owa
We just tried to test new load balancer But instead it directs us to internal URL of exchange that is 2k7mail.domain-mail.lan /owa which is internal url of exchange server.
Why it is not pulling the external OWA url which is mail2.domain.com/owa
I see autodiscover url is 2k7mail.domain-mail.lan/au
I am getting very confusing answer by following people in earlier replies:
adam brown says: The Internal/External OWA URLs configured in Exchange don't actually do anything functional.
You're probably getting the SCP referral for autodiscover if you're getting a .lan address. To fix that, run this:
get-clientaccessserver | set-clientaccessserver -autodiscoverserviceintern
this will allow outlook to talk to load balancer
then adam says make internal and external owa url the same. then do I need to change autodiscover internal uri? I never got answer
amit another expert says-owa depends upon iis in CAS , so do I need to change redirection in IIS to blank as it is set for fqdn of exchange
if I need to change to blank then do I need to still run autodiscover internal uri ??
ASKER
yes snapt t load balancer will eliminate squid proxy server, yes both are in same subnet. exchange server is behind load balancer
Ok. Exchange 2007 doesnt use DAG technology. That didnt begin until 2010. In fact 2007s whole concept of load distribution is really old and really bad. So what is the goal you are trying to achieve? Distribute load between 2007 servers?
ASKER
forget it sir, you are not able to understand what I am asking
ASKER
We just tried to test new load balancer But instead it directs us to internal URL of exchange that is 2k7mail.domain-mail.lan /owa which is internal url of exchange server.
Why it is not pulling the external OWA url which is mail2.domain.com/owa
I see autodiscover url is 2k7mail.domain-mail.lan/au
I am getting very confusing answer by following people in earlier replies:
adam brown says: The Internal/External OWA URLs configured in Exchange don't actually do anything functional.
You're probably getting the SCP referral for autodiscover if you're getting a .lan address. To fix that, run this:
get-clientaccessserver | set-clientaccessserver -autodiscoverserviceintern
this will allow outlook to talk to load balancer
then adam says make internal and external owa url the same. then do I need to change autodiscover internal uri? I never got answer
amit another expert says-owa depends upon iis in CAS , so do I need to change redirection in IIS to blank as it is set for fqdn of exchange
if I need to change to blank then do I need to still run autodiscover internal uri ??
Why it is not pulling the external OWA url which is mail2.domain.com/owa
I see autodiscover url is 2k7mail.domain-mail.lan/au
I am getting very confusing answer by following people in earlier replies:
adam brown says: The Internal/External OWA URLs configured in Exchange don't actually do anything functional.
You're probably getting the SCP referral for autodiscover if you're getting a .lan address. To fix that, run this:
get-clientaccessserver | set-clientaccessserver -autodiscoverserviceintern
this will allow outlook to talk to load balancer
then adam says make internal and external owa url the same. then do I need to change autodiscover internal uri? I never got answer
amit another expert says-owa depends upon iis in CAS , so do I need to change redirection in IIS to blank as it is set for fqdn of exchange
if I need to change to blank then do I need to still run autodiscover internal uri ??
Ok. Theres no need to repeat what you posted up above. Please assume Ive read it and I understand it. You are saying forget it but the way exchange is setup is crucial to answering your question. 2007 still allows you set up roles and what I am trying to get at is A) how this is all setup B) Why its setup that way C) What your goal is and D) Finally hopefully an answer.
So back to the question I last asked. What are you trying to accomplish? Please forget the error you are receiving. I get that you have an issue, but what are you trying to accomplish with load balancing 2007 Exchange servers?
So back to the question I last asked. What are you trying to accomplish? Please forget the error you are receiving. I get that you have an issue, but what are you trying to accomplish with load balancing 2007 Exchange servers?
ASKER
we are simply installing load balancer to allow OWA traffic to pass through instead of present squid proxy server
Present squid server has OWA URL as mail.domain.com/owa defined in their config file mail.domain.com/owa which directs traffic to our internal cas server as the squid proxy server is hardcoded to our internal CAS SERVER.
Our internal CAS server has http redirect in iis as our cas server name itself,
in case of squid server where owa traffic passes through
users when open owa it shows mail.dom.com/owa in their browser
but when in case of load balancer where when have exchange vip configured for same internal CASserver , owa page opens and mailbox also opens up but it pulls internal owa url which is on exchange it doesn't pull external owa url which we have configured on exchange that is mail2.domain.com/owa
one expert says change autodiscover internal uri to mail2 .domain.com/owa another expert says blank the space in http redirect in iis
Present squid server has OWA URL as mail.domain.com/owa defined in their config file mail.domain.com/owa which directs traffic to our internal cas server as the squid proxy server is hardcoded to our internal CAS SERVER.
Our internal CAS server has http redirect in iis as our cas server name itself,
in case of squid server where owa traffic passes through
users when open owa it shows mail.dom.com/owa in their browser
but when in case of load balancer where when have exchange vip configured for same internal CASserver , owa page opens and mailbox also opens up but it pulls internal owa url which is on exchange it doesn't pull external owa url which we have configured on exchange that is mail2.domain.com/owa
one expert says change autodiscover internal uri to mail2 .domain.com/owa another expert says blank the space in http redirect in iis
ASKER
the problem is when owa opens it should pull up mail2.domain.com/owa which is configured in external owa url and not go to internal owa url of exchange
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
My only question is if I change the autodiscover internaluri to point to mail2.domain.com will it help
Probably not; No, but it never hurts to have settings set the correct way. So feel free to change all of them to what they are supposed to be, but it will not correct any issues.
ASKER
right now autodiscover internal uri points to exchange server name if I change to external owa url wont it break anything
sorry about that but if we remove the server name in https redirect in iis , will that any way help, as I believe ssl offloading is not enabled on load balancer
sorry about that but if we remove the server name in https redirect in iis , will that any way help, as I believe ssl offloading is not enabled on load balancer
If you have load balancers in the mix then why are you doing the redirects on the Exchange servers? Those should be handled on the load balancers. I'm not sure it will fix the problem, but I believe it will help the way the system operates. I assume there are VIPs on the snapt LBs, if so when you are referring to the URLs, ALL URLs should be pointed at the LB's VIP/s correct? Do you have persistence turned on? If not, it probably should be. Id start with persistence based on source IP first.
ASKER
so when you are referring to the URLs, ALL URLs should be pointed at the LB's VIP/s correct-that means I have to do set-client client access server -autodiscoverinternal uri to load balancer url? am I correct
and not touch https redirect in IIS
and not touch https redirect in IIS
No. Im talking about DNS forward lookup zones. Any domains you are actively using to route mail through need to be pointed at the LB VIP/s.
ASKER
it si already done in forward look up zone it si pointing to load balncer
Again Exchange 2007 is old and load balancing it is difficult. Are you using persistence in your load balanced VIP?
ASKER
sorry but I am not load balancing exchange 2007 but trying to use load balancer to connect to my outlook web access URL which I have defined and populated external OWA URL in exchange,having said when I connect through load balancer does open mail2.domain.com/owa but when I put in user name and passwords it directs me to internal OWA url and not external OWA url that is mail2.domain.com/owa but I do get to open mailbox.
in my IIS of my CAS server under default website-OWA I see my exchange server name is there in http redirection (e2k7dc1.domain-mail.lan) which is also internal owa url in exchange(e2k7dc1.domain-ma
also I see auto discover pointing to exchange server name which is same as internal owa url
so what should I change so that when owa opens it should point to external owa url i.e mail2.domain.com/owa
also one expert suggested to change autodicover internal uri to mail2.domain.com/owa , I don't know how it will help.
we are trying to replace squid proxy server which at present has owa url which users access as we had external owa url was null
we just populated external owa url mail2.domain.com/owa and trying to connect through snapt load balancer.
in my IIS of my CAS server under default website-OWA I see my exchange server name is there in http redirection (e2k7dc1.domain-mail.lan) which is also internal owa url in exchange(e2k7dc1.domain-ma
also I see auto discover pointing to exchange server name which is same as internal owa url
so what should I change so that when owa opens it should point to external owa url i.e mail2.domain.com/owa
also one expert suggested to change autodicover internal uri to mail2.domain.com/owa , I don't know how it will help.
we are trying to replace squid proxy server which at present has owa url which users access as we had external owa url was null
we just populated external owa url mail2.domain.com/owa and trying to connect through snapt load balancer.
We will probably need subnet information in order to piece out the networking properly.