Exchange 2010 Proxy not working properly for OWA

We have an Exchange 2010/2007 environment. Out internet facing site has the 2010 CAS/HUB server which answers to https://owa.domain.com/owa and a 2010 CAS/HUB/Mailbox server as well as a legacy 2007 CAS/HUB and CAS/HUB/Mailbox server in it. It works fine for all exchange servers (2010 and 2007) in that site.

Our other site (we'll call it site2) consists of a 2010 CAS/HUB/Mailbox server and a legacy 2007 CAS/HUB/Mailbox server. Basically, when an internal 2010 user tries to connect to the https://owa.domain.com/owa, it proxies to the server (site2-2010-exchange.domain.com/owa) but it appends /ping.owa to the end of the url. So instead of HTTPS://site2-2010-exchange.domain.com/owa, it returns https://site2-2010-exchange.domain.com/owa/ping.owa which gives a 404 error.

If I manually remove the ping.owa, it works fine. That is not a solution for us though. I need to know why it is doing this and correct it so when we move the rest of users to 2010, they won't have this issue. The current users on 2007 do not have this issue. It redirects to the https://site2-2007-server.domain.com/owa with no issue.

Anyone seen this before. Having trouble finding relevant articles regarding this online.
stmadminAsked:
Who is Participating?
 
Ben HartConnect With a Mentor Commented:
try removing Form-based Auth via EMC-Server Config-Client Access-Site2 server-Outlook Web App, Authentication tab.  then restart IIS

Also make sure your IP's in both v4 and v6, are bound to the default website
0
 
Ben HartCommented:
Make sure the auth method on teh OWA virtual directory in Site1 is Windows-integrated
Set the ExternalURL to $Null on site2
Make sure InternalURL is teh FQDN of site2's exchange server.
0
 
Ben HartCommented:
Also post your results to: get-owavirtualdirectory <servername>\owa* | FL Identity,*auth*
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
stmadminAuthor Commented:
get-owavirtualdirectory stm0exmb01\owa* | FL Identity,*auth*

Identity                      : Site2-2010-exchange\owa (Default Web Site)
ClientAuthCleanupLevel        : High
InternalAuthenticationMethods : {Basic, Fba, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
ExternalAuthenticationMethods : {Fba}
0
 
stmadminAuthor Commented:
Identity                      : Site1-2010-exchange\owa (Default Web Site)
ClientAuthCleanupLevel        : High
InternalAuthenticationMethods : {Basic, Fba, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
ExternalAuthenticationMethods : {Fba}
0
 
Ben HartCommented:
So WindowsIntegrated was already enabled yes?
0
 
stmadminAuthor Commented:
Yes, I haven't changed anything yet.
0
 
Ben HartCommented:
So what what about the External and Internal URL variables?
0
 
stmadminAuthor Commented:
Also, ExternalURL is already $null and internal url is correct as well.
(https://site2-2010-server.domain.com/owa)
0
 
Ben HartCommented:
Also did you do any configuration changes to any of the virtual directories using IIS or via ESM?
0
 
stmadminAuthor Commented:
Oddly enough, the https bindings were blank. I forced it to use all available addresses. I have a guy out there at that site checking it now. If it still fails, then I will remove FBA and make it integrated and basic only.
0
 
Ben HartCommented:
You can also try recreating your Virtual Directories.. easy enough from the Console.
0
 
stmadminAuthor Commented:
Removing FBA did it. Thanks a lot man. ubadmin = ubdaman

Appreciate it.
0
 
stmadminAuthor Commented:
Excellent, fast, concise and on the money. Awesome EE member.
0
 
Ben HartCommented:
Much obliged! Glad your working now.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.