Feature Walk-through (ISA Server 2004 Getting Started Guide)

  • Article

ISA Server supports a highly flexible, multi-networking environment, enabling you to securely connect numerous networks with varying access permissions. Some sample scenarios illustrating the multi-networking environment and functionality are described in the following sections. Note that the scenarios do not illustrate the complete scope of new features included in this release. Rather, they demonstrate some of the more common firewall scenarios that you can deploy using ISA Server. By performing the walk-through steps in a simple laboratory environment, you can become familiar and comfortable with some of the ISA Server 2004 features and with the user interface.

We recommend that you always create your ISA Server configuration in a laboratory environment before you try it in production.

The scenarios assume a lab configuration connecting an Internal network to the Internet. Various servers are published on a perimeter network (also known as a DMZ, demilitarized zone, or screened subnet). Virtual private network (VPN) clients can access resources on the Internal network. We recommend that you set up three isolated networks in a laboratory environment before deploying a solution in a production environment. The laboratory used in this feature walk-through consists of:

  • A network simulating your corporate network, called CorpNet. In the walk-through, CorpNet spans this address range: 10.0.0.0 through 10.255.255.255.
  • A network simulating the Internet, called MockInternet. In the walk-through, MockInternet spans this address range: 192.168.0.0 through 192.168.255.255.
  • A perimeter network, called PerimeterNet. In the walk-through, PerimeterNet spans this address range: 172.16.0.0 through 172.31.255.255.

The following figure illustrates the scenario environment.

Cc302642.6a17498e-6ac3-4b04-96d8-2d4c6eecdd1a(en-us,TechNet.10).gif

The figure illustrates the following computers:

  • Two client computers, referred to as InternalClient1 and InternalClient2, with Windows® XP installed. These computers are on the CorpNet domain.

  • A server, referred to as InternalWebServer, with Windows Server 2003 and Internet Information Services (IIS) installed. This computer is on the CorpNet domain.

  • A domain controller is assumed to be located on the CorpNet. The domain controller is used for client authentication.

  • A computer, referred to as Perimeter_IIS, with Windows Server 2003 installed. IIS is also installed on this computer. The computer is on the PerimeterNet domain.

  • A computer, referred to as External1, with Windows Server 2003 and IIS installed. This computer is on MockInternet.

  • A Web server, referred to as ExternalWebServer. This computer is on MockInternet.

  • A computer, referred to as ISA_1, with Windows Server 2003 and ISA Server 2004 installed. It has three network adapters installed:

  • The IP address of the adapter connected to CorpNet is 10.0.0.1.

  • The IP address of the adapter connected to PerimeterNet is 172.16.0.1.

  • The IP address of the adapter connected to MockInternet is 192.168.0.1.

    Note

    There are no DNS servers described in the configuration. The scenario assumes that a DNS server is installed on the domain controller on CorpNet. The scenario also assumes that there is name resolution within each network, but not between the networks.

The configuration would be similar in a production environment. The differences would be in the use of the default ISA Server defined External network (representing the Internet) rather than MockInternet, and the use of your real IP address ranges for your internal and perimeter networks.

Different computers are required to test the various scenarios. The following table lists which computers are required for each scenario.

Scenario Computers required

4.1 Export a configuration

ISA_1

4.2 Access the Internet from the Internal network

ISA_1, InternalClient1, ExternalWebServer

4.3 Create and configure a restricted computer set

ISA_1, InternalClient2, External1

4.4 Create a perimeter network using the Network Template Wizard

ISA_1

4.5 Publish a Web server on the perimeter network

ISA_1, External1, Perimeter_IIS

4.6 Publish a Web server on the Internal network

ISA_1, InternalWebServer, External1

4.7 Configure virtual private networking

ISA_1, External1, InternalClient1

4.8 Modify system policy

ISA_1

4.9 Import a configuration

ISA_1

Before you begin configuring the following scenarios, verify that the routing tables on the computers are properly configured. On each network, the default gateway must be set to the IP address of the ISA Server computer’s adapter for that network. For example, to set the default gateway for Perimeter_IIS, type the following at a command prompt on the Perimeter_IIS computer:

route add 0.0.0.0 MASK 0.0.0.0 172.16.0.1

4.1 Scenario 1: Export a configuration

This scenario illustrates the export feature of ISA Server. You can save all or parts of an ISA Server computer’s configuration to an .xml file. This enables you to duplicate all or part of a configuration from one ISA Server computer to another, or to preserve a configuration before you make substantial changes, so that you can revert to an earlier configuration.

