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


Use Smartphone for use on wifi network without the need to reconfigure

Published on
40,036 Points
17 Endorsements
Last Modified:
Community Pick


You have a bunch of iPhone users that all successfully synchronise with your exchange server from outside of your network using the mobile telephone network.  However, when you try to do the same using your internal wireless network synchronisation fails.

The reason for this is because your iPhones are configured to use the externally published exchange servers, for example owa.domainname.com which in turn is configured to use the external IP address of your router/firewall.

Most, if not all business class firewalls/routers are designed to block this type of looping from internal devices.


The way to resolve this is to configure your internal network to allow access to owa.domainname.com using an internal IP address.

The easiest way to do this is using your internal DNS servers by creating a forward lookup zone called owa.domainname.com and then creating a blank A record that is configured to use your Exchange servers internal IP address.

Using the DNS Console (Start> Administrative Tools> DNS) navigate to the Forward Lookup Zones, right click and select New Zone.  You will then be presented with the New Zone wizard.

Using the wizard select the following options:
Primary Zone
Store the zone in Active Directory
To all DNS Servers in the domain
Zone Name: owa.domainname.com
Allow only secure dynamic updates
Once the new zone has been created right click the zone and select New Host (A or AAAA).  In the dialogue box leave the name blank and in the IP Address section enter the internal IP address of the Exchange server.

If you are using multiple Exchange Servers then this IP address must be the Front End Server (if using Exchange 2003) or the Client Access Server (if using Exchange 2007 or 2010)


We can easily save the inclusive minutes of our data plans and save money by using our internal wireless networks to allow mobile devices to use our internal exchange servers (or any other service) without the need to reconfigure the mobile device.

This guide provides a simple solution to what can be an annoyance for your end users.

Written by Glen Knight (demazter) as part of a series of how-to articles.
Author:Glen Knight
  • 2
  • 2
  • 2
  • +6
LVL 20

Expert Comment

this is also true for other smartphones
LVL 74

Author Comment

by:Glen Knight
Yes it is.

Perhaps a review of the title :)

Expert Comment

The article resolved my issue.

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Expert Comment

how do I award all the points to you?
LVL 76

Expert Comment

by:Alan Hardisty
Click on the Vote button - then Demazter will get some points.  You can't award question points to an article - but accepting the answer to the comment including the article (as you have) will also earn him some more points.


Expert Comment

How would you do this in a two NIC setup where the wireless AP is on the external connection?

Expert Comment


you said we need to create a forward lookup zone that’s named owa.domainname.com. should i use this even though we use mail.domainname.com? I’m just a bit confused about that. thanks in advance.



Expert Comment

Dematzer was using that as an example, Alex. If you use mail.* use that in DNS to match your current setup.


Expert Comment

by:Houston Blancett
There is already a forward looking A name with nothing but the internal server IP address. The domain is mydomain.local and we use mail.mydomain.org for email. Any suggestions?

Expert Comment

by:Houston Blancett
Sorry....posted to wrong open window.

Expert Comment

thanks for the info jaredr80. not sure if anyone can provide more insight on this but here's some additional info. i added created the forward lookup zone and added the a record with the internal ip of the exchange server. i was able to send emails internally from the iphone and outlook, but emails to external addresses failed from the iphone and outlook. the messages just built up in the queue. so i deleted the dns entry and mail started to flow again. we use postini for spam and i think this is what may be causing this issue. the send connector for postini is mail.companyname.com. should this be the name of the servername.domain.local?

Expert Comment

And for the same scenario
But with a Dyndns ?  


That's not work .

Featured Post

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.

Join & Write a Comment

Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Please check the video also in regards to recovery of deleted emails from office 365 admin center and through the MFCMAPI tool. I have mentioned each and every step with the proper steps that need to be taken care of.

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month