Cannot connect to Exchange OWA over Cisco Site to Site VPN


I am unable to access Exchange OWA from a remote office connected to main office via a Cisco site to site VPN.
Exchange 2013 sever is located at main office on a /24 subnet.
Remote office is on a /24 subnet.
Cisco 860 router each end with IPSEC VPN.
Each office has own AD domain, DNS secondary zones for the alternate office are configured at each other office.
I can successfully ping the FQDN of the Exchange server from the remote office and it resolves to the Exchange server's local IP address on the /24 subnet.
I can connect from the remote office to other devices located at the main office via TLS/SSL no problem.
OWA is working fine from main office connecting locally and every where else via Internet.
When I try to open OWA at the remote office I just get a Page cannot be displayed error.
What should I be looking at to resolve this issue?

Thanks in advance...
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.

From the command prompt run the following.  Replace OWA with the email server name.  The trace will stop at the problem network device.

tracert OWA
TRBRAuthor Commented:
The trace completes successfully to the Exchange server from the remote site

Let me know first, thats exactly error that you are gettign while accessing OWA from remote site .

Thank You!
Webinar: What were the top threats in Q2 2018?

Every quarter, the WatchGuard Threat Lab releases an Internet Security Report that describes and analyzes the top threat trends impacting companies around the world. Are you ready to learn more about the top threats of Q2 2018? Register for our Sept. 26th webinar to learn more!

TRBRAuthor Commented:
I just get the standard "This page can't be displayed" in Internet Explorer 10
I can connect from the remote site to web interfaces of other devices at the main site using https no problem.
I think you need to add a NAT exception to the outside interface of the ASA so that it doesn't NAT the exchange server when sending traffic to the remote site through the outside interface.
TRBRAuthor Commented:
I've just rechecked the config of the router and it does look to me that a NAT exemption is in place for the /24 subnet when the destination is the /24 subnet

These are a pair of 800 series routes that were given a basic config with Cisco Configuration Professional
TRBRAuthor Commented:
have implemented an alternate solution for now

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
TRBRAuthor Commented:
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

From novice to tech pro — start learning today.