In this scenario, you will export the configuration of the ISA Server computer to an .xml file before you make any of the changes associated with the scenarios that follow. To export the configuration, perform the following steps:

  1. Open Microsoft ISA Server Management and click ISA_1.

  2. In the task pane, on the Tasks tab, click Export ISA Server Configuration to a File. This will export the configuration of ISA_1, exactly as it is at the time of export.

  3. In Export Configuration, in Save in, select the location where you want to save the export file. In File name, type the file name of the .xml file to which you want to export the configuration, such as MyDefaultConfig.xml, and click Export.

    Note

    You can choose to export user permission settings, by selecting Export user permission settings. User permission settings contain the security roles of ISA Server users, for example, indicating who has administrative rights.
    You can choose to export user permission settings, by selecting Export user permission settings. User permission settings contain the security roles of ISA Server users, for example, indicating who has administrative rights.
    If you want to export confidential information, select Export confidential information. If you do, confidential information will be encrypted during export. If you export confidential information, you will be prompted to provide a password during the export process. You will need this password when you import the firewall policy configuration.

  4. When the export operation has completed, click OK to close the status dialog box.

4.2 Scenario 2: Access the Internet from the Internal network

In this scenario, internal clients require secured connectivity to the Internet. The following computers are required:

  • ISA_1, with at least two network adapters
  • InternalClient1, on CorpNet, to test the scenario
  • ExternalWebServer, on MockInternet, to test the scenario

The goal is to access ExternalWebServer from InternalClient1 through ISA_1.

The routing table on InternalClient1 routes all requests for external addresses to the internal IP address of the ISA Server computer (the IP address of the network adapter card that is connected to the Internal network). The ISA Server computer is serving as the default gateway for all Internal network requests for external IP addresses.

The following sections describe how to configure the solution:

  • 4.2.1 Configure the Internal network
  • 4.2.2 Create network rules
  • 4.2.3 Create policy rules
  • 4.2.4 Test the scenario

4.2.1 Configure the Internal network

As part of the setup process, you specified the address range in your Internal network, thereby configuring the Internal network. Verify that the configuration is valid, and that the Internal network contains only addresses on Corpnet. On ISA_1, perform the following steps:

  1. Open Microsoft ISA Server Management, expand ISA_1, expand the Configuration node, and click Networks.

  2. In the details pane, on the Networks tab, the address ranges included in each network are shown.

  3. Verify that only IP addresses of computers on your corporate network are included in the Internal network.

    Note

    If necessary, you can reconfigure the Internal network by double-clicking Internal on the Networks tab to open the Internal Properties dialog box. Select the Addresses tab, and use the Add and Remove buttons to add or remove address ranges from the network. You can also use the Add Adapter button to add all of the IP ranges associated with a particular network adapter, or the Add Private button to add private address ranges.

  4. Double-click Internal in the Networks tab to open the Internal Properties dialog box. On the Web Proxy tab, verify that Enable Web Proxy client is selected, that Enable HTTP is selected, and that in HTTP Port, 8080 is specified, and then click OK.

4.2.2 Create network rules

As part of the installation process, a default Internet Access network rule was created. This rule defines a relationship between the Internal network and the External network. To verify the rule configuration, perform the following steps:

  1. Expand the Configuration node, and click Networks.
  2. On the Network Rules tab, double-click the Internet Access rule to display the Internet Access Properties dialog box.
  3. On the Source Networks tab, verify that Internal is listed. If it is not, do the following:
    1. Click Add.
    2. In Add Network Entities, click Networks, click Internal, click Add, and then click Close.
  4. On the Destination Networks tab, verify that External is listed. If it is not, do the following:
    1. Click Add.
    2. In Add Network Entities, click Networks, click External, click Add, and then click Close.
  5. On the Network Relationship tab, select Network Address Translation (NAT).
  6. Click OK.
  7. In the details pane, click Apply to apply changes, if you made any.

4.2.3 Create policy rules

To allow the internal client access to the Internet, you must create an access rule allowing the internal clients to use HTTP and HTTPS protocols. Perform the following steps:

  1. Click Firewall Policy. On the task pane, select the Tasks tab, and click Create New Access Rule to start the New Access Rule Wizard.
  2. On the Welcome page, type the name of the rule. For example, type Allow Internal clients HTTP and HTTPS access to the Internet. Then, click Next.
  3. On the Rule Action page, select Allow, and then click Next.
  4. On the Protocols page, in This rule applies to, select Selected protocols, and then click Add.
  5. In the Add Protocols dialog box, expand Common Protocols. Click HTTP, click Add, click HTTPS, click Add, and then click Close. Then, click Next.
  6. On the Access Rule Sources page, click Add.
  7. In the Add Network Entities dialog box, click Networks, and then select Internal. Click Add, and then click Close. Then, click Next.
  8. On the Access Rule Destinations page, click Add.
  9. In the Add Network Entities dialog box, click Networks, and then select External. Click Add, and then click Close. Then, click Next.
  10. On the User Sets page, verify that All Users is specified. Then, click Next.
  11. Review the summary page, and then click Finish.
  12. In the details pane, click Apply to apply the changes you made. Note that it may be a few moments before the changes are applied.

