Exchange 2010: internal access to external OWA notworking.

Last exchange issue I swear.Well at least for this client lol.

My remaining issue is that my internal users cannot access webmail from inside the network.
They can however browse to it by https://internalIP/owa
if they try to put in, it just times out.

Any ideas? is this a DNS record issue? If so, what DNS records to do I need to update.
My firewall is allowed all traffic from all trusted zones, external and optional zones, access to the NAT'd address for webmail. OUTSIDE access works absolutely perfect!

Thank you!
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.


There are 2 things you need to setup to get it working -
1. DNS
2. Site Bindings

Lets explain, its very simple -

1. For DNS  -
a)Open up your DNS console and browse to Forward Lookup Zone
b) Create a new zone by the name You can choose default values when creating a new zone in DNS
c) Next right-click on newly created zone and choose "New Host A"
d) Now leave the TOP SPACE blank and in the 3rd row put in the IP address of your server.
e) Having done this you now need to create site bindings in IIS.

2. For Site Bindings -

a) Open up IIS7 mmc console.
b) Browse to Default Web Site
C) On the right hand column click on "Bindings"
d) Click on ADD
e) Type:http, IP Address: All Unassigned (or your server IP), Port: 80, Hostname:
f) All done now. Open up command prompt and type: iisreset

Everything should now work as you want it to :)

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
EZTEKAuthor Commented:
You sir. Are the man. (or woman??)
Thank you very much for a fast response, extremely accurate help.

EZTEKAuthor Commented:
This is what this site is all about. PERFECT!
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

No worries. Man by the way :)

What about HTTPS access to the OWA of Exchange 2010?

This states a way to get http access to webmail but HTTPS requires a certificate to be loaded and doesn't allow you to pick the URL.

Any thoughts?
I have the same problem with when trying to connect to the webmail address internally when using the same internet line as the exchange server. however i can access it by using https://internalIP/owa. (We have 2 internet gateways) If i switch internet gateways on my local PC to the line which the exchange server does not use, i can connect fine. Whats more unusual is after i have sucessfully connected to the webmail after switching internet lines, if i switch back to the previus gateway it now still works. However if i flush the DNS on my local PC it no longer works, which suggest its something relating to DNS.

Any thoughts anyone?
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.