ISA Server 2006, ISA Server 2004 & client connections from Outlook 2003 to Exchange Server 2003

How to configure ISA Server 2006, ISA Server 2004, or Microsoft Forefront Threat Management Gateway, Medium Business Edition, to allow for RPC over HTTP client connections from Outlook 2003 to Exchange Server 2003

This step-by-step article describes how to configure Microsoft Internet Security and Acceleration (ISA) Server 2006, ISA Server 2004, or Microsoft Forefront Threat Management Gateway, Medium Business Edition, so that Remote Procedure Call (RPC) over HTTP client connections can pass from Microsoft Office Outlook 2003 to Microsoft Exchange Server 2003. The RPC over HTTP feature makes it possible for remote client computers that are running Microsoft Windows Server 2003, Microsoft Windows XP Service Pack 1, or later versions of Microsoft Windows, to connect to an Exchange server without the need for a virtual private network (VPN) connection. You can configure the RPC over HTTP traffic to be sent through an ISA Server-based or Forefront Threat Management Gateway-based computer on your network by creating a Secure Sockets Layer (SSL) Web Publishing rule on the ISA Server-based computer.

Note You must confirm that RPC over HTTP traffic is functioning correctly on the Exchange server before you configure RPC over HTTP traffic to pass through the ISA Server-based computer. For more information about how to deploy Exchange Server 2003 RPC over HTTP, click the following article numbers to view the articles in the Microsoft Knowledge Base:

840255  (http://support.microsoft.com/kb/840255/ ) The "Exchange Server 2003 RPC over HTTP deployment scenarios" guide is available

833401  (http://support.microsoft.com/kb/833401/ ) How to configure RPC over HTTP in Exchange Server 2003

827330  (http://support.microsoft.com/kb/827330/ ) How to troubleshoot client RPC over HTTP connection issues in Office Outlook 2003

For more information about Exchange Server 2003 RPC over HTTP, visit the following Microsoft Web sites:

• Exchange Server 2003 RPC over HTTP Deployment Scenarios
  http://www.microsoft.com/downloads/details.aspx?FamilyID=f7d2d6e5-579f-4779-a6b8-7ef931ec02a5&DisplayLang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=f7d2d6e5-579f-4779-a6b8-7ef931ec02a5&DisplayLang=en)
• Remote Procedure Calls Using RPC over HTTP
  http://msdn2.microsoft.com/en-us/library/aa375384.aspx (http://msdn2.microsoft.com/en-us/library/aa375384.aspx)
• Configuring Outlook 2003 for RPC Over HTTP
  http://office.microsoft.com/en-us/ork2003/HA011402731033.aspx (http://office.microsoft.com/en-us/ork2003/HA011402731033.aspx)

Back to the top

Export a Web server certificate from the IIS-based computer that hosts the RPC proxy site

1. On the Web server computer, start Microsoft Internet Information Services (IIS) Manager. To do this, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. Expand the computer node, expand Web Sites, right-click the Web site that you want to export the certificate from, and then click Properties.
3. Click the Directory Security tab, and then click View Certificate.
4. In the properties of the certificate, make sure that the certificate says "You have a private key that corresponds to this certificate."
5. Click the Details tab, click Issuer, and then click Copy to File.
6. Click Next, click Yes, export the private key, and then click Next.
7. In the Export File Format dialog box, click Personal Information Exchange – PKCS #12 (.PFX).
8. Click to select the Include all certificate in the certification path if possible check box.
9. Make sure that the Enable strong protection (requires IE 5.0, NT 4.0 SP4 or above) check box and the Delete the private key if the export is successful check box are cleared.
10. On the Password page, type a password, and then confirm the password.
11. On the File to Export page, type the location where you want to save the exported certificate, and then click Next. For example, type c:\webcert.pfx, and then click Next.
12. On the Completing the Certificate Export Wizard page, click Finish.
13. When the Certificate Export Wizard dialog box informs you that the export was successful, click OK
14. Click OK to close the Default Web Site Properties dialog box.

Back to the top

On the ISA Server or Forefront Threat Management Gateway computer, import the Web server certificate from the IIS-based computer that hosts the RPC proxy site, and then install the certificate

1. On the ISA Server computer, click Start, click Run, type mmc in the Open box, and then click OK.
2. On the File menu, click Add/Remove Snap-in, click Add, and then click Certificates.
3. Click Add, click Computer account, click Next, click Finish, click Close, and then click OK.
4. Expand Certificates (Local Computer), right-click Personal, point to All Tasks, and then click Import.
5. Click Next, click the certificate file that you want to import, and then click Next.
6. In the Password box, type the password to decrypt the private key, click to select the Mark this key as exportable check box, and then click Next.
7. Leave the Place all certificates in the following store option selected, make sure that Personal is selected in the Certificate store box, click Next, and then click Finish.
8. When you receive the following message, click OK:
   The import was successful.
9. Expand Personal, and then click Certificates.
10. Make sure that the certificate with the name of the Web server computer appears in the right pane. You might have to update the display before this certificate appears.
11. Right-click the Web server certificate, and then click Properties.
12. If the Enable all purposes for this certificate option is selected, click Enable only the following purposes, click Apply, and then click OK.

Back to the top

Create a new Web publishing rule on the ISA Server computer

Note If you already have a Microsoft Outlook Web Access (OWA) Web publishing rule and the OWA server is also the RPC proxy server, you can add /RPC/* to the path instead of creating a new rule.

ISA Server 2006

1. Start the ISA Server/Threat Management Gateway Management tool.
2. Expand name of ISA Server 2006 or Threat Management Gateway computer.
3. Right-click Firewall Policy, point to New, and then click Exchange Web Client Access Publishing Rule.
4. In the Exchange Publishing rule name box of the New Exchange Publishing Rule Wizard, type a descriptive name for the new publishing rule, and then click Next.
5. In the Exchange version list, click Exchange Server 2003, click to select the Outlook RPC/HTTP(s) check box, and then click to clear the following check boxes:
   • Outlook Web Access
   • Outlook Mobile Access
   • Exchange ActiveSync
   Click Next.
6. Leave the default Publish a single Web site or load balancer option selected, and then click Next.
7. Click Use SSL to connect to the published Web server or server farm, and then click Next.
8. In the Internal site name box, type the DNS name that internal users use to access the Web site. For example, type alias.example.com.
   
   Note The internal name must match the name that appears on the server certificate that is installed on the internal Web server.
9. Click to select the Use a computer name or IP address to connect to the published server check box, type the name of the computer or the IP address of the computer that hosts the RPC Proxy in the Computer name or IP address box, and then click Next.
10. In the Accept requests for list, click This domain name (type below), type the DNS name that external users must use to access the Web server. For example, type mail.example.com. In this domain name, replace mail with the publicly-accessible alias that you use for the Web site.
11. Click Next.
12. On the Select Web Listener page, click New.
13. On the Welcome to the New Web Listener Wizard page, type a descriptive name in the Web listener name box, and then click Next.
14. Leave the default Require SSL secured connections with clients option selected, and then click Next.
15. On the Web Listener IP Addresses page, click to select the External check box, and then click Next.
16. Click Select Certificate, click the server certificate that you previously imported, and then click Select.
    
    Note Make sure that the name on the certificate matches the name that is used by Office Outlook 2003 clients to connect. If the certificate does not match, the Office Outlook 2003 connection does not work, the Office Outlook 2003 user does not receive a warning, and the user cannot continue.
17. Click Next.
18. In the Select how clients will provide credentials to ISA Server/Threat Management Gateway list, click HTTP Form Authentication, and then click Next.
    
    Note For more information about the authentication methods that are available, click the authentication settings link.
19. If you want to enable the Single Sign On functionality, click to select the Enable SSO for Web sites published with this Web listener check box, and then type the Single Sign On domain in the SSO domain name box. For example. type .example.com..
    
    Note In this example, note the period (dot) that appears before "example.com."
20. Click Next. Review the settings on the Completing the New Web Listener Wizard page, and then click Finish.
21. If you configured a different authentication method in step 18, examine the value of the Require all users to authenticate check box for this Web listener. To do this, follow these steps:
    • On the Select Web Listener page, click Edit.
    • Click the Authentication tab, and then click Advanced.
    • If the Require all users to authenticate check box is selected on the Web listener, you must reconfigure the Web listener to use basic authentication.
    • Click OK two times.
22. On the Select Web Listener page, click Next.
23. In the Select the method used by ISA Server/Threat Management Gateway to authenticate to the published Web server list, click Basic authentication, and then click Next.
24. On the User Sets page, leave the All Authenticated Users user set in the This rule applies to requests from the following user sets box, click Next, and then click Finish. For more information about what to do if you are not using the default settings in the HTTP filter configuration, click the following article number to view the article in the Microsoft Knowledge Base:
    823175  (http://support.microsoft.com/kb/823175/ ) Fine-tuning and known issues when you use the Urlscan utility in an Exchange 2003 environment
    For more information about HTTP filtering, visit the following Microsoft Web site:
    http://technet.microsoft.com/en-us/library/cc302627.aspx (http://technet.microsoft.com/en-us/library/cc302627.aspx)
25. Click Apply to apply the changes to the firewall policy, and then click OK.

ISA Server 2004

1. Start the ISA Server Management tool.
2. Expand name of your ISA Server 2004-based computer.
3. Right-click Firewall Policy, point to New, and then click Web Server Publishing Rule.
4. Type a descriptive name for the new server publishing rule, and then click Next.
5. If the Allow option is not selected, click Allow, and then click Next.
6. Under Computer name or IP address, type the name of the computer or the IP address of the computer that hosts the RPC Proxy, type the path of the file or folder you want to publish in the Path box, and then click Next.
7. Under Accept requests for, you can configure the rule to accept all requests, or only to accept requests for a specific domain name.
8. Type the domain name in the Public name box, and then click Next. For example, type host header name that you assigned to the Web site.domain name.com, and then click Next.
9. On the Select Web Listener page, click New.
10. On the Welcome to New Web Listener Wizard page, type a descriptive name in the Web listener name box, and then click Next.
11. On the IP Addresses page, click to select the External check box, and then click Next.
12. On the Port Specification page, click to select the Enable SSL check box, and then click Select.
13. Click the server certificate that you previously created, and then click OK.
    
    Note Make sure that the name on the certificate matches the name that is used by Office Outlook 2003 clients to connect. If the certificate does not match, the Office Outlook 2003 connection does not work, the Office Outlook 2003 user does not receive a warning, and the user cannot continue.
14. Click Next, and then click Finish.
15. On the Select Web listener name page, click Edit.
16. Click the Preferences tab, and then click Authentication.
17. If the Require all users to authenticate check box is selected on the Web listener, you must reconfigure the Web listener to use basic authentication.
18. Click OK two times.
19. On the Select Web Listener page, click Next.
20. On the User Sets page, click All Users, click Next, and then click Finish. For more information about what to do if you are not using the default settings in the HTTP filter configuration, click the following article number to view the article in the Microsoft Knowledge Base:
    823175  (http://support.microsoft.com/kb/823175/ ) Fine-tuning and known issues when you use the Urlscan utility in an Exchange 2003 environment
    For more information about HTTP filtering, visit the following Microsoft Web site:
    http://technet.microsoft.com/en-us/library/cc302627.aspx (http://technet.microsoft.com/en-us/library/cc302627.aspx)

Back to the top

Troubleshooting

• Make sure that RPC over HTTP traffic is functioning correctly internally. You must allow access from ISA Server or from Threat Management Gateway to the Web server that hosts the RPC proxy before you can test traffic from ISA Server or from Threat Management Gateway. If ISA Server or Threat Management Gateway is configured as an Edge Firewall and the RPC proxy is located on the internal network, you must have either of the following rules:
  • A rule that allows SSL from the Localhost object to the Internal network.
  • A rule that allows all IP traffic from the Localhost object to the Internal network.
  To test the RPC over HTTP traffic, type https://domain name/rpc in a Web browser, and then press ENTER. If you receive the following warning message, click OK:
  You are about to view pages over a secure connection.
  
  Any information you exchange with this site cannot be viewed by anyone else on the Web.
  If you receive a message that states that the certificate was issued by a company that you have not chosen to trust, make sure that the client computer trusts the root certification authority (CA) that issued the certificate. Typically, you receive this message when you do not configure the server to use a third-party certificate.
  
  When you are prompted for your credentials, type your user name in the Universal Naming Convention (UNC) format, type your password, and then click OK. For example, type your user name in the domain\user name format , and then click OK.
  
  The following error message is the expected behavior and indicates that both the server and the client are correctly configured:
  The page cannot be displayed HTTP Error 403.2 - Forbidden: Read access is denied. Internet Information Services (IIS)
• If you have Windows Server 2003 Service Pack 1 (SP1) installed, you are prompted to enter your credentials three times instead of one time. After you enter your credentials for the third time and then click OK, you receive the following error message:
  You are not authorized to view this page
  You do not have permission to view this directory or page due to the access control list (ACL) that is configured for this resource on the Web server.
  
  HTTP Error 401.3 - Unauthorized: Access is denied due to an ACL set on the requested resource.
  Internet Information Services (IIS)
  This error message is the expected behavior. The error message indicates that the RPC virtual directory on the server is correctly configured.
  
  Alternatively, you can use the Web browser to locate the Rpcproxy.dll file that is hosted in the RPC virtual directory. To do this, follow these steps:
  1. On the client computer, start Microsoft Internet Explorer, type the URL of the Rpcproxy.dll file that is hosted in the RPC virtual directory in the Address list, and then click Go.
     
     For example, type https://mail.contoso.com/rpc/rpcproxy.dll, and then click Go.
  2. When you are prompted for credentials, type a user name in the UNC format (domain\user_name), type a password, and then click OK.
  You see a blank page in the Web browser together with a lock icon in the Internet Explorer status bar. The lock icon signifies that you have successfully established a secured (SSL) connection to the server. This behavior indicates that the RPC virtual directory is configured correctly on the server.
• If you use Web publishing and the domain name is the same on the internal network and the external network, it is a good idea to confirm that the ISA Server or Threat Management Gateway computer can successfully resolve all the names that are used in the publishing rule to the RPC proxy server. If all the names are not resolved successfully, you can change the hosts file on the ISA Server or Threat Management Gateway computer.
• If a remote user is prompted for logon credentials multiple times, the remote user may be typing credentials in the wrong format. Remote users must use the domain name\user name format.
• You can verify the RPC over HTTP connection to the computer that is running Exchange. To do this, follow these steps:
  1. Click Start, click Run, type outlook /rpcdiag in the Open box, and then click OK.
  2. Type your credentials in the User name box and in the Password box, and then click OK. If HTTPS appears in the Conn column in the Exchange Server Connection Status dialog box, a service is connected by using RPC over HTTP.
     
     Note The Exchange Server Connection Status window may appear directly behind the Outlook program window.