4.2.4 Test the scenario

To verify that the scenario works, InternalClient1 will access ExternalWebServer on the External network (MockInternet).

On InternalClient1, perform the following steps:

  1. On InternalClient1, open Internet Explorer 6.0.
  2. In Internet Explorer, click the Tools menu, and then click Internet Options.
  3. On the Connections tab, click LAN Settings.
  4. In Proxy server, select the Use a proxy server for your LAN check box.
  5. In Address, type the computer name of ISA_1 and in Port, type 8080. If there is no DNS server in your lab configuration, use the IP address of ISA_1 rather than its name.
  6. Verify that Automatically detect settings is not selected.
  7. Close Internet Explorer. Then, reopen Internet Explorer.
  8. In Internet Explorer, in Address, type the IP address of ExternalWebServer.

Note that if a DNS server is available for name resolution on MockInternet, you can type the fully qualified domain name (FQDN) of ExternalWebServer.

If your browser displays the Web page published on ExternalWebServer, InternalClient1 accessed ExternalWebServer, and you have successfully configured this scenario.

4.3 Scenario 3: Create and configure a restricted computer set

In this scenario you will create a computer set within the Internal network, and deny it access to the Internet. The following computers are required:

  • ISA_1 with at least two network adapters.
  • InternalClient2, on CorpNet.
  • ExternalWebServer, on MockInternet, to test the scenario.

The following sections describe how to configure the solution:

  • 4.3.1 Configure the restricted computer set
  • 4.3.2 Restrict access to the Internet
  • 4.3.3 Test the scenario

4.3.1 Configure the restricted computer set

The following example uses the IP addresses associated with the lab deployment Internal network: 10.0.0.0 through 10.255.255.255. In the example, you will create a computer set containing the IP addresses 10.54.0.0–10.55.255.255, which includes InternalClient2. Perform the following steps:

  1. Open Microsoft ISA Server Management, expand ISA_1, and click Firewall Policy.
  2. On the task pane, select the Toolbox tab, select Network Objects, click New, and then select Computer Set.
  3. In Name, type a name for the new computer set, such as Restricted Computer Set.
  4. Click Add and select AddressRange.
  5. In the New Address Range Rule Element dialog box, provide a name for the address range, such as Range for Restricted Computer Set. Provide an IP address range that includes the address of InternalClient2, such as 10.54.0.0–10.55.255.255, and then click OK.
  6. Click OK to close the New Computer Set Rule Element dialog box.
  7. In the details pane, click Apply to apply the changes you made.
  8. Save the network configuration to an .xml file, so that if you make a make a configuration change that changes or destroys this network object, you can recover its configuration. On the task pane, in the Toolbox tab, select Network Objects, expand Computer Sets, right-click the newly defined computer set, and select Export Selected. Choose a location in which to save the file containing the configuration information, and a name that describes its contents, such as Restricted computer set export file. Click Export to export the configuration.
  9. When the export operation is complete, click OK to close the status dialog box.

4.3.2 Restrict access to the Internet

You can now create an access rule denying Internet access to the computer set. Note that the order of the access rules will affect whether the computer set will be able to access the Internet. ISA Server reads access rules in order, and will allow access if it reads the Internal network allow rule before it reads the Restricted Computer Set deny rule.

To create an access rule that denies access from the Restricted Computer Set to the External network, perform the following steps:

  1. Click Firewall Policy. In the task pane, select the Tasks tab, and click Create New Access Rule to start the New Access Rule Wizard.
  2. On the Welcome page, type the name of the rule. For example, type Deny Restricted Computer Set HTTP and HTTPS access to the Internet. Then, click Next.
  3. On the Rule Action page, select Deny, and then click Next.
  4. On the Protocols page, in This rule applies to, select Selected protocols, and then click Add.
  5. In the Add Protocols dialog box, click Common Protocols. Click HTTP, click Add, click HTTPS, click Add, and then click Close. Then, click Next.
  6. In the Add Network Entities dialog box, click Computer Sets, and then select Restricted Computer Set. Click Add, and then click Close. Then, click Next.
  7. On the Access Rule Destinations page, click Add.
  8. In the Add Network Entities dialog box, click Networks, and then select External. Click Add, and then click Close. Then, click Next.
  9. On the User Sets page, verify that All Users is specified. Then, click Next.
  10. Review the summary page, and then click Finish.
  11. In the details pane, click Apply to apply the changes you made.
  12. Save the rule to an .xml file so that if you make a basic change, such as running a Network Template Wizard, you can import the rule. In the details pane, right-click the newly defined rule, and select Export Selected. Choose a location in which to save the file containing the rule information, and a name that describes its contents, such as Restricted Computer Set Internet Deny Rule.xml. Click Export to export the rule.
  13. When the export operation is complete, click OK to close the status dialog box.

