Make external IP address accessable from internal network

15 pts.
DNS management
External IP Addresses
IP Routing
Microsoft Exchange
Microsoft Exchange ActiveSync
Mobile enterprise applications
Sonicwall NSA 3500
Hi, Out users have iPhones which receive their emails via Exchange Active Sync. To work correctly they need to be able to access the exchange server using the same IP address internally and externally. Currently I have mapped the DNS name to our internall address while in our network. This worked fine until iOS 4 came out. How can I get our Sonicwall NSA 3500 to allow users on the internal network access the mail server using the same IP address as our external users?

Software/Hardware used:
Sonicwall NSA 3500

Answer Wiki

Thanks. We'll let you know when a new response is added.

If I read your post correctly, I’m going to assume you want all users (internal and external) to utilize the front-end server (OWA) public server which utilize RPC over HTTPS.

<a href=”https://OWA.DOMAIN.COM”>https://OWA.DOMAIN.COM</a>

The sonic firewall is not involved as long as the NAT for the OWA server is setup. Have all Outlook users internally even to have the option Checked to utilize RPC over https within the Outlook Mail Setup Configuration.

Discuss This Question: 2  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • RGunther
    I am assuming you have setup wireless on the iPhones and that is whats causing the issue? The way my company has this setup is we use our Domain Controler as the DNS for internal traffic and then have seperate external falling DNS Servers. This way the internal wireless will talk to the Domain Controllers and get the internal IP Address. When you are outside your network the phones should pick up the external IP address and connect appropriately. As for getting your firewall to allow inside users to access a public NAT will be difficult. Most of the firewalls I have worked with will not like that at all. An option is to put the Exchange server on a different port and give it a static public ip instead of a private with a public NATed to it. Ryan Gunther
    650 pointsBadges:
  • Paulr62
    RGunther, I have them on the wireless on the internal network. The issue is point 2 on the following KB article I agree that it is going to be an issue getting it working.
    15 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: