Shijaz.com: Articles | Windows Server | Exchange Server | ISA Server |

 

Publishing SharePoint with ISA 2006

 

Shijaz Abdulla, MVP

www.shijaz.com/isaserver

 

This article explains how to successfully publish a SharePoint site on ISA Server 2006. In this example I have used ISA 2006 Enterprise Edition. However, it is not much different to configure publishing SharePoint on ISA 2006 Standard Edition.

 

Assumptions/Objectives

 

Step-by-Step

 

Part 1: Configuration on SharePoint Server

1.    On the SharePoint Portal Server computer, click Start, point to All Programs, point to SharePoint Portal Server, and click SharePoint Central Administration.

2.    Under Portal Site and Virtual Server Configuration, click Configure alternate portal site URLs for intranet, extranet and custom access.

3.    Under Mapping Name, click the Web site and select Edit.

4.    Under Extranet URL, provide the public name for the SharePoint Web site, for example http://intranet.shijaz.com. If you are using SSL make sure you type the https:// prefix.

 

 

 

Part 2: Configuration on ISA Server

 

1.    On the computer running ISA 2006, open the ISA Management Console.

2.    Right click on Firewall Policy, choose New > SharePoint Site Publishing Rule.

 

 

3.    Give the rule a name. This can be anything that makes sense to you. Click Next.

 

 

4.    Choose Publish a Web site or a load balancer. Click Next.

 

 

5.    Choose Use non-secured connections to connect the published Web server or server farm option. Click Next.

6.    For the Internal site name, type the name of your SharePoint server. Select the checkbox Use a computer name or IP address to connect to the published server and browse to select your SharePoint server. Click Next.

 

 

7.    For Accept requests for, select This domain name (type below) option and in the text box for Public name, enter your internet (public) name that you wish to use for this sharepoint site. Click Next.

 

8.    It is now time to create a Web Listener for your SharePoint publishing rule. Click New in the next window. You will be taken to the New Web Listener Wizard.

9.    Since we are publishing over HTTP, Choose Do not require SSL secured connections with clients. Click Next.

 

 

10.  Under Listen for incoming requests on these networks, choose External. Click Next.

 

 

11.  Choose the Authentication Setting you want to use. HTTP Authentication means that the user will be provided a popup window in his browser prompting for his domain credentials. If you select HTTP Forms based Authentication, the prompt for credentials will be in the form of a webpage like the one shown below:

 

HTTP Forms Authentication

 

12.  You’re done with the Web Listener. Click Finish.

 

13.  See the description for each form of Authentication Delegation. Choose No Delegation, but client may authenticate directly option to enable client to authenticate directly to the published SharePoint server. ISA does not get in the middle of the authentication process. Click Next.

 

 

14.  Select SharePoint AAM is already configured on the SharePoint server in the Alternate Access Mapping Configuration page.

 

 

15.  Select SharePoint AAM is already configured on the SharePoint server in the Alternate Access Mapping Configuration page. Click Next and Finish.

 

16.  You now have the publishing rule and listener in place. However, since we are using HTTP, ISA 2006 automatically disables client authentication over HTTP. To enable it, open the Listener properties of the Web Listener that you just created.

 

17.  On the Authentication tab, click Advanced.

 

 

18.  Click Allow client authentication over HTTP. Click OK and click Apply to save your changes in ISA configuration.

 

 

Comments

·         I highly recommend that you procure an SSL certificate and use https if you plan to publish your SharePoint Portal over the internet.

 

 

Was this Article Useful?

Sign my Guestbook!

 

 

 

 

Disclaimer

 

The steps mentioned in this are results of testing in a lab environment. The procedure might require additional testing before being deployed on a live environment. I assume no responsibility for damage(s) occurring due to following this procedure or any other procedure listed on this site. Use it at your own risk!