4.3.3 Test the scenario

To verify that the scenario works, InternalClient2 in the Restricted Computer Set will try to access ExternalWebServer on the External network (MockInternet).

On InternalClient2, perform the following steps:

  1. On InternalClient2, open Internet Explorer 6.0.

  2. In Internet Explorer, click the Tools menu, and then click Internet Options.

  3. On the Connections tab, click LAN Settings.

  4. In Proxy server, select the Use a proxy server for your LAN check box.

  5. In Address, type the computer name (or IP address, if you do not have a DNS server configured) of ISA_1 and in Port, type 8080.

  6. Verify that Automatically detect settings is not selected.

  7. Close Internet Explorer. Then, reopen Internet Explorer.

  8. In Internet Explorer, in Address, type the IP address of ExternalWebServer.

    Note

    If a DNS server is available for name resolution on MockInternet, you can type the FQDN of ExternalWebServer.

If your browser displays an access denied page, you configured the computer set and deny rule successfully.

The deny access rule you created appears first in the list of access rules in the Firewall Policy details pane. If you move it down in order below the Allow Internal clients HTTP and HTTPS access to the Internet allow rule (created in the previous scenario), ISA Server will evaluate the allow rule first, and computers in the Restricted Computer Set will have access to the Internet. To change the order of the deny rule, right-click the rule and select Move Down. After you move the deny rule below the allow rule and apply changes by clicking the Apply button in the details pane, test the Internet access again. InternalClient2 should now have Internet access.

If your browser now displays the Web page published on ExternalWebServer, InternalClient2 accessed ExternalWebServer, and you have successfully configured this scenario.

4.4 Scenario 4: Create a perimeter network using the Network Template Wizard

In this scenario, you will use the Network Template Wizard to create a perimeter network.

To configure this scenario, you will perform the following steps:

  • 4.4.1 Create a perimeter network
  • 4.4.2 Restore restricted computer set access rule

4.4.1 Create a perimeter network

You will use the Network Template Wizard to create the perimeter network, and to establish Internet access from the Internal network to the Internet.

To create a perimeter network, perform the following steps:

  1. In Microsoft ISA Server Management, expand ISA_1, click Configuration, and then click Networks.

  2. In the task pane, on the Templates tab, select 3-Leg Perimeter. This starts the Network Template Wizard.

  3. On the Welcome page, click Next.

  4. On the Export the ISA Server Configuration page, click Export if you want to preserve your current configuration. With this step, you can revert to your current configuration by importing it from the saved file. If you click Export, provide a location and a descriptive file name such as Configuration prior to configuring 3-leg Perimeter, and click Export.

  5. On the Export the ISA Server Configuration page, click Next.

  6. On the Internal Network IP Addresses page, use the Add and Remove buttons to ensure that only the IP addresses of the Internal network are shown. This would include the IP address of InternalClient1 and the IP address of the network adapter card on ISA_1 that connects to the Internal network. Click Next.

  7. On the Perimeter Network IP Addresses page, use the Add and Remove buttons to ensure that only the IP addresses of the perimeter network are shown. This would include the IP address of Perimeter_IIS, and the IP address of the network adapter card on ISA_1 that connects to the perimeter network. Click Next.

  8. On the Select a Firewall Policy page, select Allow limited Web access to create an access rule allowing access from the Internal network to the External network (upon completion of the wizard), and then click Next.

  9. On the summary page, review the network configuration, and then click Finish.

  10. In the details pane, click Apply to apply the changes you made using the wizard.

    Note

    The Network Template Wizard creates two network rules: one that creates a route relationship between the perimeter network and the External network (the Perimeter Access rule), and one that creates a NAT relationship between the Internal network and the perimeter network (the Perimeter Configuration rule). Verify that the rules were created by selecting the Network Rules tab in the Networks details pane.
    A route relationship is bidirectional. Routing is from source to destination and destination to source. A NAT relationship is unidirectional. Routing is from source to destination.

