OMA Issues With New Front End Server

We have five Exchange servers in our environment.  Three are in production and hosting mailboxes.  These three are at different locations and each is setup for OWA, OMA, and RPC over HTTPS over their respective internet connections.  We use forms based auth and ssl for OWA and my predecessor setup a second virtual directory called exchange-oma that was setup without SSL  and modified the registry so AcrtiveSync would point to it.

We used to have 4 servers with this exact config but one of our offices closed.  I moved this server and configured it as a front end server.  I turned off forms based auth and require ssl on the three existing production servers.  I can connect through the Front End server just fine for OWA, and RPC over HTTPS no matter what server the user mailbox is on.  However accessing OMA with Activesync does not work.  I receive a 85010014 error on the phones and event id 9175 in the log on the Front End server.

The interesting thing is I setup a new server that is just to host mailboxes.  I duplicated the exchange-oma directory on it and it works.  Any mailbox I put on this server I can access using Activesync, OWA, or rpc over https through the Front End server.  I can't figure out why it works on this new server but won't on any of my existing three production ones.
B0311Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

BusbarSolutions ArchitectCommented:
This error is because of incorrect authentication/SSL settings between the FE and BE, it looks that you have an incorrect setting that has been been inherited and hidden and you cannot figure it out,
0
B0311Author Commented:
Whatever the setting is it's only preventing Activesync from working through the front end server,  it works fine if you point the phone directly to the back end server.
0
BusbarSolutions ArchitectCommented:
this is so normal, since the wrong setting is not on the BE it is on the FE
0
B0311Author Commented:
I had to remove the HKLM\SYSTEM\CurrentControlSet\Services\MasSync\Parameters\ExchangeVDir  key on the front end server.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

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.