Trying to publish Exchange 2010 OWA on TMG

I am attempting to publish Exchange 2010 client access externally using TMG 2010 and im hitting a brick wall

The environment

1 x TMG
2008 R2 VM
1x DMZ Nic with IP from DMZ subnet, Default Gateway set inc DNS
1x LAN Nic with IP from LAN subnet, Default Gateway not set, no DNS
Routing table updated to allow routing to LAN subnet and DNS resolves internal server names and

2 x Exchange 2010 multi-role servers (SP3 ru10)
2008 R2 VM's

TMG Config
Installed as an Edge Firewall

I pretty much followed this article to the tee - cross referencing other articles on the web

Cert installed and valid

Web listener created requiring SSL, listening on the External network, HTML Form Auth & SSO to domain.local

Web Farm created and added by host name - Test run and seems OK
Outlook Web App rule created (i will create Activesync and Outlook Anywhere later) - published to the farm, requires SSL, set to, Authenticated users only

When this is tested from an external source i either get page cannot be displayed or err_tunnel_connection_failed dependant on browser

When i look at the TMG logs i see the following

two initiated HTTPS connections from External to local host followed by two Closed connections with the error - A connection was abortively closed after one of the peers sent an RST packet

Everything looks OK from within TMG, and all the tests/check paths come back successfull - I can browse to OWA directly from the TMG

Any Idea's please
StuartTechnical Architect - CloudAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

StuartTechnical Architect - CloudAuthor Commented:
I tested this from another server within the DMZ and it worked, I then went over the network config again and it appears the DG was incorrect on the DMZ NIC. Changed to correct IP and everything works!

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
StuartTechnical Architect - CloudAuthor 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
Microsoft Forefront ISA Server

From novice to tech pro — start learning today.