4.4.2 Restore restricted computer set access rule

When you ran the Network Template Wizard and applied changes, you removed the restricted computer set and the access rule denying the restricted computer set access to the Internet. You could create these again, or you can import them from the .xml files you saved when you created the restricted computer set and its access rule.

To import the configuration, perform the following steps:

  1. In Microsoft ISA Server Management, expand ISA_1, right-click Firewall Policy, and select Import.

  2. Provide the location and file name for the exported access rule, such as Restricted Computer Set Internet Deny Rule.xml created in Scenario 3, and click Import. When the import is complete, click OK.

  3. In the details pane, click Apply to apply the changes you made.

    Note

    When you import an access rule, you also import the rule elements that it refers to, so there is no need to import the computer set separately. You can import rule elements separately by right-clicking the type of rule element in the task pane, on the Toolbox tab, and selecting Import All.

4.5 Scenario 5: Publish a Web server on the perimeter network

In this scenario, a Web server located on the perimeter network will be made available to users on the Internet.

You use Web publishing rules to publish Web servers. Web publishing rules require Web listeners, which listen for Web requests.

The following computers are required:

  • ISA_1, with at least three network adapters.
  • Perimeter_IIS, on PerimeterNet, to test the scenario.
  • External1, on MockInternet, to test the scenario.

To configure this scenario, you will perform the following steps:

  • 4.5.1 Create a Web publishing rule
  • 4.5.2 Test the scenario

4.5.1 Create a Web publishing rule

To create a Web publishing rule allowing a client computer on the Internet (External1) access to a Web server on the perimeter network (Perimeter_IIS), perform the following steps:

  1. In Microsoft ISA Server Management, expand ISA_1, and click Firewall Policy.

  2. In the task pane, on the Tasks tab, click Publish a Web server to start the New Web Publishing Rule Wizard.

  3. On the Welcome page, in Web publishing rule name, type the rule name: Allow External to Perimeter_IIS. Click Next.

  4. On the Select Rule Action page, select Allow, and then click Next.

  5. On the Define Website to Publish page, in Computer name or IP address, type the IP address or computer name of the Web server to publish, and then click Next.

    Note

    On the Define Website to Publish page, in Folder, you can specify a specific folder to publish.

  6. On the Public Name Details page, verify that This domain name is selected. In the text box under This domain name, type the public domain name or IP address of the published website. This is what the user will type in the address field of the browser to access your website. In a laboratory setting where there is no resolvable name, use the IP address of the ISA Server computer’s external network adapter. You can specify a folder, which will be appended to the name and is then displayed in Site. Click Next.

  7. On the Select Web Listener page, click New to start the New Web Listener Wizard.

  8. On the Welcome page of the New Web Listener Wizard, in Web listener name, type the name of the Web listener: Listen on Port 80 of External Network. Then, click Next.

  9. On the IP Addresses page, select External, and then click Next. This listener will then listen for requests from the External network.

  10. On the Port Specification page, in HTTP port, type 80. Optionally, you can select Enable SSL and an SSL port if you want to publish on HTTPS. This would require you to select a certificate on this page, using the Select button. Click Next.

  11. Review the summary page, and then click Finish to close the New Web Listener Wizard.

  12. On the Select Web Listener page, click Next.

  13. On the User Sets page, verify that All Users is listed in This rule applies to requests from the following user sets. Click Next.

  14. Review the summary page, and then click Finish.

  15. In the details pane, click Apply to apply the changes you made.

Note

You can create and modify Web listeners independently of Web publishing rules. Access to existing Web listeners is through the Web Listeners folder on the Toolbox tab in the Firewall Policy task pane. To create a new Web listener, in the Firewall Policy task pane, on the Toolbox tab, click New, and then select Web Listener.

4.5.2 Test the scenario

To verify that the scenario works, the external client, External1, will access Perimeter_IIS, the HTTP server located on the perimeter network (PerimeterNet). On External1, perform the following steps:

  1. Open Internet Explorer.
  2. Verify that no proxy client is configured. To do this, on the Tools menu, select Internet Options. On the Connections tab, click LAN Settings. Verify that none of the following check boxes are selected: Automatically detect settings, Use automatic configuration script, and Use a proxy server for your LAN. Click OK to close Internet Options.
  3. In Address, type the IP address of the ISA Server computer’s external network adapter.

If the client accessed the default website on Perimeter_IIS, you successfully configured this scenario.

4.6 Scenario 6: Publish a Web server on the Internal network

