asked on

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.

Ben Hart

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.

Ben Hart

Also post your results to: get-owavirtualdirectory <servername>\owa* | FL Identity,*auth*

stmadmin

ASKER

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}

stmadmin

ASKER

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}

Ben Hart

So WindowsIntegrated was already enabled yes?

stmadmin

ASKER

Yes, I haven't changed anything yet.

Ben Hart

So what what about the External and Internal URL variables?

stmadmin

ASKER

Also, ExternalURL is already $null and internal url is correct as well.
(https://site2-2010-server.domain.com/owa)

Ben Hart

Also did you do any configuration changes to any of the virtual directories using IIS or via ESM?

ASKER CERTIFIED SOLUTION

Ben Hart

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

stmadmin

ASKER

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.

Ben Hart

You can also try recreating your Virtual Directories.. easy enough from the Console.

stmadmin

ASKER

Removing FBA did it. Thanks a lot man. ubadmin = ubdaman

Appreciate it.

stmadmin

ASKER

Excellent, fast, concise and on the money. Awesome EE member.

Ben Hart

Much obliged! Glad your working now.