SBS 2003 R2 Access for OWA over iPad's & Iphones

Posted on 2010-11-16
Last Modified: 2012-05-10
My current setup is as follows:

1 x SBS 2003 R2 server allowing OWA - this works flawlessly with outlook + IE
Several Ipad's & Iphones which will connect to the OWA mailbox when I use server.domainname in the config.

My problem happens when the user returns to where the server is placed, when ever they attempt to view their email on the same network as the server it fails to resolve.
The only solution I've found so far is to create a seperate entry on the iphone for server.domain.local (not the normal domain)  This is turn works a treat when local, BUT obiously not when roaming.

Is there an DNS / routing setup wrong somewhere which would allow server.domainname to work locally instead of manually changing setting to .local ?
I've set this up on Exchange 2007 and it all works fine (at a seperate location), SBS is just casuing me so much grief, please help.
Question by:thegiantsmurf
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 15

Expert Comment

ID: 34144152
This will not be possible for DNS to resolve this.
LVL 71

Accepted Solution

Chris Dent earned 500 total points
ID: 34144192
I don't see why not.

From the sounds of it they're connecting to your LAN? Then they're expecting to use "server.domainnanme", which I assume resolves to the public IP Address of the server?

If that is the case you have two choices:

1. Fix up NAT Loopback on your router so the public IP can be used for your server. This depends on the firewall / router and may be as simple as a tickbox, or a lot more complex.


2. Create a new Forward Lookup Zone in DNS as follows:

a. Open the DNS Console
b. Select Forward Lookup Zones
c. Right click and select New Zone
d. Select Primary and "Store this zone in Active Directory"
e. Name the zone "server.domainname". Note that inclusion of "server" here is deliberate
f. Disable Dynamic Update for the zone
g. Finish
h. Select the newly created zone
i. Right click and select New Host (A) record
j. Leave the Name blank and enter the Internal IP Address of the server

All done. I have no idea how you would flush the DNS cache on those devices. Reboot? :) Once done, they should be able to connect to server.domainname; using the same name in either scenario.


LVL 23

Expert Comment

ID: 34144357
But why you are not using ActiveSync?
Comparison of Amazon Drive, Google Drive, OneDrive

What is Best for Backup: Amazon Drive, Google Drive or MS OneDrive? In this free whitepaper we look at their performance, pricing, and platform availability to help you decide which cloud drive is right for your situation. Download and read the results of our testing for free!


Author Comment

ID: 34144679
I've done the forward lookup and reset the server later today.
I just need to kick the user's off
LVL 71

Expert Comment

by:Chris Dent
ID: 34144899

You shouldn't need to reset the server, it's the clients (the iPads and stuff) that'll remember the old address, they're the ones that need to forget. If all else fails they will eventually (anything from an hour to a day if they're switched on all the time).


Expert Comment

ID: 34149945
The way I read your problem is that when the iphone/ipad tries to sync their email while they are in the office, it does not work, but when they are out of the office it will work fine?

I'm assuming you have a WAP connected to the internal network and the iphone/ipad are connecting to this WAP while in the office?

If so, you need to create a new forward lookup zone in DNS on the SBS server.

Create the zone as (or whatever the domain is that the devices use).

Then add a new A record with the prefix that you use on the devices, so if you use the servername of on the iphones/ipad then create a new A record of mail.

Then have the new A record point to the INTERNAL ip address of the SBS server.

NOTE - this will now mean that everyone on the trusted network at the office, will resolve DNS to this new domain, so if you have existing WWW records, or anything else, like FTP or other A records, you will need to manually enter these in as well, otherwise it will break for internal office uses.

This should then mean that when the devices are in the office, DNS should resolve to the internal IP address of the server and when they are out of range of the WAP, they will resolve to your external IP address from your ISP.

Hope this helps.
LVL 71

Expert Comment

by:Chris Dent
ID: 34149976
> so if you have existing WWW records, or anything else, like FTP or other A records, you will need to manually enter these
> in as well, otherwise it will break for internal office uses

The method I outlined above avoids the need to do that.


Author Comment

ID: 34150021
Chris' solution seems to be working, but the update to the devices is very slow,
Is this normal - 20 mins to download an in box to an iPad for example ?

Does anyone have any data on this?

LVL 71

Expert Comment

by:Chris Dent
ID: 34150069
Hmm it should be fast with it being on the local network. All this does is provide the device with the internal IP of the server instead of the external IP.

It's possible it's still caching something of the old connection, but I don't really have any experience with iPad / iPhone to say what the best step would be there.


Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit If you want to manage em…

691 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question