In this scenario, a Web server located on the Internal network will be made available to users on the Internet. The following computers are required:

  • ISA_1, with at least two network adapters available.
  • InternalWebServer as the Web server, to test the scenario.
  • External1 on MockInternet as the external client, to test the scenario.

To configure this scenario, you will perform the following steps:

  • 4.6.2 Publish the Web server
  • 4.6.3 Test the scenario

4.6.1 Create network rules

Before you verify the network rule defining the network relationship between Internal and External networks, see section 4.2.1 for instructions on validating the configuration of the Internal network.

Upon installation, a default network rule, defining a NAT relationship from the Internal network to the External network, was created. On ISA_1, to verify that the rule is properly configured, perform the following steps:

  1. In Microsoft ISA Server Management, expand ISA_1, expand the Configuration node, and then click Networks to view the Networks details pane.
  2. In the details pane, click the Network Rules tab. You can verify the rule in the details pane, or open the rule properties as described in the following steps.
  3. Double-click the Internet Access rule to open Internet Access Properties.
  4. On the General tab, ensure that the rule is enabled.
  5. On the Source Networks tab, ensure that the Internal network is listed.
  6. On the Destination Networks tab, ensure that the External network is listed.
  7. On the Network Relationship tab, ensure that Network Address Translation is selected.

4.6.2 Publish the Web server

Use Web publishing rules to allow external clients to access the Web server located on the Internal network.

Publishing the Web server requires that you create a Web publishing rule. In the process of creating the rule, you will also create a Web listener that specifies on which IP addresses ISA Server will listen for requests for the internal website. If you still have the listener that you created for the perimeter Web publishing scenario, you should use it in this scenario, rather than create a new listener.

Note

You can create and modify Web listeners independently of Web publishing rules. Access to existing Web listeners is through the Web Listeners folder on the Toolbox tab in the Firewall Policy task pane. To create a new Web listener, in the Firewall Policy task pane, on the Toolbox tab, click New, and then select Web Listener.

To create a Web publishing rule allowing a client computer on the Internet (External1) access to a Web server on the Internal network (InternalWebServer), perform the following steps:

  1. In Microsoft ISA Server Management, expand ISA_1, and click Firewall Policy.

  2. In the task pane, on the Tasks tab, click Publish a Web server to start the New Web Publishing Rule Wizard.

  3. On the Welcome page, in Web publishing rule name, type the rule name: Allow External to InternalWebServer. Click Next.

  4. On the Select Rule Action page, select Allow, and then click Next.

  5. On the Define Website to Publish page, in Computer name or IP address, type the IP address or computer name of the Web server to publish. In a laboratory setting where there is no resolvable name, use the IP address of the ISA Server computer’s external network adapter. Click Next.

    Note

    On the Define Website to Publish page, in Folder, you can specify a specific folder to publish. In a laboratory setting where there is no DNS server, you would use the same IP address to identify both the perimeter and internal Web servers, so only one will be available at a time, based on which rule appears first in the rule order. In a production deployment, or in a laboratory deployment with a DNS server, the use of names that are resolved by a DNS server would eliminate this issue.

  6. On the Public Name Details page, verify that This domain name is selected. In the text box under This domain name, type the public domain name or IP address of the published website. This is what the user types in the address field of the browser to access your website. You can specify a folder, which will be appended to the name and is then displayed in Site. Click Next.

  7. On the Select Web Listener page, click New to start the New Web Listener Wizard.

  8. On the Welcome page of the New Web Listener Wizard, in Web listener name, type the name of the Web listener: Listen on Port 80 of External Network. Then, click Next.

  9. On the IP Addresses page, select External, and then click Next. This listener will then listen for requests from the External network.

  10. On the Port Specification page, in HTTP port, type 80. Optionally, you can select Enable SSL and an SSL port if you want to publish on HTTPS. This would require you to select a certificate on this page, using the Select button. Click Next.

  11. Review the summary page, and then click Finish.

  12. On the Select Web Listener page, click Next.

  13. On the User Sets page, verify that All Users is listed in This rule applies to requests from the following user sets. Click Next.

  14. Review the summary page, and then click Finish.

  15. In the details pane, click Apply to apply the changes you made.

4.6.3 Test the scenario

To verify that the scenario works, the external client, External1, will access InternalWebServer, the HTTP server located on the Internal network (CorpNet). ISA_1 will listen for the requests on behalf of InternalWebServer, and forward them in accordance with the Web publishing rule to InternalWebServer.

On External1, perform the following steps:

  1. Open Internet Explorer.
  2. In Address, type the IP address of the external adapter on ISA_1.

