The next procedure is to create a Hosts file entry on the ISA Server 2004 firewall computer so it resolves the name that you specified for your internal Web mail server to the IP address of the Exchange server that is on the internal network.
You could also use a split DNS infrastructure for this purpose. However a Hosts file entry is easier to create. On a production network, you would create a split DNS infrastructure so the ISA Server 2004 firewall would resolve the fully qualified domain name (FQDN) of the OWA Web site to the IP address that the Exchange Server uses on the internal network.
In Notepad, save the changes to the file, and then close Notepad.
Setting the ISA Server 2004 Idle Session Timeout
In this procedure, you will modify the idle session timeout to accommodate the time that is required for the direct push technology to successfully function.
For more information about modifying the idle session timeout time, see the "Best Practice: Configuring Your Firewall for Optimal Direct Push Performance" section in Best Practices for Deploying a Mobile Messaging Solution.
To set the ISA Server 2004 idle session timeout to 1800 seconds
3. From the list of folders, expand the Web Listeners node, and then view the Properties of the appropriate Web Listener.
4. Select the Preferences tab, and then click the Advanced… button.
5. Modify the value for Connection Timeoutfrom the default 120 seconds (2 minutes) to 1800 seconds (30 minutes).
6. Click OK twice to accept the change.
7. Click Apply to make these changes.
Testing OWA and Exchange ActiveSync
After you complete the configuration, you should test the following features that you configured:
Test OWA (optional).
Test Exchange ActiveSync.
An external client mobile device can access the OWA server as long as it can resolve a FQDN to the external IP address of the ISA server. This resolution is usually achieved by registering a public Internet domain name with a public DNS server that maps the Web site name to the external IP address of the ISA Server.
If you have set up OWA according to the instructions in the Exchange Server 2003 Client Access Guide at http://go.microsoft.com/fwlink/?LinkId=62628, you can test it by using the following process.
To test the deployment in a lab environment, specify the Web site host name resolution information by using Notepad in the client mobile device hosts file that is located under the following path: \system32\drivers\etc\hosts in the Windows installation directory.
To test OWA (if installed)
1. To connect to the OWA Web site from the external client mobile device, type the Web address that you specified during setup. Be certain to specify https in the URL.
2. When you connect, you should see a logon page that requests credentials and the session type (public or private). Provide this information so you can access your mailbox.
3. If you have set time-outs or blocked attachments, test those features by leaving the browser inactive for a period of time and then trying to access mail, and by trying to open or save attachments.
Testing Exchange ActiveSync
You can configure a mobile device to connect to your Exchange server by using Exchange ActiveSync, and to be sure that ISA Server 2004 and Exchange ActiveSync are working properly.
As an alternative, you can test Exchange ActiveSync by using Internet Explorer.
To test Exchange ActiveSync by using Internet Explorer
1. Open Internet Explorer.
2. In the Address bar, type https://published_server_name/Microsoft-Server-Activesync, where published_server_name is the published name of your OWA server (the name your end users will type).
3. Type the user name and information that you want to authenticate.
If you receive one of the following error messages: Error 501/505 "Not implemented" or "Not supported", ISA Server 2004 and Exchange ActiveSync are working together properly.