We help IT Professionals succeed at work.

Iphone Can't get Exchange mail on LAN but ok on 3G.

Hello,
We have a exchange 2003 sevrer and a OWA 2003 server as well.
When the domain was installed whoever installed it named it mycompany.com
Our exchange server is owa.mycompany.com.
This is the setting people put in their iphone to get exhcnage mail when they are on 3g. When they come to work and connect to our internal wifi, the mail server does not connect. So i tried adding a different dns record called owa1.mycompany.com and pointed it to the outside public address. The phones still do not like this and will not connect when they are in our wifi zone.
I know calling the domain the same thing as our websites, email servers etcc is wrong but i did not set it and changing it is not a option.
Thanks in advance.
Comment
Watch Question

Awarded 2009
Top Expert 2010

Commented:
This is because the hostname will be different on the WIFI.

Create a new forward lookup zone on your internal DNS that is the same as your external URL then create a blank A record in this zone and give it your internal IP address of your exchange server.

Author

Commented:
i already added a host record for owa1.mycomapny.com pointing to external ip. Is that what you mean? I dont understand the blank one it looks like there are several blank ones there that just referecne the servers?

Commented:
No, demazter is saying to add a DNS record in your internal DNS for owa.mycompany.com that points to the internal IP address of your OWA server (probably a front-end server)

This way when iPhones are on the WLAN they will contact the server internally instead of going out the router and trying to come back in. A lot of firewalls and routers do not like/permit this.

so as you are saying your internal DNS is the same as your external DNS then all you should need to do is add the owa A Record and point it to your internal IP address of your OWA server.

Commented:
You need the host record to your internal DNS Serveres for owa1.mycompany.com to point to the INTERNAL ip address of the client access server (exchange server)..

Commented:
just use owa.mycompany.com internal so then people don't have to keep reconfiguring their iPhones...
Awarded 2009
Top Expert 2010

Commented:
Thanks meganuk, vamatic the orward lookup zone needs to be the same name you use outside of your network as advised in my first post.  Otherwise you will need to keep reconfiguring the iPhone.
Awarded 2009
Top Expert 2010

Commented:
Make sure you create a forward lookuo zone for owa.comapny.com otherwise if you just create a zone for company.com you will have to setup all your external records in the internal DNS.

Creating an A record in your existing zone will not help either.

Author

Commented:
Ok, tomorrow when i get back to work i will create a new zone and then add the host record for owa.mycompany.com??? Thanks for all the posts so far.

Author

Commented:
do i create the blank host record for the actual exchange server or my owa server?
Awarded 2009
Top Expert 2010

Commented:
the Exchange server, it needs to have the internal IP address of your Exchange Server.

Author

Commented:
still not working i am going to change the host record to the owa front end server?
Awarded 2009
Top Expert 2010
Commented:
OK, let me try and explain this again.

If when not connected to the wifi the servername you use on the iphone is:

owa.domainname.com then this will be an A record in your external DNS pointing to the external IP address of the Exchange Server.

owa.domainname.com above is just an example, you will need to check your phone for the exact servername.

So on your internal DNS, you need to create a forward lookup zone that is the same as the above, so if the above is owa.domainname.com you create a forward lookup zone for owa.domainname.com then you create a blank A record and point it to the INTERNAL IP address of your Exchange Server.

It's pointless pointing it to the external IP address because this will not work, this is why it's not working at the moment because most routers are designed to block these sorts of loops.

Author

Commented:
Worked great, needed to be pointed to my OWA front end server not the actual exchange server.