If the client accessed the default website on InternalWebServer, you successfully configured this scenario.

4.7 Scenario 7: Configure virtual private networking

In this scenario, ISA Server serves as the VPN server for remote clients connecting to the corporate (Internal) network. The following computers are required:

  • ISA_1, with at least two network adapters available.
  • External1 on MockInternet, the VPN client, to test the scenario.
  • InternalClient1 on Corpnet, to test the scenario.

The following sections describe how to configure the scenario:

  • 4.7.1 Enable VPN client access
  • 4.7.2 Create access rules
  • 4.7.3 Create a Windows user with dial-up permissions
  • 4.7.4 Create a network dial-up connection
  • 4.7.5 Test the scenario

4.7.1 Enable VPN client access

In this step, you will enable VPN client access. To allow VPN connections, you must enable virtual private networking. All other VPN client properties will assume the default settings. This includes the default settings for the pool of IP addresses dynamically assigned from the Internal network, which will be available for clients connecting to ISA Server. This solution also assumes a dynamically assigned name resolution server that VPN clients can use to resolve names on the Internal network.

To configure the VPN properties, perform the following steps:

  1. In Microsoft ISA Server Management, expand ISA_1, and click Virtual Private Networks (VPN).

  2. In the task pane, on the Tasks tab, click Enable VPN Client Access.

  3. In the details pane, click Apply to apply the changes you made.

    Note

    During installation, ISA Server creates a network rule establishing a route relationship between the VPN clients and the Internal network. If you want certain VPN clients to be able to access other networks, you must create an additional network rule. The relationship between the VPN client and the Internal network is a route relationship, because the goal is for the VPN client to transparently become part of the Internal network, and be able to see the computers on the Internal network.

If your laboratory configuration does not include a DHCP server that assigns IP addresses to VPN clients, to create a static address pool from which the addresses will be assigned, perform the following steps:

  1. In Microsoft ISA Server Management, expand ISA_1, and click Virtual Private Networks (VPN).
  2. In the task pane, on the Tasks tab, under the heading General VPN Configuration, click Define Address Assignments. This opens the Virtual Private Networks (VPN) Properties page Address Assignment tab.
  3. Select Static address pool.
  4. Click Add. In the IP Address Range Properties dialog box, provide a range of IP addresses that will be assigned to VPN clients. Note that these addresses cannot be from the range of addressees included in the Internal network.
  5. Click OK.
  6. In the details pane, click Apply to apply the changes you made.

4.7.2 Create access rules

To allow the VPN clients access to resources on the Internal network, you must create an access rule. Perform the following steps:

  1. In Microsoft ISA Server Management, expand ISA_1, and click Firewall Policy.

  2. In the task pane, on the Tasks tab, click Create New Access Rule to start the New Access Rule Wizard.

  3. On the Welcome page, type the name of the rule. For example, type Allow VPN clients access to Internal. Then, click Next.

  4. On the Rule Action page, select Allow, and then click Next.

  5. On the Protocols page, in This rule applies to, select All outbound protocols, to allow VPN clients to access the Internal network on any protocol. Click Next.

  6. On the Access Rule Sources page, click Add.

  7. In Add Network Entities, click Networks, and then select VPN Clients. Click Add, and then click Close. Then, on the Access Rule Sources page, click Next.

  8. On the Access Rule Destinations page, click Add.

  9. In Add Network Entities, click Networks, and then select Internal. Click Add, and then click Close. Then, on the Access Rule Destinations page, click Next.

  10. On the User Sets page, verify that All Users is specified. Click Next.

  11. Review the summary page, and then click Finish.

  12. In the details pane, click Apply to apply the changes you made.

    Note

    You can restrict which protocols the VPN clients can use when communicating with the Internal network by selecting Selected protocols in step 5. In this case, be sure to include the DNS Query protocol, so that VPN clients can resolve the names of computers on the Internal network.

You could also create a rule allowing only certain users access to specific computers, or to parts of your corporate network that you have defined separately from the Internal network.

4.7.3 Create a Windows user with dial-up permissions

For a VPN client to dial in to the network, you must create a user with dial-in permissions on CorpNet. The user can be a domain user or a local user on the ISA Server computer. The VPN client will authenticate as this user. Perform the following steps:

  1. On ISA_1, open Computer Management by right-clicking My Computer on the desktop and selecting Manage.
  2. In Computer Management, click Computer Management (Local), expand System Tools, and click Local Users and Groups.
  3. In the details pane, right-click Users, and then click New User.
  4. Type the user details, and then click Create.
  5. In the details pane, double-click Users to display the list of users, right-click the new user, and then click Properties.
  6. On the Dial-in tab, select Allow access, and then, click OK.

4.7.4 Create a network dial-up connection

The VPN client creates a new connection that can be used to dial in to the CorpNet. On External1, perform the following steps:

  1. Click Start, select Control Panel, and then double-click Network Connections.
  2. On the File menu, select New Connection to open the New Connection Wizard.
  3. On the Welcome screen, click Next.
  4. On the Network Connection Type page, select Connect to the network at my workplace, and then click Next.
  5. On the Network Connection page, select Virtual Private Network connection, and then click Next.
  6. On the Connection Name page, in Company Name, type Connect to ISA_1, and then click Next.
  7. On the Public Network page, select whether you want Windows to automatically dial the initial connection to the network, and which connection to dial, and then click Next.
  8. On the VPN Server Selection page, in Host name or IP address, provide the IP address of the external network adapter card of ISA_1, and then click Next.
  9. On the Connection Availability page, select My use only to ensure that the VPN connection will only be used when you are logged on to the client computer, and then click Next.
  10. Review the summary page, and then click Finish.

4.7.5 Test the scenario

To verify that the scenario works, the VPN client, External1, will access a computer on the Internal network. On External1, perform the following steps:

  1. Click Start, click Connect To, and then click Connect to ISA_1.
  2. In ISA_1\User name, type the name of the user you created in Section 4.7.4. Then, click Connect.

If the connection is created, you successfully configured this scenario.

4.8 Scenario 8: Modify system policy

We recommend that you disable elements of the system policy that you are not going to use. This scenario demonstrates how to disable Terminal Server remote management of ISA Server.

To disable Terminal Server remote management of ISA Server, perform the following steps:

  1. In Microsoft ISA Server Management, expand the ISA Server computer node, and click Firewall Policy.
  2. In the task pane, on the Tasks tab, click Edit System Policy to open the System Policy Editor.
  3. Under Configuration Groups, locate Remote Management and select Terminal Server.
  4. On the General Tab, clear the Enable check box, and then click OK.
  5. In the details pane, click Apply to apply the changes.

4.9 Scenario 9: Import a configuration

This scenario illustrates the export and import feature of ISA Server. This scenario relates to Scenario 1, Export a configuration.

In this scenario, you will perform the following procedures:

  1. 4.9.1 Export current configuration
  2. 4.9.2 Import old and new configurations

4.9.1 Export current configuration

To export the current configuration to an .xml file, perform the following steps:

  1. Open Microsoft ISA Server Management and click ISA_1.

  2. In the task pane, on the Tasks tab, click Export ISA Server Configuration to a File. This will export the configuration of ISA_1, exactly as it is at the time of export.

  3. In Export Configuration, in Save in, select the location where you want to save the export file. In File name, type the file name of the .xml file to which you want to export the configuration, such as MyNewConfig.xml, and click Export.

    Note

    You can choose to export user permission settings, by selecting Export user permission settings. User permission settings contain the security roles of ISA Server users, for example, indicating who has administrative rights.If you want to export confidential information, select Export confidential information. If you do, confidential information will be encrypted during export. If you export confidential information, you will be prompted to provide a password during the export process. You will need this password when you import the firewall policy configuration.

  4. When the export operation is complete, click OK to close the status dialog box.

4.9.2 Import old and new configurations

To import configurations, perform the following steps:

  1. Open Microsoft ISA Server Management and click ISA_1.

  2. In the task pane, on the Tasks tab, click Import from an Exported ISA Server Configuration File.

  3. In Import Configuration, in File name, type or browse to the file name of the .xml file you created in Scenario 1 (MyDefaultConfig.xml), and then click Import. If you are importing confidential information, you will be prompted to provide a password in the Type Password to Open File dialog box.

    Note

    You can choose to import user permission settings, by selecting Import user permission settings. You can also choose to import cache drive settings and SSL certificate usage configuration by selecting Import cache drive settings and SSL certificates. This may be inappropriate when copying a policy to another server, because these selections tend to be specific to a particular server.

  4. Check the details pane of the Firewall Policy and Networks nodes, and verify that the perimeter network and the rules you created in scenarios 2 through 7 are no longer present. If so, the import succeeded, and the ISA Server computer is now configured as it was before you completed scenarios 2 through 7.

  5. Repeat the procedure, this time importing the configuration you saved to MyNewConfig.xml. The perimeter network and the rules you created in scenarios 2 through 7 should now be in place.

In the details pane, click Apply to apply changes, if you want the changes made by the restore operation to be applied.

[Topic Last Modified: 02/27/2008]