Copyright: Monday, November 13, 2000 16:07:45


Provides a space for you to type the name of the server or array.

The name should be unique. Using the Fully Qualified Domain Name (FQDN) will avoid any conflict with duplicated server names.

For more information, see The enterprise, arrays and stand-alone servers.


(Optional) Provides a space for you to type a description.


Displays the creation date.


Displays the last modification date.


Displays the array type: Array or Stand-alone server. Arrays can have zero or more member servers. Enterprise policies can be applied to domain arrays.

A stand-alone server has only one member server. Only array policies can be applied to independent arrays.

For more information, For more information, see Arrays and stand-alone servers.


Displays the installation mode: firewall, cache or integrated. Depending on the mode, different functions are available.

For more information, For more information, see ISA Server modes


Displays the name of the server.


Displays the Fully Qualified Domain Name (FQDN) of the computer.


(Optional) Provides a space for you to type a description of the server.


Displays the version of ISA Server that is installed on the computer.


Displays the product identification number of the ISA Server software.


Displays the date when ISA Server was installed.


No help is available for the specified topic.


Displays the name of the folder where ISA Server is installed.


Displays the name of the domain controller to which the server or array is connected.


Provides a space for you to type the IP address that should be used for communication with other array members.

If your ISA Server is a member of a multiserver array, the Cache Array Routing Protocol (CARP) algorithm is used. When a member server determines that an object is not available in its cache, CARP uses this IP address to send the request to another member server. This IP address must be internal and included in the local address table (LAT).

For more information, For more information, see Configuring Cache Array Routing Protocol


Click to choose a different internal IP address for communication with other array members.


Provides a place to type the load factor.

One of the advantages of an array is load balancing, allowing the client load to be distributed evenly among all array members. Changing the value of the load factor increases or decreases the load on the ISA Server computer.

For more information, For more information, see Configuring Cache Array Routing Protocol


Specifies that log information should be saved to a file.

 For more information, For more information, see Logging to a file


Displays a list of available file formats for the log. You can choose between W3C extended log file format and ISA file format.

 For more information, For more information, see Logging to a file


Lists how often ISA Server creates a new log. You can create a new log daily, weekly, monthly, or yearly. When a new log is created, the previous log is closed.

For more information, For more information, see Logging to a file


Displays the name of the log file.

Yyyy represents the year that the log was created.

Mm represents the month that the log  was created.

Dd represents the date that the log was created.

For example: FWXEXT20001104 is the name of a log in W3C extended format, that was created on November 4, 2000.

 For more information, For more information, see Logging to a file


Click to change the location of the log and to set compression.


Specifies that ISA Server should save log information to an ODBC-compliant database.

For more information, For more information, see Logging to a database


Provides a space for you to type the ODBC data source name for the log database.

For more information, For more information, see Logging to a database


Provides a space for you to type the name of the database table for the ISA Server log. The table name should not include spaces.

For more information, For more information, see Logging to a database


Provides a space for you to type an account name to use when logging on to the log database.

For more information, For more information, see Logging to a database


Click to specify a user account for logging on to the database.


Provides a space for you to type your password to log on to the log database.

For more information, For more information, see Logging to a database


Specifies whether logging is enabled for this component. If not selected, no events are recorded in the log.

For more information, For more information, see Configuring Log


Click to limit the number of log files that are saved.


Provides space to type a limit for the number of log files that are saved.


Lists fields that can appear in the log. In database logging, all fields except Time and Date may be excluded. When logging to a file, all fields except Time may be excluded.

If you have chosen the ISA file format, then all fields will be appear in the file, but unselected fields will be marked with a hyphen. If you have chosen W3C extended log file format, then only selected files will be logged. (Text) indicates headings as they will appear in the log.

 For more information, see Firewall and Web Proxy log fields;  Packet Filter log fields


Click to select the fields that are logged by default.


Click to select all the listed fields.


Click to deselect all fields except those that are mandatory.


Specifies that ISA Server saves the log file in the ISA\ ISALogs folder.

For more information, see Logging to a file


Specifies that ISA Server saves the log file in the specified folder.

For more information, see Logging to a file


Provides a space for you to type the name of the folder in which to save the log file.

 For more information, see Logging to a file


Click to select the folder in which to save the log file.


Click to enable compression of the log file. This reduces the disk space used by the log files. Files are only compressed if they are stored on NTFS partitions.


Provides a space for you to type the name of the alert.

An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts;  ISA Server events


(Optional) Provides a space for you to type a description of the alert.


Specifies whether the rule is enabled.

An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts;  ISA Server events.


Displays a list of events defined by ISA Server.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts;  ISA Server events


When applicable, displays a list of additional keys for the selected event. An additional key means an additional condition that must be fulfilled in order for the alert to be triggered.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts;  ISA Server events


Displays a list of servers. This alert can be triggered for a specific server, or in an array, for all servers in the array.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts;  ISA Server events


Select when the alert is reissued.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts;  ISA Server events.


Specifies a threshold level of how many events should pass before the alert is reissued. If a value is typed in here, and a value is also typed in Number of events per second before the alert is reissued, then both limits must be reached before an alert is reissued.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts;  ISA Server events.


Provides a space for you to type how many times an event should recur before the alert is reissued. If a value is typed in here, and a value is also typed in Number of events per second before the alert is reissued, then both limits must be reached before an alert is reissued.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts;  ISA Server events.


Specifies whether the alert should be reissued if the specified number of events occur per second. If a value is typed in here, and a value is also typed in Number recurrences before the alert is reissued, then both limits must be reached before an alert is reissued.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts;  ISA Server events.


Provides a space for you to type how many events per second should occur before the alert is reissued. If a value is typed in here, and a value is also typed in Number recurrences before the alert is reissued, then both limits must be reached before an alert is reissued.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts;  ISA Server events


Displays a list of choices for how recurring actions are initiated.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts;  ISA Server events


Specifies that the action should be executed immediately after the specified conditions occur.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts


Specifies that the action should be executed only after the alert is manually reset.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts


Specifies that the action should be executed if it was executed before the specified number of minutes.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts


Provides a space for you to type how many minutes should pass before re-issuing the alert.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see  Configuring alerts


Displays a description of the event.


Specifies whether an e-mail should be sent when the alert conditions are met. Select this option only if an internal Simple Mail Transfer Protocol (SMTP) server can be used to send the e-mail. In order to check whether an SMTP Server is available, click Servers and Arrays, click Name , click Extensions, click Application Filters and then click SMTP Filter and check Server properties.

An alert notifies you when specified events occurs and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts


Provides a space for you to type the Internet protocol (IP) address or name of the Simple Mail Transfer Protocol (SMTP) server.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts


Click to find available Simple Mail Transfer Protocol (SMTP)  servers


Provides a space for you to type the e-mail address of the recipient.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts


Provides a space for you to type the e-mail address of the person who receives a copy of the mail.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts


Provides a space for you to type the e-mail address of the sender.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts


Click to test e-mail facility.


Specifies whether a program should be executed when the alert conditions are met.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts


Provides a space for you to type the location and name of the program you want to run. If you are not sure of the program's location or file name, click Browse.

For more information, see Configuring alerts


Click to browse through folders to find the file you want.


Displays the name of the selected user account or local system account that will be used to run the specified program.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts


Click to select which account to use when running the specified program.


Specifies whether the event should be written to the Windows 2000 event log when the alert conditions are met.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

To view the Windows 2000 event log, click Start, point to Programs, point to Administrative Tools, and click Event Viewer.

For more information, see ISA Server events


Specifies whether the selected services should be stopped when the alert conditions are met. If you set the alert actions to start and stop a service, then the service is first stopped and then restarted.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts;  ISA Server services


Click to select which services to stop.


Specifies whether the selected services, Firewall Proxy and Web Proxy, should be started when the alert conditions are met. If you set the alert actions to start and stop a service, the service is first stopped then restarted.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts;  ISA Server services


Click to select which services to start or restart.


Displays a list of ISA Server services. Select which services to stop or start.

For more information, see ISA Server services


Specifies that the local system account will run the program. You can configure which credentials should be used when an application is run. The specified user should have Logon as batch job privileges. For more information, For more information, see Logon rights in Windows 2000 Server help.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts


Specifies that the user account specified will run the program. You can configure which credentials should be user when an application is run. The specified user should have Logon as batch job privileges. For more information, For more information, see Logon rights in Windows 2000 Server help.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts


Provides a space for you to type the name of the user account that will run the program. Be sure that the specified user has appropriate permissions to run the program.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts


Provides a space for you to type the password for the user account.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts


Provides a space for you to retype the password for the user account.

An event is an action that occurs as the result of an exception in ISA Server. An alert notifies you when specified events occur and can be configured to trigger a series of actions as a result of these events.

For more information, see Configuring alerts


Click to select the user account.


Provides a schedule table for you to create or modify a schedule. A dark cell means the rule is in effect during that hour on that day. A white cell means the rule is not in effect.

A schedule is one of the predefined policy elements you use in creating rules.

For more information, see To create a schedule;  To modify a schedule


Specifies when the rule is active, according to selections made on the schedule.


Specifies when the rule is in effect. A dark cell in the table means the rule is active during that hour. A white cell means the rule is inactive.


Specifies when the rule is in effect. A dark cell in the table means the rule is active during that hour. A white cell means the rule is inactive.


Provides a space for you to type the name of the schedule.

A schedule is one of the predefined policy elements you use in creating rules.

For more information, see Configuring schedules


(optional) Provides a space for you to type in a description of the schedule.


Provides a schedule table for you to create or modify a schedule. A dark cell means the rule is in effect during that hour on that day. A white cell means the rule is not in effect.

A schedule is one of the predefined policy elements you use in creating rules.

For more information, see To create a schedule;  To modify a schedule


Specifies when the rule is active, according to selections made on the schedule.


Specifies when the rule is in effect. A dark cell in the table means the rule is active during that hour. A white cell means the rule is inactive.


Specifies when the rule is in effect. A dark cell in the table means the rule is active during that hour. A white cell means the rule is inactive.


Provides a space for you to type the outbound bandwidth. This is the bandwidth on the external network cards that will be allocated for requests from internal clients for objects on the Internet. Bandwidth rates can be set from 1 to 200.

Bandwidth priority can be used to configure bandwidth rules, which provide control over how much bandwidth is allowed for a specific network connection.

For more information, see Configuring bandwidth priorities


Provides a space for you to type the inbound bandwidth. This is the bandwidth on the internal network cards that will be allocated for requests from external clients for objects on the local network. Bandwidth rates can be set from 1 to 200.

Bandwidth priority can be used to configure bandwidth rules, which provide control over how much bandwidth is allowed for a specific network connection.

For more information, see Configuring bandwidth priorities


Provides a space for you to type the name of the bandwidth priority.

Bandwidth priority can be used to configure bandwidth rules, which provide control over how much bandwidth is allowed for a specific network connection.

For more information, see Configuring bandwidth priorities


(Optional) Provides a space for you to type a description of the bandwidth priority.


Provides a space for you to type the outbound bandwidth priority. ISA Server allocates this bandwidth for requests from internal clients for objects on the Internet. The bandwidth priority can be any number between 1 and 200.

Bandwidth priority can be used to configure bandwidth rules, which provide control over how much bandwidth is allowed for a specific network connection.

For more information, see Configuring bandwidth rules;  Configuring bandwidth priorities


Provides a space for you to type the inbound bandwidth priority. ISA Server allocates this bandwidth for requests from external clients for objects on the local network. The bandwidth priority can be any number between 1 and 200.

Bandwidth priority can be used to configure bandwidth rules, which provide control over how much bandwidth is allowed for a specific network connection.

For more information, see Configuring bandwidth rules;  Configuring bandwidth priorities


Displays the list of computers in the destination set.

Computers can be specified by domain name or by a range of  Internet protocol (IP) addresses. You can use an asterisk (*) as a wildcard when you specify the computer name. For example, to specify all computers in the microsoft.com domain, enter the destination as *.microsoft.com. Note that the asterisk can appear only at the start of the domain name, and can be specified only once in the name or by computer name.

A destination set consists of one or more computers that are defined as a group for the purpose of simplifying application of rules. Host and path names for destination sets are not case-sensitive.

For more information, see Configuring destination sets


Click to add a computer to the destination set.


Click to modify a computer or a range of computers in the destination set.


Click to remove a computer or a range of computers from the destination set.


Provides a space to type the name of the destination set.

Computers can be specified by domain name or by a range of  Internet protocol (IP) addresses. You can use an asterisk (*) as a wildcard when you specify the computer name. For example, to specify all computers in the microsoft.com domain, enter the destination as *.microsoft.com. Note that the asterisk can appear only at the start of the domain name, and can be specified only once in the name or by computer name.

Destination sets include one or more computers or directories on specific computers. Host and path names for destination sets are not case-sensitive.

For more information, see Configuring destination sets


(Optional) Provides a space for you to type a description of the destination set.


Displays the list of computers in the destination set.

Computers can be specified by domain name or by a range of  Internet protocol (IP) addresses. You can use an asterisk (*) as a wildcard when you specify the computer name. For example, to specify all computers in the microsoft.com domain, enter the destination as *.microsoft.com. Note that the asterisk can appear only at the start of the domain name, and can be specified only once in the name or by computer name.

A destination set consists of one or more computers that are defined as a group for the purpose of simplifying application of rules.

For more information, see Configuring destination sets


Click to add a computer or range of computers to the destination set.


Click to modify a computer or range of computers in the destination set.


Click to remove a computer or range of computers from the destination set.


Provides a space for you to type the name of a computer to include in the destination set. For site and content rules, you will typically specify external computers. For Web publishing rules, you will typically specify internal computers.

Computers can be specified by domain name or by a range of  Internet protocol (IP) addresses. You can use an asterisk (*) as a wildcard when you specify the computer name. For example, to specify all computers in the microsoft.com domain, enter the destination as *.microsoft.com. Note that the asterisk can appear only at the start of the domain name, and can be specified only once in the name or by computer name.

A destination set consists of one or more computers that are defined as a group for the purpose of simplifying application of rules.

For more information, see Configuring destination sets


Click to select a computer to add to the destination set.


Provides a space for you to type the first IP address in the destination set. For site and content rules, you will typically specify IP addresses of external computers. For Web publishing rules, you will typically specify IP addresses of internal computers.

Computers can be specified by domain name or by a range of  Internet protocol (IP) addresses. You can use an asterisk (*) as a wildcard when you specify the computer name. For example, to specify all computers in the microsoft.com domain, enter the destination as *.microsoft.com. Note that the asterisk can appear only at the start of the domain name, and can be specified only once in the name or by computer name.

A destination set consists of one or more computers that are defined as a group for the purpose of simplifying application of rules. For more information, see Configuring destination sets


(Optional) Provides a space for you to type the last IP address in the new destination set range. All the computers with addresses in that range of IP addresses will be included in the destination set. If you do not type an IP address here, only one computer is added to the destination set,

Computers can be specified by domain name or by a range of  Internet protocol (IP) addresses. You can use an asterisk (*) as a wildcard when you specify the computer name. For example, to specify all computers in the microsoft.com domain, enter the destination as *.microsoft.com. Note that the asterisk can appear only at the start of the domain name, and can be specified only once in the name or by computer name.

A destination set consists of one or more computers that are defined as a group for the purpose of simplifying application of rules.

For more information, see Configuring destination sets


(Optional) Provides a space for you to type a path to a specific folder on the specified computer to define the new destination set. . Host and path names for destination sets are not case-sensitive.

To include all the files in the folder as part of the destination set, use this format: /folder_name/*

To include a single file in the folder as part of the destination set, use this format: /folder_name/file_name

A destination set consists of one or more computers that are defined as a group for the purpose of simplifying application of rules.

For more information, see Configuring destination sets


Click to add a computer to the destination set by specifying a computer name.


Click to add a computer to the destination set by specifying an IP address, or a range of IP addresses for more than one computer.


Displays a list of Internet protocol (IP) addresses in the client address set.

For access policy rules, a client address set consists of one or more internal client computers that are defined as a group for the purpose of simplifying application of rules for clients. For server publishing rules, client sets are usually used to define a set of IP addresses for external clients, usually located on the Internet, for the purpose of allowing these clients access to an internal server.

For more information, see Configuring client address sets


Click to add a computer or range of computers to the client address set.


Click to modify a computer or range of computers in the client address set.


Click to remove a computer or range of computers from the client address set.


Provides a space for you to type the name of a computer to include in the client address set.

For access policy rules, a client address set consists of one or more internal client computers that are defined as a group for the purpose of simplifying application of rules for clients. For server publishing rules, client sets are usually used to define a set of IP addresses for external clients, usually located on the Internet, for the purpose of allowing these clients access to an internal server.

For more information, see Configuring client address sets


(Optional) Provides a space for you to type a description of the client address set.


Displays a list of IP addresses of all clients included in the client address set.

For access policy rules, a client address set consists of one or more internal client computers that are defined as a group for the purpose of simplifying application of rules for clients. For server publishing rules, client sets are usually used to define a set of IP addresses for external clients, usually located on the Internet, for the purpose of allowing these clients access to an internal server.

For more information, see Configuring client address sets


Click to add a client or clients by IP address.


Click to edit IP address or IP addresses included in the client address set.


Click to delete IP address or range of addresses that are included in the client address set.


Provides a space for you to type the first IP address in the client address set range. All computers with addresses in this range of IP addresses will be included in the client address set.

For access policy rules, a client address set consists of one or more internal client computers that are defined as a group for the purpose of simplifying application of rules for clients. For server publishing rules, client sets are usually used to define a set of IP addresses for external clients, usually located on the Internet, for the purpose of allowing these clients access to an internal server.

For more information, see Configuring client address sets


Provides a space for you to type the last IP address in the client address set range. All computers with addresses in that range of IP addresses will be included in the client address set.

For access policy rules, a client address set consists of one or more internal client computers that are defined as a group for the purpose of simplifying application of rules for clients. For server publishing rules, client sets are usually used to define a set of IP addresses for external clients, usually located on the Internet, for the purpose of allowing these clients access to an internal server.

For more information, see Configuring client address sets


Displays the name of the vendor that developed this application filter.


Displays the application filter version.


Displays a description for the application filter.


Specifies that the application filter is enabled.


Displays the name of the application filter.

Application filters can access the datastream or datagrams associated with a session within the Firewall Service, and perform protocol-specific or system specific tasks, such as authentication or virus check.

For more information, see Application filters


Click to redirect Hypertext Transfer Protocol (HTTP) requests to the local Web Proxy server.

The HTTP filter forwards HTTP requests from Firewall and SecureNAT clients to the Web Proxy service by directing the request to a local ISA Server, to the requested Web server or by rejecting requests from these clients.

For more information, see HTTP filter;  Application filters


Click to redirect Hypertext Transfer Protocol (HTTP) requests to the requested Web server, if the local Web Proxy server is not available.

The HTTP filter forwards HTTP requests from Firewall and SecureNAT clients to the Web Proxy service by directing the request to, a local ISA Server, to the requested Web server or by rejecting requests from these clients.

For more information, see HTTP filter;  Application filters


Click to direct Hypertext Transfer Protocol (HTTP) requests to the requested Web server.

The HTTP filter forwards HTTP requests from Firewall and SecureNAT clients to the Web Proxy service by directing the request to a local ISA Server, to the requested Web server or by rejecting requests from these clients.

For more information, see HTTP filter;  Application filters


Click to reject Hypertext Transfer Protocol (HTTP) requests from Firewall and SecureNAT clients.

The HTTP filter forwards HTTP requests from Firewall and SecureNAT clients to the Web Proxy service by directing the request to a local ISA Server, to the requested Web server or by rejecting requests from these clients.

For more information, see HTTP filter;  Application filters


Provides a space for you to type the name of the protocol definition and secondary connections.

A protocol definition consists of a port, direction and protocol type. You can create protocol definitions, and ISA Server also has numerous predefined protocol definitions. Protocol definitions that are installed with ISA Server or with extensions cannot be modified.

For more information, see Configuring protocol definitions


(Optional) Provides a space for you to type a description.


Displays the port number for this protocol definition.

A protocol definition consists of a port, direction and protocol type. You can create protocol definitions, and ISA Server also has numerous predefined protocol definitions. Protocol definitions that are installed with ISA Server or with extensions cannot be modified.

For more information, see Configuring protocol definitions


Displays the low-level protocol used for the protocol definition.

A protocol definition consists of a port, direction and protocol type. You can create protocol definitions, and ISA Server also has numerous predefined protocol definitions. Protocol definitions that are installed with ISA Server or with extensions cannot be modified.

For more information, see Configuring protocol definitions


Specifies the direction of the communication for this protocol definition.

A protocol definition consists of a port, direction and protocol type. You can create protocol definitions, and ISA Server also has numerous predefined protocol definitions. Protocol definitions that are installed with ISA Server or with extensions cannot be modified.

For more information, see Configuring protocol definitions


Displays a list of secondary connections specified for this protocol definition.

A secondary connection is the range of ports numbers, protocol and direction used for additional connections or packets that follow the initial connection.

For more information, see Configuring protocol definitions


Click to add a secondary connection for this protocol definition.


Click to modify the secondary connection for this protocol definition.


Click to remove the secondary connection for this protocol definition.


Displays a list of secondary connections specified for this protocol definition.

A secondary connection is the range of ports numbers, protocol and direction used for additional connections or packets that follow the initial connection.

For more information, see Configuring protocol definitions


Provides a space for you to type the first port number in the range of ports used for the secondary connection.

For more information, see Configuring protocol definitions


Provides a space for you to type the last port number in the range of ports used for the secondary connection. If the secondary connection should allow only one port, then type the same number as From Port.

For more information, see Configuring protocol definitions


Displays a list of low-level protocols, either TCP or UDP.

For more information, see Configuring protocol definitions


Displays a list of directions for the secondary connection, either inbound or outbound.

For more information, see Configuring protocol definitions


Displays the total cache size of all the servers.

For more information, see Configuring cache drives


Specifies whether Hypertext Transfer Protocol (HTTP) caching is enabled.

When caching is enabled, HTTP objects are stored in the cache and expire in accordance with the specified policy.

For more information, see Configuring expiration policy


ISA Server can keep expired objects in the cache for a specified amount of time if the source Internet site for an object is unavailable.

An expired object is an object whose time-to-live period (TTL) has run out. Expiration policy balances your organization's need for fresh, current data against network performance.

For more information, see Configuring expiration policy


Specifies that objects will be updated in the cache relatively frequently. If you select this option, objects in the cache will be more recent, although there may be some degradation in network performance because objects are retrieved more regularly from the Internet.

For more information, see Configuring expiration policy


Specifies that objects will be updated in the cache so that objects in the cache will be fairly current without degrading network performance.

For more information, see Configuring expiration policy


Specifies that objects will be updated in the cache relatively infrequently. If you select this option, objects in the cache will be less current, but network performance will improve.

For more information, see Configuring expiration policy


Specifies that ISA Server will use custom settings to determine how often the cache is refreshed.

ISA Server can keep expired objects in the cache for a specified amount of time if the source Internet site for an object is unavailable. An expired object is an object whose time-to-live period (TTL) has run out. Expiration policy balances your organization's need for fresh, current data against network performance.

For more information, see Configuring expiration policy


Specifies custom settings for expiration policy of objects in the cache.

ISA Server can keep expired objects in the cache for a specified amount of time if the source Internet site for an object is unavailable. An expired object is an object whose time-to-live period (TTL) has run out. Expiration policy balances your organization's need for fresh, current data against network performance.

For more information, see Configuring expiration policy


Specifies that all cached objects expire immediately, with a zero time-to-live (TTL) period.

For more information, see Configuring expiration policy


Provides a space for you to specify how long the Hypertext Transfer Protocol (HTTP) objects remains in the cache, expressed as a percentage of the time of the content's existence. The higher the percentage, the less frequently the cache is updated.

For more information, see Configuring expiration policy


Provides a space for you to type the minimum amount of time that the Hypertext Transfer Protocol (HTTP) objects remain in the cache.

For more information, see Configuring expiration policy


Provides a space for you to type the maximum amount of time that the Hypertext Transfer Protocol (HTTP) objects remain in the cache.

For more information, see Configuring expiration policy


Lists the available time units for maximum expiry time of cached Hypertext Transfer Protocol (HTTP) objects.


Click to reset the Hypertext Transfer Protocol (HTTP) cache expiration policy to the default value, Normal (Equally Important).


Lists the available time units for minimum expiry time of cached Hypertext Transfer Protocol (HTTP) objects.


Specifies whether File Transfer Protocol (FTP) caching is enabled.

 When caching is enabled, FTP objects are stored in the cache and expire in accordance with the specified policy.

For more information, see Configuring expiration policy


Provides a space for you to type the minutes that File Transfer Protocol (FTP) objects should remain in the cache. The default time-to-live (TTL) setting is 1440 minutes.


Click to reset File Transfer Protocol (FTP) caching expiration policy to 1440 minutes, which is the default setting.


Lists the available time units for expiry time of File Transfer Protocol (FTP) objects.


Specifies whether ISA Server automatically caches new content as expiration of old content is near, thus ensuring freshness of the most popular Internet objects. If a dial-up connection is in use, then the computer will dial out to the ISP to retrieve the content.

Active caching is configured according to the chosen policy and automatically retrieves frequently accessed content during off-peak hours.

For more information, see Configuring active caching


Specifies the expiration policy of the pre-caching function.

ISA Server can automatically cache new content as expiration of old content is near, thus ensuring freshness of the most popular Internet objects.

Active caching is configured according to the chosen policy and automatically retrieves frequently accessed content during off-peak hours.

For more information, see Configuring active caching


Specifies that ISA Server should pre-cache frequently. In this way, the client response will be faster, although the network performance may degrade.

ISA Server can automatically cache new content as expiration of old content is near, thus ensuring freshness of the most popular Internet objects.

Active caching is configured according to the chosen policy and automatically retrieves frequently accessed content during off-peak hours.

For more information, see Configuring active caching


Specifies that ISA Server should pre-cache so that clients will perceive fast response without degrading network performance.

For more information, see Configuring active caching


Specifies that ISA Server should pre-cache infrequently. In this way, the network performance will not degrade, although objects that are requested by the client may not be in the cache.

For more information, see Configuring active caching


Click to reset active caching to Normally, which is the default setting.


Provides a space for you to type the maximum size for a cached file.

For more information, see Configuring negative caching


Specifies whether ISA Server can cache objects that do not have a last modification time in the header. Dates and times in the header indicate when a request is received and a time for the request to expire on the network.

For more information, see Configuring negative caching


Specifies whether ISA Server can cache objects that do not include an "OK" response (HTTP code 200).

For more information, see Configuring negative caching


Specifies whether ISA Server can cache objects with URLs that contain question marks. Question marks indicate search response content.

For more information, see Configuring negative caching


Allows you to specify how ISA Server should return objects to the client if the requested Web server is down, and the requested object already expired.

For more information, see Routing Web requests


Specifies that ISA Server should return the object only if it is in the cache. If it is not in the cache, it does not connect to the Internet to retrieve the object, and an error message is returned to the client.

For more information, see Routing Web requests


Specifies that if the source Web server of an expired object cannot be contacted, ISA Server should return the expired object from the cache, in accordance with the specified conditions.

For more information, see Routing Web requests


Provides a space for you to type the maximum period in which ISA Server returns the expired object.

The period is expressed in a maximum percentage of the original time to live (TTL) setting.

For more information, see Routing Web requests


Provides a space for you to type the maximum number of minutes that can pass before ISA Server will return the expired object.

For more information, see Routing Web requests


Click to set the following default policy:

Cache items if the last modification time is not specified

Cache items that do not have a 200 0K response

Do not cache URLs containing question marks

Return the expired object only if it expired less than 50% of the original time to live (TTL) but no more than 60 minutes.

For more information, see Routing Web requests


Specifies whether a size limit of Internet objects in the cache is set.

For more information, see Configuring negative caching


Lists the available measurement units.


Provides space to type the percentage of available memory (RAM) that should be used for caching.  The default is 50%.


Provides space to type the maximum size of a URL in the memory cache (RAM).


Provides space to type the maximum size of a URL in the memory cache (RAM).


Displays the name.


Lists the configuration of all the cache drives on the server, including drive letter, type of drive, size of drive, and cache size.

For more information, see Configuring cache drives


Provides a space for you to type the size of the cache on the selected drive in the drive table. Only NTFS drives can be used for caching.

For more information, see Configuring cache drives


Click to apply the change in the cache file size.


Displays the total size of the disk on the server.


Displays the total size of all the cache drives on the server.


Specifies whether the Firewall client setup process may configure Web browser settings.

For more information, see To enable Web browser configuration during client setup;  Configuring Web Proxy clients


Specifies that the client computer should automatically attempt to find the ISA Server computer.

When enabled, you can configure the DNS or DHCP server to include WPAD (Web Proxy Automatic Discovery). The Web Proxy client will use the WPAD feature to automatically discover which ISA Server computer to use for Web requests. This assures that roaming clients will always connect to the appropriate ISA Server computer when logging on to the Internet, cutting-down on time-consuming adjustments. This is relevant only to Internet Explorer 5 and future supporting browsers.

. For more information, see Automatic discovery


Specifies whether the Web browser of the client should use configuration information that is contained in the specified file, the automatic configuration script.

This configuration script will automatically be available to the Web browser, and means you can easily update all Web browser settings without having to reconfigure each individual Web browser.

For more information, see Configuring Web Proxy clients


Specifies that the default client configuration script should be used. During setup, ISA Server creates a default URL which points to the location of the automatic configuration script.

This default configuration script will automatically be available to the Web browser, and means you can easily update all client Web browser settings without having to reconfigure each individual Web browser.

For more information, see Configuring Web Proxy clients.


Specifies that a custom client configuration script should be used.

As an alternative to the default configuration script, you can manually construct your own configuration script. When the Web browser looks for the configuration script, your custom script will be returned to the browser.

For more information, see Configuring Web Proxy clients


Provides a space for you to type a URL or file name of the customized client configuration script.

The file includes configuration settings for the proxy server. As an alternative to the default configuration script, you can manually construct your own configuration script. When the Web browser looks for the configuration script, your custom script will be returned to the browser.

For more information, see Configuring Web Proxy clients


Provides a space for you to type the name of the ISA Server computer, array, DNS name or IP address to which the Web Proxy clients should connect.

The server name should be unique. Using the Fully Qualified Domain Name (FQDN) will avoid any conflict with duplicated server names.

For more information, see Configuring Web Proxy clients


Click to select a computer to which the Web Proxy clients should connect.


Specifies the port number that Web Proxy clients should use when sending requests to the specified ISA Server computer.

This should be the port on which the ISA Server computer is listening for outgoing Web requests. By default, this is set to port 8080.

For more information, see Configuring Web Proxy clients


Displays a list of computers and domains that the client can access directly, without using ISA Server.

 For more information, see To configure a server for direct access


Click to add a range of IP addresses or domain names to the list of computers that the client can access directly.


Click to modify a range of IP addresses or domain names in the list of computers that the client can access directly.


Click to add a range of IP addresses or domain names from the list of computers that the client can access directly


Specifies whether the client should bypass the ISA Server when accessing the local server.

 For more information, see To configure a server for direct access


Specifies whether the client can directly access computers defined in the local domain table (LDT).

The LDT lists all the computer names in the local network that are served by the ISA Server.

For more information, see Configuring the local domain table


Specifies whether a backup route should be used to service client requests if the ISA Server computer is not available.

For more information, see To configure a back-up route for Web requests


Specifies that for a back-up route, the Web Proxy client should retrieve the request directly from the Internet, if the ISA Server computer is unavailable.

For more information, see To configure a back-up route for Web requests


Specifies that, for a backup route, the request should be sent to an alternate server if ISA Server is unavailable.

For more information, see To configure a back-up route for Web requests


Click to find an alternate server, if the ISA Server is unavailable.


Click to verify whether the server that is specified in the backup route is responding.


Specifies which servers the client can access directly.

For more information, see To configure a server for direct access


Provides a space for you to type the first IP address in the range of computers that the client can access directly.

For more information, see To configure a server for direct access


Provides a space for you to type the last IP address in the range of computers that the client can access directly.

For more information, see To configure a server for direct access


Specifies that the computers in the domain are accessed directly and not via the ISA Server computer.

For more information, see To configure a server for direct access


Provides a space to type the name of a computer in the domain that is accessed directly and not via the ISA Server computer.

For more information, see To configure a server for direct access


Click to select a domain for direct access.


Provides a space for you to type the name of the ISA Server computer or array to which Firewall clients should connect.

The server name should be unique. Using the Fully Qualified Domain Name (FQDN) will avoid any conflict with duplicated server names.

For more information, see Firewall clients


Click to enable automatic discovery.

If enabled, the Firewall client will use automatic discovery to locate the appropriate ISA Server computer.

For more information, see Automatic discovery


Specifies that the client computer should automatically attempt to find the ISA Server computer, using an automatic discovery setting on the DNS or DHCP Server. When enabled, you can configure the DNS or DHCP server to include WPAD (Web Proxy Automatic Discovery) and WSPAD (Winsock Proxy Automatic Discovery) entries. This assures that roaming clients will always connect to the appropriate ISA Server computer when logging on to the Internet, cutting-down on time-consuming adjustments.

With automatic discovery enabled, Firewall and SecureNAT clients will use the WSPAD feature to discover automatically which ISA Server computer to use for Winsock requests. With automatic discovery enabled, Web Proxy clients will use the WPAD feature to automatically discover which ISA Server computer to use for Web requests.

For more information, see Automatic discovery


Provides a space for you to type the IP address of the ISA Server computer or array to which Firewall clients should connect.

For more information, see Firewall clients


Specifies the name of the ISA Server computer or array to which Firewall clients should connect.

For more information, see Firewall clients


Click to find a computer or array to which Firewall clients should connect.


Specifies the IP address of the ISA Server or array to which Firewall clients should connect.


Specifies that the ISA Server computer should use its primary method of connecting to the Internet when retrieving objects for Firewall or SecureNAT clients.

For more information, see Routing requests from Firewall and SecureNAT clients


Specifies that the ISA Server computer should forward requests from Firewall or SecureNAT clients to an upstream server. The upstream server must be either an ISA Server computer or a Microsoft Proxy Server 2.0 computer.

For more information, see Routing requests from Firewall and SecureNAT clients


Specifies whether the ISA Server computer should dial to connect to an upstream server when retrieving objects for Firewall or SecureNAT clients.

For more information, see Routing requests from Firewall and SecureNAT clients


Displays a list of dial-up entries that are configured on all the ISA Server computers in the array. If no dial-up entries are configured, this list is empty.

For more information, see Routing requests from Firewall and SecureNAT clients


Provides a space for you to type the name of the upstream server. The upstream server must be either an ISA Server computer or a Microsoft Proxy Server 2.0 computer.

The server name should be unique. Using the Fully Qualified Domain Name (FQDN) will avoid any conflict with duplicated server names.

For more information, see Routing requests from Firewall and SecureNAT clients


Click to find an upstream server or ISA array.


Click to find a user account.


Specifies whether credentials should be passed to the upstream server when chaining requests. If the upstream server requires authentication, then you must select this option and specify a user account with permissions to access the upstream server.

For more information, see Routing requests from Firewall and SecureNAT clients


Provides a space for you to type the name of the user account that has permissions to access the upstream server.

For more information, see Routing requests from Firewall and SecureNAT clients


Provides a space for you to type the password of the user account that has permissions to access the upstream server.

For more information, see Routing requests from Firewall and SecureNAT clients


Provides a space for you to type the password for the user account.

For more information, see Routing requests from Firewall and SecureNAT clients


Specifies whether the ISA Server computer should dial out to the Internet when retrieving objects for Firewall or SecureNAT clients.

For more information, see Routing requests from Firewall and SecureNAT clients


Displays a list of dial-up entries configured on all the ISA Server computers in the array. If no dial-up entries are configured, this list is empty.

For more information, see Routing requests from Firewall and SecureNAT clients


Applies the rule to destinations.

All internal destinations applies the rule to all computers that are specified in the local address table or the local domain table. All external destinations applies  the rule to all computers that are not specified in the local address table or the local domain table. Selected destination set applies the rule to all computers included in the destination set specified. All destinations except selected set applies the rule to all computers except for those in the specified destination set.

For more information, see Configuring destination sets


Displays a list of destination sets defined. If the server belongs to an array, the list also includes any enterprise-level destination sets.

A destination set consists of one or more computers that are defined as a group for the purpose of simplifying application of rules. Host and path names for destination sets are not case-sensitive.

For more information, see Configuring destination sets


Click to add a new destination set.


Displays the scope of the selected destination set, array or enterprise. Enterprise policy elements can be applied to array-level rules.

A destination set consists of one or more computers that are defined as a group for the purpose of simplifying application of rules.

For more information, see Configuring destination sets


(Optional) Displays a description of the destination set.


Displays the list of computers in the destination set. Destinations can be specified by computer names or by IP addresses. A destination set consists of one or more computers that are defined as a group for the purpose of simplifying application of rules.

For more information, see Configuring destination sets


Displays a list of defined schedules. If the server belongs to an array,  the list also includes any enterprise-level schedules. A schedule is a predefined policy element that determines when a rule is put into effect.

 For more information, see Configuring schedules


Click to create a new schedule


Displays the scope of the selected schedule.


Displays a description of the schedule, if one exists.


Displays the schedule. A dark cell means the rule is in effect during that hour on that day. A white cell means the rule is not in effect.

For more information, see To modify a schedule


Specifies when the rule is active, according to the schedule.


Specifies when the rule is in effect. A dark cell in the table means the rule is active during that hour. A white cell means the rule is inactive.


Specifies when the rule is in effect. A dark cell in the table means the rule is active during that hour. A white cell means the rule is inactive.


Specifies that a request will be allowed if it meets the conditions of the rule.

You can configure rules to meet specific security needs. Rules can be combined together to create an access policy.

For more information, see Access policy rules


Specifies that  a request will be denied if it  meets the conditions of the rule.

You can configure rules to meet specific security needs. Rules can be combined together to create an access policy.

For more information, see Access policy rules


Provides a space for you to type the alternate URL that is returned to users whose Hypertext Transfer Protocol (HTTP) requests are denied.

The URL must be accessible to the clients or users. The URL should either be on a local computer, or a rule must explicitly allow access to the URL. You can configure rules to meet specific security needs. Rules can be combined together to create an access policy.

For more information, see Site and content rules


Specifies that, when a Hypertext Transfer Protocol (HTTP) request is rejected, ISA Server should return an object at a different URL to the user.

You can configure rules to meet specific security needs. Rules can be combined together to create an access policy.

For more information, see Site and content rules


Specifies that the rule applies to all requests from any computer or any user. If you configured ISA Server to always authenticate users, then the rule applies only to authenticated users.

For more information, see Rules and authentication


Specifies that the rule applies to requests from specific users or groups.

Note: If you select this option you cannot limit the rule to specific IP addresses. This may have implications for Secure Network Address Translation (SecureNAT) clients, which can only be specified by IP address.  You can create client address sets to group computers together by IP address.

For more information, see Rules and authentication


Specifies that the rule applies to requests from specific client address sets. Client address sets include IP addresses of one or more computers.

For access policy rules, a client address set consists of one or more internal client computers that are defined as a group for the purpose of simplifying application of rules for clients. For server publishing rules, client sets are usually used to define a set of IP addresses for external clients, usually located on the Internet, for the purpose of allowing these clients access to an internal server.

For more information, see Configuring client address sets


Displays a list of client address sets to which the rule applies.

For access policy rules, a client address set consists of one or more internal client computers that are defined as a group for the purpose of simplifying application of rules for clients. For server publishing rules, client sets are usually used to define a set of IP addresses for external clients, usually located on the Internet, for the purpose of allowing these clients access to an internal server.

For more information, see Configuring client address sets


Displays a list of user accounts and groups to which the rule applies.


Displays a list of client address sets to which the rule does not apply.

For access policy rules, a client address set consists of one or more internal client computers that are defined as a group for the purpose of simplifying application of rules for clients. For server publishing rules, client sets are usually used to define a set of IP addresses for external clients, usually located on the Internet, for the purpose of allowing these clients access to an internal server.

For more information, see Configuring client address sets


Displays a list of users or groups to which the rule does not apply.


Click to add a user or group to which the rule should be applied.


Click to remove a user, group, or client address set from the list.


Click to add a user, group, or client address set from the list.


Click to remove a user, group, or client address set from the list.


Click to For more information, see the properties of the selected client address set.


Click to For more information, see the properties of client address sets to which the rule does not apply.


Specifies that the request receive the default scheduling priority, as specified by the operating system.

Bandwidth rules allow the setting of bandwidth priorities. A default bandwidth policy exists, or you may create your own.

For more information, see Configuring bandwidth rules;  Configuring bandwidth priorities


Specifies that the request receives the selected bandwidth priority.

Bandwidth rules allow the setting of bandwidth priorities. You can use the default bandwidth policy or you may create your own.

For more information, see Configuring bandwidth rules;  Configuring bandwidth priorities


Displays a list of defined bandwidth priorities.

For more information, see Configuring bandwidth rules;  Configuring bandwidth priorities


Click to create a new bandwidth priority.


Displays a description of the bandwidth priority.


Displays the outbound bandwidth priority. This is the bandwidth on the external network cards that will be allocated for requests from internal clients for objects on the Internet.

Bandwidth rules allow the setting of bandwidth priorities. You can use the default bandwidth policy or you may create your own.

For more information, see Configuring bandwidth rules;  Configuring bandwidth priorities


Displays the inbound bandwidth priority. This is the bandwidth on the internal network cards that will be allocated for requests from external clients for objects on the local network.

Bandwidth priorities define the priority level applied to connections that pass through ISA Server.

For more information, see Configuring bandwidth rules;  Configuring bandwidth priorities


Specifies that the rule applies to all content located on the selected destination sets.

Specific security and control needs can be met by configuring rules. Rules can be created and then applied to create an access policy. Content groups specify a set of file and MIME types. These content groups are used when defining site and content rules, to control Web access. A complete list of MIME types and file extensions can be found on the linked page.

For more information, see Configuring content groups


Specifies that the rule applies only to the types of content selected..

Specific security and control needs can be met by configuring rules. Rules can be created and then applied to create an access policy Content groups specify a set of file and MIME types. These content groups are used when defining site and content rules, to control Web access.  A complete list of MIME types and file extensions can be found on the linked page.

For more information, see ISA Server rules;  Configuring content groups


Displays a list of content groups. If the server belongs to an array, the list also includes any enterprise-level content groups.

Content groups specify a set of file and MIME types. These content groups are used when defining site and content rules, to control Web access. A complete list of MIME types and file extensions can be found on the linked page.

For more information, see Configuring content groups


Click to select all the available content groups.


Click to clear all the selected content groups.


Click to create a new content group.


Click to view the properties of the selected content group.


Specifies that only selected content groups should be displayed in the list.

For more information, see Configuring content groups


Specifies that the rule applies to the protocols selected.

All IP traffic includes all communication with the ISA Server computer, even using protocols not specifically defined and listed by ISA Server.  Selected protocols can include protocols defined by ISA Server, or customized protocol.

You can meet specific security and control needs by configuring rules. A set of rules makes up an access policy.

For more information, see ISA Server rules


Displays a list of protocol definitions.

Protocol rules determine which protocols clients can use to access the Internet. Protocol rules can be applied to a specific set of protocol definitions.

For more information, see Protocol rules;  Configuring protocol definitions


Click to select all the protocol definitions listed.


Click to clear the selection.


Click to create a new protocol definition.


Click to view the protocol definition properties.


Specifies that only selected protocol definitions should be displayed in the list.

Protocol rules determine which protocols clients can use to access the Internet. Protocol rules can be applied to a specific set of protocol definitions.

For more information, see Protocol rules;  Configuring protocol definitions


Specifies that ISA Server send requests from Web Proxy clients directly to the Internet.

Routing rules determine whether a Web Proxy client request is retrieved directly, or is sent to another upstream proxy server, or to an alternate destination.

For more information, see Routing Web requests


Specifies that ISA Server send requests from Web Proxy clients to an upstream server for processing. The upstream server will determine if the request is allowed or denied. The upstream server must be either an ISA Server computer or a Microsoft Proxy Server 2.0 computer.

Routing rules determine whether a Web Proxy client request is retrieved directly, or is sent to another upstream proxy server, or to an alternate destination.

For more information, see Routing Web requests


Specifies that ISA Server routes requests from Web Proxy clients to an alternate destination.

Routing rules determine whether a Web Proxy client request is retrieved directly, or sent to another upstream proxy server, or to an alternate destination.

For more information, see Routing Web requests


Click to configure which upstream server fulfills the requests.


Lists ISA Server options for fulfilling requests if the primary route is unavailable. If you select Upstream proxy server, you must specify which server will be used. The upstream server must be either an ISA Server computer or a Microsoft Proxy Server 2.0 computer.

Routing rules determine whether a Web Proxy client request is retrieved directly, or sent to another upstream proxy server, or to an alternate destination.

For more information, see Routing Web requests


Click to configure which upstream server fulfills the requests.


Provides a space for you to type the URL of the alternate destination for the request.

Routing rules determine whether a Web Proxy client request is retrieved directly, or to another upstream proxy server, or to an alternate destination.

For more information, see Routing Web requests


Click to find the URL of an alternate destination for the request.


Specifies whether ISA Server should use a dial-up connection when connecting to the primary route.

Routing rules determine whether a Web Proxy client request is retrieved directly, or is sent to another upstream Proxy server, or to an alternate destination.

For more information, see Routing Web requests


Displays a list of dial-up entries configured on all of the ISA Server computers in the array. If no dial-up entries are configured, this list is empty.

For more information, see Routing Web requests


Specifies whether ISA Server should use a dial-up connection when connecting to the backup route.

For more information, see Routing Web requests


Displays a list of dial-up entries configured on all the ISA Server computers in the array. If no dial-up entries are configured, this list is empty.

 For more information, see Routing Web requests


Provides a space for you to type the port number of the alternate destination.

Routing rules determine whether a Web Proxy client request is retrieved directly, or is to another upstream proxy server, or to an alternate destination.

For more information, see Routing Web requests


Provides a space for you to type the Secure Sockets Layer (SSL) port number of the alternate destination.

Routing rules determine whether a Web Proxy client request is retrieved directly, or is sent to another upstream Proxy server, or to an alternate destination.

For more information, see Routing Web requests


Provides a space for you to type the name of the upstream server or ISA Server array.

The server name should be unique. Using the Fully Qualified Domain Name (FQDN) will avoid any conflict with duplicated server names.

The upstream server must be either an ISA Server computer or a Microsoft Proxy Server 2.0 computer.

For more information, see Routing Web requests


Provides a space for you to type the port to use when connecting to the upstream server.

 For more information, see Routing Web requests


Provides a space for you to type the Secure Sockets Layer (SSL) port that should be used when connecting to the upstream server.

For more information, see Routing Web requests


Specifies whether the ISA Server should determine whether the upstream server is an array member. If it is, then it also points to the other member servers in the array. The local ISA Server uses this information to retrieve objects from the upstream array. The upstream server must be either an ISA Server computer or a Microsoft Proxy Server 2.0 computer.

For more information, see To configure a primary route for Web requests


Provides a space for you to type the URL to use when checking the upstream server. ISA Server automatically constructs a URL if you type the server name. You can then modify this URL, if needed.


Specifies whether credentials will be used when communicating with the upstream server.

For more information, see Configure outgoing and incoming Web requests


Provides a space for you to type the name of the user account for accessing the upstream server.

For more information, see Routing Web requests


Provides a space for you to type the corresponding password for the user account.

For more information, see Configure outgoing and incoming Web requests


Click to select a user account for accessing the upstream server.


Displays the authentication types to use when communicating with an upstream server. You can select Basic or Windows NT Challenge/Response.

For more information, see Configure outgoing and incoming Web requests


Provides a space for you to type the port to use when connecting to the upstream server.

For more information, see Configure outgoing and incoming Web requests


Click to find an upstream server or an ISA Server array.


Click to find a user account.


Specifies that, if the request meets the rule’s conditions, it will be rejected.

Web publishing rules specify, which server, if any, should return the requested object. The request can be discarded or redirected to an alternate site, usually to a Web server on the corporate network.

For more information, see Web publishing rules


Specifies that, if the request meets the rule’s conditions, it will be redirected to an internal Web server.

Web publishing rules specify, which server, if any, should return the requested object. The request can be discarded or redirected to an alternate site, usually to a Web server on the corporate network.

For more information, see Web publishing rules


Provides a space for you to type the name of the computer to which the request should be redirected.

The server name should be unique. Using the Fully Qualified Domain Name (FQDN) will avoid any conflict with duplicated server names.

Web publishing rules specify, which server, if any, should return the requested object. The request can be discarded or redirected to an alternate site, usually to a Web server on the corporate network.

For more information, see Web publishing rules


Click to find a server to which requests should be redirected.


Provides a space for you to type the port to use when redirecting Hypertext Transfer Protocol (HTTP) requests.

Web publishing rules specify which server, if any, should return the requested object. The request can be discarded or redirected to an alternate site, usually to a Web server on the corporate network.

For more information, see Web publishing rules


Provides a space for you to type the port to use when redirecting Secure Sockets Layer (SSL) requests.

Web publishing rules specify which server, if any, should return the requested object. The request can be discarded or redirected to an alternate site, usually to a Web server on the corporate network.

For more information, see Web publishing rules


Provides a space for you to type the port to use when redirecting Hypertext Transfer Protocol (HTTP) or Secure Sockets Layer (SSL) requests as File Transfer Protocol (FTP) requests.

Web publishing rules specify which server, if any, should return the requested object. The request can be discarded or redirected to an alternate site, usually to a Web server on the corporate network.

For more information, see Web publishing rules


Creates a log to monitor and analyze status of allow filters.

Allow filters are exception filters, which block all packet types except those specified.

For more information, see IP packet filters;  Packet filter log fields


Select to enable fragment filtering.

Fragmented packets may represent a security threat. When you select this option, Firewall and Web Proxy services drop all fragmented IP packets.

For more information, see Packet filter options


Select to make ISA Server reject all packets that have IP options in the header.

If a header contains IP options it may present a security risk. When you select this option, all packets with IP options in the header are dropped.

For more information, see Packet filter options


 Select to enable logging for Allow filters.

IP packet filters can be configured to either allow or block packets destined for the internal network. Allow filters are exception filters, meaning that all packet types will be blocked, except for those you specify with an Allow filter. Block filters can limit Allow filters, closing the ports specified. Even if you do not enable packet filtering, communication between your local network and the Internet is allowed only when you explicitly configure rules that permit access.

For more information, see Packet filter options


Specifies that Hypertext Transfer Protocol (HTTP) requests should be redirected as HTTP requests.

For more information, see Routing Web requests


Specifies that Hypertext Transfer Protocol (HTTP) requests should be redirected as File Transfer Protocol (FTP) requests.

For more information, see Routing Web requests


Specifies that Hypertext Transfer Protocol (HTTP) requests should be redirected as Secure Sockets Layer (SSL) requests. In this case, ISA Server opens a secure channel to the server.

For more information, see Routing Web requests


Specifies that Secure Sockets Layer (SSL) requests should be redirected as Hypertext Transfer Protocol (HTTP) requests.

For more information, see Routing Web requests


Specifies that Secure Sockets Layer (SSL) requests should be redirected as File Transfer Protocol (FTP) requests.

For more information, see Routing Web requests


Specifies that Secure Sockets Layer (SSL) requests should be redirected as SSL requests. In this case, ISA Server opens a secure channel to the server.

For more information, see Routing Web requests


Click to require access through a secure (SSL) channel only.


Click to select 128-bit encryption.


Click to use a certificate to authenticate to the Secure Sockets Layer (SSL) server.

Certificates act as an added security mechanism between ISA Server and a Secure Sockets Layer (SSL) Web server.

For more information, see Client certificates and server certificates


Click to edit a certificate.


Click to select a certificate.


Provides a space for you to type the name of an internal domain/server.

The server name should be unique. Using the Fully Qualified Domain Name (FQDN) will avoid any conflict with duplicated server names.

The local domain table (LDT) lists all the computer names in the internal network protected by ISA Server. When a client makes a request and requires name resolution, the client checks the LDT.

For more information, see Configuring the local domain table


Click to find a local domain.


Provides a space for you to type in a description of an internal server.


Provides a space for you to type in the name of an internal server.

The server name should be unique. Using the Fully Qualified Domain Name (FQDN) will avoid any conflict with duplicated server names.

The local domain table (LDT) lists all the computer names in the internal network protected by ISA Server. When a client makes a request and requires name resolution, the client checks the LDT.

For more information, see Configuring the local domain table


Click to find a local domain.


Provides a space for you to type in a description of a local server.

The local domain table (LDT) lists all the computer names in the internal network protected by ISA Server. When a client makes a request and requires name resolution, the client checks the LDT.


Provides a space for you to type the first IP address in a range of addresses for the local address table.

The local address table (LAT) is a series of IP address ranges that define your internal network address space and is centrally maintained on the ISA Server computer.

For more information, see Configuring the local address table


Provides a space for you to type the last IP address in a range of addresses for the local address table.

The local address table (LAT) is a series of IP address ranges that define your internal network address space and is centrally maintained on the ISA Server computer.

For more information, see Configuring the local address table


(Optional) Provides a space for you to type a description for the local address table entry.


Provides a space for you to type the first IP address in a range of addresses for the local address table.

The local address table (LAT) is a series of IP address ranges that define your internal network address space and is centrally maintained on the ISA Server computer.

For more information, see Configuring the local address table


Provides a space for you to type the last IP address in a range of addresses for the local address table.

The local address table (LAT) is a series of IP address ranges that define your internal network address space and is centrally maintained on the ISA Server computer.

For more information, see Configuring the local address table


(Optional) Provides a space for you to type a description for the local address table entry.


Click to include the following private ranges in the LAT. These three private IP address blocks are designated for use only on internal networks. They are never used on the Internet.


Click to include address ranges based on the Windows 2000 routing table.

A routing table contains internal network addresses. The Windows 2000 routing table defines all the IP addresses available in your local network.


Displays a list of servers in the array. Select a computer whose routing table should be used in determining the LAT

A routing table contains internal network addresses. The Windows 2000 routing table defines all the IP addresses available in your internal network.


Select the network adapters that are associated with the internal network addresses.

The local address table (LAT) is a series of IP address ranges that define your internal network address space. It is centrally maintained on the ISA Server computer. The Windows 2000 routing table defines all the IP addresses available in your internal network.

For more information, see Configuring the local address table


Select the network adapters that are associated with the internal network addresses.

The local address table (LAT) is a series of IP address ranges that define your internal network address space and is centrally maintained on the ISA Server computer. The Windows 2000 routing table defines all the IP addresses available in your internal network.

For more information, see Configuring the local address table


Displays a list of the network adapters associated with the internal network addresses.

The local address table (LAT) is a series of IP address ranges that define your internal network address space and is centrally maintained on the ISA Server computer. The Windows 2000 routing table defines all the IP addresses available in your internal network.

For more information, see Configuring the local address table


Specifies that ISA Management manages the local computer on which ISA Server is running.

For more information, see Remote administration


Specifies that ISA Management will be used to remotely manage the specified stand-alone server.


Specifies that ISA Management will be used to remotely manage an array or enterprise.


Specifies that ISA Management will be used to manage the remote server.

For more information, see Remote administration


Click to find the remote stand-alone serverr that ISA Management should manage.


Provides a space for you to type the name of the remote stand-alone server to be managed by ISA Management.

The server name should be unique. Using the Fully Qualified Domain Name (FQDN) will avoid any conflict with duplicated server names.

For more information, see Remote administration


Displays a list of file types and MIME types to include in the content group.

For more information, see Configuring content groups


Displays a list of available file types and MIME types.

For more information, see Configuring content groups


Click to add a file type or MIME type to the content group.


Click to remove a file type or MIME type from the content group.


Provides a space for you to type the name of the backup file, which will be used to restore configuration information.

For more information, see Backing up and restoring the ISA Server configuration


Click to find an existing backup file.


(Optional) Provides a space for you to type a description of the backup.


Displays any comments added about the backup file.


(Optional) Specifies any  comments about the backup file.


Displays the date that the backup file was created.


Specifies the date of the backup file.


Displays details of the array configuration.


Displays details of the server configuration.


Specifies details of the server or array configuration.


Provides a space for you to type the name of the IP packet filter.

IP packet filters control communication between the local network and the Internet. There are two kinds of IP packet filters: allow filters and block filters. Allow filters are exception filters, all packet types are blocked except for those you specify with an Allow filter. Block filters can limit Allow filters, closing the ports specified. Even if you do not enable packet filtering, communication between your local network and the Internet is allowed only when you explicitly configure rules that permit access.

For more information, see Packet filtering


Enables the packet filter.

For more information, see IP packet filters


(Optional) Provides a space for you to type a description for the IP packet filter.


Specifies that the filter applies to all servers in the array.

For more information, see IP packet filters


Click to find the IP address of a specific computer.


Specifies that the filter will apply to the selected server.

For more information, see IP packet filters


Specifies that the IP packet filter will apply to the default IP address for each external interface of the ISA Server computer. The selected ports will be opened or blocked only on these IP addresses.

IP packet filters control communication between the local network and the Internet. There are two kinds of IP packet filters: allow filters and block filters. Allow filters are exception filters, all packet types are blocked except for those you specify with an Allow filter. Block filters can limit Allow filters, closing the ports specified. Even if you do not enable packet filtering, communication between your local network and the Internet is allowed only when you explicitly configure rules that permit access.

For more information, see IP packet filters


Provides a space for you to type the IP address to which the IP packet filter will apply. The selected ports will be opened or blocked only on this IP address.

 For more information, see IP packet filters


Specifies that the filter applies to a specific IP address of a computer in the perimeter network. The selected ports will be opened or blocked on these IP addresses.

A perimeter network (also known as DMZ, demilitarized zone, and screened subnet) is a computer host or small network between the internal network and the Internet. It allows external users access to the perimeter network, while preventing access to the internal network. Perimeter network IP addresses are valid Internet addresses and perimeter network address space is excluded from the LAT. IP packet filters are opened to enable traffic between the Internet and the perimeter network.

 For more information, see Perimeter network scenarios;  Packet filtering


Click to find the IP address of a specific computer.


Specifies that the IP packet filter applies to the range of IP addresses in the perimeter network. The selected ports will be opened or blocked on these IP addresses.

A perimeter network (also known as DMZ, demilitarized zone, and screened subnet) is a computer host or small network between the internal network and the Internet. It allows external users access to the perimeter network, while preventing access to the internal network. Perimeter network IP addresses are valid Internet addresses and perimeter network address space is excluded from the LAT. IP packet filters are opened to enable traffic between the Internet and the perimeter network.

For more information, see Perimeter network scenarios;  Packet filtering


Provides a space for you to type the subnet of the perimeter network..


Provides a space for you to type the subnet mask for the perimeter network.


Specifies that the IP packet filter applies to the specific IP address on the ISA Server computer. The selected ports will be opened or blocked only on this IP address.

For more information, see IP packet filters


Specifies that the IP packet filter applies to the specified IP address. The selected ports will be opened or blocked only on this IP address.

For more information, see Perimeter network scenarios;  IP packet filters


Click to find the IP address of a specific computer.


Specifies that the IP packet filter applies to all external computers.

IP packet filters control communication between the local network and the Internet. There are two kinds of IP packet filters: allow filters and block filters. Allow filters are exception filters, all packet types are blocked except for those you specify with an Allow filter. Block filters can limit Allow filters, closing the ports specified. Even if you do not enable packet filtering, communication between your local network and the Internet is allowed only when you explicitly configure rules that permit access.

For more information, see IP packet filters


Provides a space for you to type the specific IP address of the external computer. The selected ports will be opened or blocked only for this IP address.


Click to find the IP address of a specific computer.


Specifies that the IP packet filter applies to the specific subnet and mask. . The selected ports will be opened or blocked for the selected IP addresses.

For more information, see IP packet filters


Provides a space for you to type the subnet of the computer range.


Provides a space for you to type the subnet mask of the computer range.


Specifies that the IP packet filter applies to the specific external computer.

For more information, see IP packet filters


Displays a list of filters that were installed with ISA Server.

For more information, see IP packet filters;  Configuring protocol definitions


Specifies that the IP packet filter use a predefined filter. Predefined filters specify the port, low-level protocol, and direction. You cannot modify properties of predefined filters.

IP packet filters control communication between the local network and the Internet. There are two kinds of IP packet filters: allow filters and block filters. Allow filters are exception filters, all packet types are blocked except for those you specify with an Allow filter. Block filters can limit Allow filters, closing the ports specified. Even if you do not enable packet filtering, communication between your local network and the Internet is allowed only when you explicitly configure rules that permit access.

For more information, see IP packet filters


Specifies that the IP packet filter use a custom filter. With custom filters, you specify the port, low-level protocol, and direction.

IP packet filters control communication between the local network and the Internet. There are two kinds of IP packet filters: allow filters and block filters. Allow filters are exception filters, all packet types are blocked except for those you specify with an Allow filter. Block filters can limit Allow filters, closing the ports specified. Even if you do not enable packet filtering, communication between your local network and the Internet is allowed only when you explicitly configure rules that permit access.

For more information, see IP packet filters


Displays a list of low-level protocols.

If you select Any, the IP packet filter applies to all protocols. You can specify the direction.

For more information, see IP packet filters


Displays available directions: inbound, outbound, or both.

For more information, see IP packet filters


Displays options for selecting which ports the IP packet filter opens or blocks on the local computers.

To apply the IP packet filter to all ports on the specified local computer, select All Ports.

To apply the IP packet filter to the specific port on the specified local computer, select Fixed port.

To make ISA Server open any of the ports numbered between 1025 and 5000 on the specified local computer, select Dynamic.

For more information, see IP packet filters


Displays options for selecting which ports the IP packet filter opens or blocks on the remote computers.

To apply the IP packet filter to all ports on the specified local computer, select All Ports

To apply the IP packet filter to the specific port on the specified local computer, select Fixed port.

For more information, see IP packet filters


Displays the protocol number.

•	6 indicates TCP.

•	17 indicates UDP.

•	1 indicates ICMP.

For Custom IP protocol, this provides a space for you to type a protocol number.

A protocol definition consists of a port, direction and protocol type. You can create protocol definitions, and ISA Server also has numerous predefined protocol definitions. Protocol definitions that are installed with ISA Server or with extensions cannot be modified.

For more information, see Configuring protocol definitions


Provides a space for you to type the port number that the IP packet filter opens or blocks on the local computers.

For more information, see IP packet filters


Provides a space for you to type the port number that the IP packet filter opens or blocks on the remote computers.

For more information, see IP packet filters


Displays options for selecting Internet Control Message Protocol (ICMP) type.

ICMP handles control messages for Internet protocol and reports errors in communications processing.


Displays options for selecting Internet Control Message Protocol (ICMP) code.

ICMP handles control messages for Internet protocol and reports errors in communications processing.


Specifies that ISA Server should only retrieve the object from the cache if it has not expired. If it has expired, it should be retrieved from the Internet according to the routing rule.

Web Proxy routing rules define how the cache is searched for an object and how to route the request if no valid object exists.

For more information, see How caching works


Specifies that ISA Server should retrieve the object from the cache when available, even if it has expired. If the object is not found in the cache, it should be retrieved from the Internet, according to the routing rule.

Web Proxy routing rules define how the cache is searched for an object and how to route the request if no valid object exists.

For more information, see How caching works


Specifies that the object should only be retrieved if it is in the cache, even if it is expired or invalid.

Web Proxy routing rules define how the cache is searched for an object and how to route the request if no valid object exists.

For more information, see How caching works


Displays options for selecting the Internet Control Message Protocol (ICMP) type.

ICMP handles control messages for Internet protocol and reports errors in communications processing. The ICMP type defines a message type and is identified by a number. The ICMP code contains specific message information and is also identified by a number.


Displays options for selecting the Internet Control Message Protocol (ICMP) code.

ICMP handles control messages for Internet protocol and reports errors in communications processing. The ICMP type defines a message type and is identified by a number. The ICMP code contains specific message information and is also identified by a number.


Provides a space for you to enter the Internet Control Message Protocol (ICMP) type.

ICMP handles control messages for Internet protocol and reports errors in communications processing. The ICMP type defines a message type and is identified by a number. The ICMP code contains specific message information and is also identified by a number.


Provides a space for you to type the Internet Control Message Protocol (ICMP) code.

ICMP handles control messages for Internet protocol and reports errors in communications processing. The ICMP type defines a message type and is identified by a number. The ICMP code contains specific message information and is also identified by a number.


Displays available directions: inbound, outbound, or both.

For more information, see IP packet filters


Displays the name of the Web filter.

Web filters monitor and respond to Hypertext Transfer Protocol (HTTP) communication between the internal network and the Internet.

For more information, see Web filters


Displays a description of the Web filter.


Displays the name of the vendor who developed the Web filter.

Web filters monitor and respond to Hypertext Transfer Protocol (HTTP) communication between the internal network and the Internet.

For more information, see Web filters


Displays the Web filter version.

Web filters monitor and respond to Hypertext Transfer Protocol (HTTP) communication between the internal network and the Internet.

For more information, see Web filters


Specifies the path to the Web filter.

Web filters monitor and respond to Hypertext Transfer Protocol (HTTP) communication between the internal network and the Internet.

For more information, see Web filters


Specifies whether the Web filter is enabled.

Web filters monitor and respond to Hypertext Transfer Protocol (HTTP) communication between the internal network and the Internet.

For more information, see Web filters


Specifies how ISA Server should respond to incoming and outgoing Web requests.

For more information, see Configuring outgoing Web request properties;  Configuring incoming Web request properties


Click to configure ISA Server to listen for incoming or outgoing Hypertext Transfer Protocol (HTTP) and Secure Socket Layer (SSL) requests on all Internet protocol addresses.

On Outgoing Web Requests tab, select this option to make ISA Server listen on all addresses associated with internal interface cards. On Incoming Web Requests tab, select this option to make ISA Server listen on all addresses associated with internal and external interface cards. Incoming and outgoing configurations are independent of each other.

 For more information, see Configuring outgoing Web request properties;  Configuring incoming Web request properties


Specifies which IP addresses and ports on the server should listen for requests.


Click to configure ISA Server to listen for incoming or outgoing Hypertext Transfer Protocol (HTTP) and Secure Socket Layer (SSL) requests on specific Internet protocol addresses.

On Outgoing Web Requests tab, select this option to make ISA Server listen  on specified IP addresses associated with internal interface cards. On Incoming Web Requests tab,  select this option to make ISA Server listen on specified IP addresses associated with internal and external interface cards. Incoming and outgoing configurations are independent of each other.

For more information, see Configuring outgoing Web request properties;  Configuring incoming Web request properties


Displays a list of all Internet Protocol (IP) addresses that ISA Server uses to listen for incoming or outgoing Hypertext Transfer Protocol (HTTP) and Secure Socket Layer (SSL) requests.

For more information, see Configuring outgoing Web request properties;  Configuring incoming Web request properties


Displays a list of IP addresses that ISA Server uses to listen for incoming or outgoing Hypertext Transfer Protocol (HTTP) and Secure Socket Layer (SSL) requests.

For more information, see Configuring outgoing Web request properties;  Configuring incoming Web request properties


Click to configure ISA Server to listen for incoming or outgoing Secure Socket Layer (SSL) requests.


Provides a space for you to type the port on which ISA Server should listen for Transmission Control Protocol (TCP) requests.

The default port number for incoming Web requests is 80.

The default port number for outgoing Web requests is 8080.

For more information, see ISA Server and IIS Server


Provides a space for you to type the port on which ISA Server should listen for Secure Socket Layer (SSL) requests.

Most Web browsers can only use port 443 for SSL requests.

For more information, see Configuring outgoing Web request properties;  Configuring incoming Web request properties


Specifies the configuration of connection settings for Web requests


Specifies that ISA Server should resolve a Web Proxy client request within the array, before routing accorded to the specified routing policy.

For more information, see Routing Web requests


Select the server that should listen for outgoing or incoming Web requests.

ISA Server must be configured so that it knows how to respond to incoming and outgoing Web requests. Select Use the same listener configuration for all internal IP addresses to make ISA Server listen for incoming and outgoing Web requests on all addresses associated with internal and external interface cards. Select Configure listeners individually per IP address to make ISA Server listen for incoming and outgoing Web requests only on specified IP addresses. Incoming and outgoing configurations are independent of each other.

For more information, see Configuring outgoing Web request properties;  Configuring incoming Web request properties


Click to add the IP address that ISA Server should use to listen for incoming and outgoing requests.


Click to remove an IP address so that ISA Server no longer uses it to listen for incoming and outgoing requests.


Click to edit an IP address.


Click to specify the maximum number of Web Proxy clients that can connect to the server at any one time simultaneously and the length of time in seconds before the server disconnects an inactive user.


Specifies that ISA Server should authenticate the user before allowing a request.

A Web publishing rule or access policy rule can apply to client address sets or to users. If a rule applies to users, then for outgoing requests, ISA Server will check outgoing Web request properties to determine how the user should be authenticated. For incoming requests, ISA Server will check incoming Web request properties. If this option is chosen, and a user does not provide proper credentials for authentication, then the request will be denied.

For more information, see Configure outgoing and incoming Web requests


Provides a space to type in the name of a domain that should be used for basic authentication, other than the default local Windows domain.

For more information, see Basic authentication


Click to find a domain to be used for basic authentication.


Displays a list of domains.

Users who log on to the network with the basic authentication methods must belong to a specific domain. Usually, the Windows domain that is used for basic authentication is the local domain in which the Web server is active. A different domain can be specified, if required.

For more information, see About authentication


Provides a space for you to type the name of a server, with the IP address that should listen for incoming and outgoing Web requests.

The server name should be unique. Using the Fully Qualified Domain Name (FQDN) will avoid any conflict with duplicated server names.

ISA Server must be configured so that it knows how to respond to incoming and outgoing Web requests. Select Use the same listener configuration for all internal IP addresses to make ISA Server listen for incoming and outgoing Web requests on all addresses associated with internal and external interface cards. Select Configure listeners individually per IP address to make ISA Server listen for incoming and outgoing Web requests only on specified IP addresses. Incoming and outgoing configurations are independent of each other.

For more information, see Configuring outgoing Web request properties;  Configuring incoming Web request properties


Provides a space for you to type a display name for the server that is listening for incoming and outgoing IP addresses.

ISA Server must be configured so that it knows how to respond to incoming and outgoing Web requests. Select Use the same listener configuration for all internal IP addresses to make ISA Server listen for incoming and outgoing Web requests on all addresses associated with internal and external interface cards. Select Configure listeners individually per IP address to make ISA Server listen for incoming and outgoing Web requests only on specified IP addresses. Incoming and outgoing configurations are independent of each other.

For more information, see Configuring outgoing Web request properties;  Configuring incoming Web request properties


Provides a space for you to type the server name with the IP address that should listen for incoming or outgoing Web requests.

The server name should be unique. Using the Fully Qualified Domain Name (FQDN) will avoid any conflict with duplicated server names.

ISA Server must be configured so that it knows how to respond to incoming and outgoing Web requests. Incoming and outgoing configurations are independent of each other. Configuration includes setting IP addresses and ports to listen for requests, authentication methods, and the number of connections.

For more information, see Configuring outgoing Web request properties;  Configuring incoming Web request properties


Displays a list of IP addresses on the selected computer. Select the IP address that should listen for incoming or outgoing Web requests.

For more information, see Configuring outgoing Web request properties;  Configuring incoming Web request properties


Provides a space for you to type the IP address that listens for incoming or outgoing Web requests.

For more information, see Configuring outgoing Web request properties;  Configuring incoming Web request properties


Provides a space for you to type a display name for the server that listens for incoming and outgoing IP addresses

For more information, see Configuring outgoing Web request properties;  Configuring incoming Web request properties


Specifies whether ISA Server should use a certificate to authenticate itself to Web Proxy clients.

 For more information, see Client certificates and server certificates


Displays the certificate that ISA Server uses to authenticate itself to Web Proxy clients.


Click to select the certificate that ISA Server should use to authenticate itself to Web Proxy clients.


Specifies that ISA Server supports a variety of authentication methods. Authentication can be set for all IP addresses on the server, or separately for each IP address.

Authentication is required when access policy rules or Web publishing rules apply to users or groups rather than client address sets. It is also required when you select Ask unauthenticated users for identification in Incoming Web Requests and Outgoing Web Requests.

For more information, see Incoming and outgoing Web request authentication


Specifies whether to use basic authentication. Note that basic authentication results in the transmission of passwords across the network in unencrypted form.

For more information, see Basic authentication


Click to configure ISA Server to use a logon domain other than the default local domain with the Basic authentication method.


Specifies whether digest authentication is used when authentication is required.

Note that digest authentication requires domain controller to store users passwords using reversible encryption.

For more information, see Digest authentication


Specifies whether to use integrated Windows authentication when authentication is required.

Integrated Windows authentication is secure, because the user name and password are not sent across the network.

For more information, see Integrated Windows authentication


Specifies whether to use the client certificate when authentication is required.

Secure Socket Layer (SSL) uses client certificates to authenticate users who request information on your Web site. SSL authenticates users by checking the encrypted digital identifiers that are submitted by a user’s browser during the logon process.

For more information, see Client certificates and server certificates


Click to configure ISA Server to use a logon domain other than the default local domain with the Digest authentication method.


Displays the name of a domain to be used with the Basic authentication method. By default, the local domain is used.


Displays the name of a domain to be used with the Digest authentication method. By default, the local domain is used.


Specifies that the content should be downloaded from the Internet only once, at the specified date and time.

For more information, see Updating cache content automatically


Specifies that the content should be downloaded from the Internet daily, at the specified time.

For more information, see Updating cache content automatically


Specifies that the content should be downloaded from the Internet on the selected days, at the specified time.

For more information, see Updating cache content automatically


Specifies that the content should be downloaded from the Internet every Sunday, at the specified time.


Specifies that the content should be downloaded from the Internet every Monday, at the specified time.


Specifies that the content should be downloaded from the Internet every Tuesday, at the specified time.


Specifies that the content should be downloaded from the Internet every Wednesday, at the specified time.


Specifies that the content should be downloaded from the Internet every Thursday, at the specified time.


Specifies that the content should be downloaded from the Internet every Friday, at the specified time.


Specifies that the content should be downloaded from the Internet every Saturday, at the specified time.


Provides a space for you to type the time when the content should be copied from the Internet to the cache on the ISA Server.

Scheduled cache content allows you to customize cache content. By monitoring and analyzing Internet access, you can anticipate frequently-requested objects and schedule them for download directly to the ISA Server cache. When you schedule content download, you can configure dynamic content to be cached, by configuring the ISA Server cache to store the objects, even if the Hypertext Transfer Protocol (HTTP) cache control headers indicate that they are not necessarily cachable.

For more information, see Updating cache content automatically


Provides a space for you to type the date when the content should be copied from the computer on the Internet to the cache on the ISA Server.

Scheduled cache content allows you to customize cache content. By monitoring and analyzing Internet access, you can anticipate frequently-requested objects and schedule them for download directly to the ISA Server cache. When you schedule content download, you can configure dynamic content to be cached, by configuring the ISA Server cache to store the objects, even if the Hypertext Transfer Protocol (HTTP) cache control headers indicate that they are not necessarily cachable.

For more information, see Updating cache content automatically


Provides a space for you to type the URL from which to begin downloading content.

Scheduled cache content allows you to customize cache content. By monitoring and analyzing Internet access, you can anticipate frequently-requested objects and schedule them for download directly to the ISA Server cache. Content may be downloaded from a single URL, multiple URLs or an entire Web site. When you schedule content download, you can configure dynamic content to be cached, by configuring the ISA Server cache to store the objects, even if the Hypertext Transfer Protocol (HTTP) cache control headers indicate that they are not necessarily cachable.

For more information, see Updating cache content automatically


Specifies whether downloaded content should be marked with a new time-to-live (TTL) setting. The TTL setting defines how long the downloaded content will remain in the cache.

For more information, see Updating cache content automatically;  Configuring expiration policy


Provides a space for you to type the new time-to-live (TTL) setting.

Scheduled cache content allows you to customize cache content. By monitoring and analyzing Internet access, you can anticipate frequently-requested objects and schedule them for download directly to the ISA Server cache. The TTL setting defines how long the downloaded content will remain in the cache.

For more information, see Updating cache content automatically;  Configuring expiration policy


Specifies that ISA Server should override the time-to-live (TTL) of an object with either the TTL entered here or the TTL specified for the cache configuration properties. The TTL setting defines how long the downloaded content will remain in the cache.

For more information, see Configuring expiration policy


Specifies that, if the object has no time-to-live (TTL), then it should be allocated either the TTL entered here or the TTL specified for the cache configuration properties. The TTL setting defines how long the downloaded content will remain in the cache.

For more information, see Configuring expiration policy


Specifies a limit for the number of links that can be followed from a single page.


Provides space to type the number of links that can be followed from a single page.


Specifies a limit for the total number of links that can be followed.


Provides space to type the total number of links that can be followed.


Specifies whether content should be downloaded only from the domain specified in Begin downloading from URL.

For more information, see Updating cache content automatically;  Configuring expiration policy


Specifies whether only text objects should be downloaded.

For more information, see Updating cache content automatically


Specifies that ISA Server should force a content download and overwrite previous versions in the cache.

For more information, see Updating cache content automatically


Displays a list of client address sets.

For access policy rules, a client address set consists of one or more internal client computers that are defined as a group for the purpose of simplifying application of rules for clients. For server publishing rules, client sets are usually used to define a set of IP addresses for external clients, usually located on the Internet, for the purpose of allowing these clients access to an internal server.

For more information, see Configuring client address sets


Click to create a new client address set.


Click to add the selected client address set to the list of client address sets that are specified for the rule.


Click to remove the selected client address set from the list.


Displays a list of client address sets that will be specified for the rule.

For access policy rules, a client address set consists of one or more internal client computers that are defined as a group for the purpose of simplifying application of rules for clients. For server publishing rules, client sets are usually used to define a set of IP addresses for external clients, usually located on the Internet, for the purpose of allowing these clients access to an internal server.

For more information, see Client address sets


Displays the name of the content group.

Content groups specify a set of file and MIME types. These content groups are used when defining site and content rules, to control Web access. A complete list of MIME types and file extensions can be found on the linked page.

For more information, see Configuring content groups


(Optional) Provides a space for you to type a description of the content group.


Displays a list of file types and MIME types to include in the content group.

For more information, see Configuring content groups


Displays a list of available file types and MIME types.

Content groups specify a set of file and MIME types. These content groups are used when defining site and content rules, to control Web access. A complete list of MIME types and file extensions can be found on the linked page.

For more information, see Configuring content groups


Click to add a file type or MIME type.


Click to remove the selected MIME type or file type.


Specifies the IP address of the local server that publishes its content to external clients.

Server publishing allows your internal servers to publish to the Internet. Server publishing rules filter all incoming and outgoing requests to these internal servers.

For more information, see Server publishing rules and IP packet filters


Provides a space for you to type the IP address of the internal server that publishes its content to external clients.

Server publishing allows your internal servers to publish to the Internet. Server publishing rules filter all incoming and outgoing requests to these internal servers

For more information, see Server publishing rules and IP packet filters


Click to select a protocol definition that can be used by external clients to access the computer.


Provides a space for you to type the IP address on one of ISA Server computer’s external interface cards that will be accessed by external clients.

Server publishing allows your internal servers to publish to the Internet. Server publishing rules filter all incoming and outgoing requests to these internal servers

For more information, see Server publishing rules and IP packet filters


Click to find the IP address of the internal computer.


Click to view a list of external IP addresses on this ISA Server computer.


Displays a list of protocol definitions that external clients can use to access the computer. Only protocol definitions that are inbound appear.

Server publishing allows your internal servers to publish to the Internet. Server publishing rules filter all incoming and outgoing requests to these internal servers.

For more information, see Server publishing rules and IP packet filters


Specifies that retrieved objects should always be cached, regardless of content.


Specifies that ISA Server should cache retrieved objects if the content is non-dynamic.

Non-dynamic means that something in the header indicates that the content should not be cached.


Specifies that ISA Server should never cache retrieved objects.


Specifies that ISA Server should generate an event if an out-of-band denial-of-service attack is attempted against a computer protected by ISA Server.

ISA Server generates an alert and executes an action if an attempted intrusion is detected. Although an event is generated when the attack occurs, you must specifically enable and configure an alert to trigger an action.

For more information, see Configuring intrusion detection


Specifies that ISA Server should generate an event if a TCP SYN packet is sent with a spoofed source IP address and port number that matches that of the destination IP address and port.

ISA Server generates an alert and executes an action if an attempted intrusion is detected. Although an event is generated when the attack occurs, you must specifically enable and configure an alert to trigger an action.

For more information, see Configuring intrusion detection


Specifies that ISA Server should generate an event if a large amount of information is appended to an ICMP echo request (ping) packet.

ISA Server generates an alert and executes an action if an attempted intrusion is detected. Although an event is generated when the attack occurs, you must specifically enable and configure an alert to trigger an action.

For more information, see Configuring intrusion detection


Specifies that ISA Server should generate an event if repeated attempts to a destination computer were made and no corresponding ACK packets were communicated.

ISA Server generates an alert and executes an action if an attempted intrusion is detected. Although an event is generated when the attack occurs, you must specifically enable and configure an alert to trigger an action.

For more information, see Configuring intrusion detection


Specifies that ISA Server should generate an event if an attempt is made to count the services running on a computer by probing each port for a response.

ISA Server generates an alert and executes an action if an attempted intrusion is detected. Although an event is generated when the attack occurs, you must specifically enable and configure an alert to trigger an action.

For more information, see Configuring intrusion detection


Specifies than an event should be generated if there is an attempt to send an illegal UDP packet. Although an event will be generated when the attack occurs, you must specifically enable and configure an alert to trigger an action.

ISA Server will generate an alert and execute some action if an attempted intrusion is detected. Although an event will be generated when the attack occurs, you must specifically enable and configure an alert to trigger an action.

For more information, see Configuring intrusion detection


Provides a space for you to type the maximum number of ports that can be scanned before generating an event when a port scan attack is detected.

ISA Server generates an alert and executes an action if an attempted intrusion is detected. Although an event is generated when the attack occurs, you must specifically enable and configure an alert to trigger an action.

For more information, see Configuring intrusion detection


Provides a space for you to type the maximum number of well-known ports that can be scanned before generating an event when a port scan attack is detected. A well-known port is any port in the range of 1-2048.

For more information, see Configuring intrusion detection


Provides a space for you to type the maximum number of well-known ports that can be scanned before generating an event when a port scan attack is detected. A well-known port is any port in the range of 1-2048.

For more information, see Configuring intrusion detection


Provides a space for you to type the maximum number of ports that can be scanned before generating an event when a port scan attack is detected.

For more information, see Configuring intrusion detection


Specifies that packet filtering is enabled.

IP packet filters control communication between the local network and the Internet. There are two kinds of IP packet filters: allow filters and block filters. Allow filters are exception filters, all packet types are blocked except for those you specify with an Allow filter. Block filters can limit Allow filters, closing the ports specified. Even if you do not enable packet filtering, communication between your local network and the Internet is allowed only when you explicitly configure rules that permit access.

For more information, see Filtering and routing


Specifies that routing is enabled.

When you enable routing, ISA Server routes all traffic between the Internet and your corporate network, in accordance with the defined policy. Routing does not take security into consideration. Packet filtering works with routing to provide the required security.

For more information, see Filtering and routing


Specifies that intrusion detection is enabled.

 ISA Server can generate an alert and execute an action if an attempted intrusion is detected.

For more information, see Configuring intrusion detection


Provides a space for you to type the name.


(Optional) Provides a space for you to type a description.


Specifies whether the rule is enabled.


Provides a space for you to type the name of the internal server that you want to make available to external users.

The server name should be unique. Using the Fully Qualified Domain Name (FQDN) will avoid any conflict with duplicated server names.


Click to find a local server.


Click to find the IP addresses that are associated with the specified computer.


Displays a list of IP addresses that are associated with the specified computer.


Provides a space for you to type the name of the protocol definition.

A protocol definition consists of a port, direction and protocol type. You can create protocol definitions, and ISA Server also has numerous predefined protocol definitions. Protocol definitions that are installed with ISA Server or with extensions cannot be modified.

For more information, see Configuring protocol definitions


(Optional) Provides a space for you to type a description of the protocol definition.


Provides a space for you to type the port number for this protocol definition. The port can be any number between 1 and 65,535.

A protocol definition consists of a port, direction and protocol type. You can create protocol definitions, and ISA Server also has numerous predefined protocol definitions. Protocol definitions that are installed with ISA Server or with extensions cannot be modified.

For more information, see Configuring protocol definitions


Specifies whether the low-level protocol used for the protocol definition should be TCP or UDP.

A protocol definition consists of a port, direction and protocol type. You can create protocol definitions, and ISA Server also has numerous predefined protocol definitions. Protocol definitions that are installed with ISA Server or with extensions cannot be modified.

For more information, see Configuring protocol definitions


Specifies whether the direction of the communication for this protocol definition should be inbound or outbound.

A protocol definition consists of a port, direction and protocol type. You can create protocol definitions, and ISA Server also has numerous predefined protocol definitions. Protocol definitions that are installed with ISA Server or with extensions cannot be modified.

For more information, see Configuring protocol definitions


Displays a list of secondary connections specified for this protocol definition.

A secondary connection is the range of port numbers, protocol, and direction used for additional connections or packets that follow the initial connection.

For more information, see Configuring protocol definitions


Click to add a secondary connection for the protocol definition.


Click to modify the selected secondary connection.


Click to remove the selected secondary connection.


Specifies the number of Web Proxy clients connected to the server at one time. To specify no upper limit on the number of connections that are permitted or to specify a maximum number, click Unlimited. To specify the length of time, in seconds, before the server disconnects an inactive user, click Connection timeout.


Displays a list of all the internal IP addresses defined for the server.


Click to specify an unlimited amount of Web Proxy clients connecting to the server at any one time


Click to specify a maximum number of Web Proxy clients connecting to the server at any one time.


Provides a space for you to type the maximum number of Web Proxy clients connecting to the server at one time.


Provides a space for you to enter the number of seconds before the server disconnects an inactive user.


Displays a list of certificates stored in the certificate store of the ISA Server computer.

 For more information, see Client certificates and server certificates


Specifies that clients will be able to use ISA Server to automatically detect the appropriate ISA Server computer for Web Proxy clients to use when making Hypertext Transfer Protocol (HTTP), HTTPS (secured HTTP), or File Transfer Protocol (FTP) requests.

For more information, see Automatic discovery


Provides a space for you to type the port that ISA Server should use to listen for automatic discovery requests.

For more information, see Automatic discovery


Provides a space for you to type the name of the scheduled report.

Scheduled reports offer flexible ways to present report findings, based on the data collected from log files.

For more information, see Scheduling reports


(Optional) Provides a space for you to type a description of the scheduled report.


Click to enable a report.


Specifies at what intervals the report will be scheduled.

Scheduled reports offer flexible ways to present report findings, based on the data that is collected from logs.

For more information, see Scheduling reports


Click to specify that the report should be scheduled on a daily basis.


Click to specify that the report should be scheduled on a weekly basis.


Click to specify that the report should be scheduled on a monthly basis.


Click to specify that the report should be scheduled on an annual basis.


Click to specify a customized time frequency for the report schedule.


Provides space for you to type a start date for the report schedule.

Scheduled reports offer flexible ways to present report findings, based on the data collected from logs.

For more information, see Scheduling reports


Provides space for you to type an end date for the report schedule.

Scheduled reports offer flexible ways to present report findings, based on the data collected from logs.

For more information, see Scheduling reports


Specifies the schedule for report generation should begin.

Scheduled reports offer flexible ways to present report findings, based on the data collected from logs.

For more information, see Scheduling reports


Click to begin report generation immediately.


Click to begin report generation at a specific date and time.


Provides a space for you to enter a date to commence the report schedule.

Scheduled reports offer flexible ways to present report findings, based on the data collected from logs.

For more information, see Scheduling reports


Provides a space for you to enter a time to commence the report schedule.

Scheduled reports offer flexible ways to present report findings, based on the data collected from logs.

For more information, see Scheduling reports


Specify a recurring pattern for the generation of a scheduled report.

Scheduled reports offer flexible ways to present report findings, based on the data collected from logs.

For more information, see Scheduling reports


Click to generate a single scheduled report.


Click to generate a daily scheduled report.


Click to generate a scheduled report on specified days.


Specifies whether reports should be generated every Sunday.


Specifies whether reports should be generated every Monday.


Specifies whether reports should be generated every Tuesday.


Specifies whether reports should be generated every Wednesday.


Specifies whether reports should be generated every Thursday.


Specifies whether reports should be generated every Friday.


Specifies whether reports should be generated every Saturday.


Click to indicate that a scheduled report should be generated once a month.


Specifies the date of the month on which the monthly scheduled report should be generated.

Scheduled reports offer flexible ways to present report findings, based on the data collected from logs.

For more information, see Scheduling reports


Specifies that log data will be saved in daily and monthly summaries. At least 35 daily summaries, and 13 monthly summaries, must be saved.

 For more information, see Configuring report log summaries


Specifies the location of the log summaries.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Configuring reports


Specifies that ISA Server save the daily summary database to the \ISA\ISASummaries folder.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Configuring reports


Specifies that the daily summary database is saved to the selected folder.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Configuring reports


Provides a space for you to type the name of the folder in which to save the daily summary database.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Configuring reports


Click to browse to a folder in which to save the daily summary database.


Specifies the number of summaries that should be saved.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Configuring reports


Provides a space for you to type how many daily summaries should be saved.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Configuring reports


Provides a space for you to type how many monthly summaries should be saved.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Configuring reports


Specifies that the ISA Server reporting facility is available. When enabled, the computer running ISA Management performs the scheduled report jobs.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Configuring reports


Specifies where report information will be stored.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Configuring reports


Specifies that the report database is saved in the \ISA\ISAReports folder on the computer running ISA Management.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Configuring reports


Specifies that the report database should be saved to the selected folder.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Configuring reports


Provides a space for you to type the folder in which to save the report database.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Configuring reports


Click to browse to a folder in which to save the report database.


Specifies that reports can be sorted according to a choice of preferences. This allows customization of predefined reports.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Viewing predefined reports


Click to sort information about cache hits according to the number of requests to the cache.


Click to sort information about cache hits according to the number of bytes in requests to the cache.


Specifies how many users that receive authorization failures at remote sites should be included for reporting purposes.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Viewing predefined reports


Specifies that reports can be sorted according to a choice of preferences. This allows customization of predefined reports.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Viewing predefined reports


Click to sort protocol information according to the amount of requests handled for a particular protocol.


Click to sort protocol information according to the most active users of a particular protocol.


Click to sort protocol information according to the number of bytes received from any remote computer using a particular protocol.


Click to sort protocol information according to the number of bytes sent by any remote computer using a particular protocol.


Click to sort protocol information according to the total bytes transferred using a particular protocol.


Specifies how many of the top Web sites accessed through ISA Server should be included for reporting purposes.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Viewing predefined reports


Specifies that reports can be sorted according to a choice of preferences. This allows customization of predefined reports.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Viewing predefined reports


Click to sort top Web site information according to the amount of requests received for a particular Web site.


Click to sort top Web site report information according to the most active users of these Web sites.


Click to sort top Web site information according to number of bytes received from a Web site.


Click to sort top Web site information according to number of bytes sent to a Web site.


Click to sort top Web site information according to the total bytes transferred from a Web site.


Specifies how many of the most frequent Web users should be included for reporting purposes.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Viewing predefined reports


Specifies that reports can be sorted according to a choice of preferences. This allows customization of predefined reports.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Viewing predefined reports


Click to sort top user information according to the amount of requests received from a particular user.


Click to sort top user information according to number of bytes received from a user.


Click to sort top user information according to number of bytes sent by a user.


Click to sort top user information according to the total bytes transferred from a Web site.


Specifies how many of the most frequently used client applications should be included for reporting purposes.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Viewing predefined reports


Specifies that reports can be sorted according to a choice of preferences. This allows customization of predefined reports.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Viewing predefined reports


Click to sort client-application information according to the number of requests received for a particular application.


Click to sort client-application information according to the number of users requesting a particular application.


Specifies how many of the most popular Web destinations should be included for reporting purposes.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Viewing predefined reports


Specifies that reports can be sorted according to a choice of preferences. This allows customization of predefined reports.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Viewing predefined reports


Click to sort destination information according to the number of requests received for a particular destination.


Click to sort client-application information according to the number of users who request access to a particular destination.


Click to sort destination information according to the number of bytes received from any remote computer.


Click to sort destination information according to the number of bytes sent to any remote computer.


Click to sort top user information according to the total bytes transferred to and from a destination.


Specifies how many of the most popular types of browser accessing ISA Server should be included for reporting purposes.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Viewing predefined reports


Specifies that reports can be sorted according to a choice of preferences. This allows customization of predefined reports.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Viewing predefined reports


Click to sort browser information according to the number of requests received from a particular browser.


Click to sort browser information according to the identities of the most active Web users


Specifies how many of the most popular types of operating system that are used to access the ISA Server should be included for reporting purposes.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Viewing predefined reports


Specifies that reports can be sorted according to a choice of preferences. This allows customization of predefined reports.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Viewing predefined reports


Click to sort operating system information according to the number of requests received from a particular operating system.


Click to sort operating system information according to the number of users that communicate with ISA Server using a particular operating system.


Specifies how many of the top Web users whose packets were rejected should be included for reporting purposes.

ISA Server reporting mechanism collates data from ISA Server logs into a database on each ISA Server.

For more information, see Viewing predefined reports;  Configuring IP packet filters


Specifies that the array use the default enterprise policy settings. The enterprise administrator configures these defaults at the enterprise level.

For more information, see Administer the enterprise;  The enterprise and arrays;  Policy elements.


Specifies that the array uses custom policy settings. If you select this option, configure how the enterprise policy is applied to the array.

For more information, see Administer the enterprise;  The enterprise and arrays;  Policy elements


Specifies that the array does not use any of the enterprise-level rules.

For more information, see Administer the enterprise;  The enterprise and arrays;  Policy elements.


Specifies that the rules of the selected enterprise policy should be applied to the array.

For more information, see Administer the enterprise;  The enterprise and arrays;  Policy elements.


Specifies whether an array policy can be created to extend the enterprise policy. Array policies can only further restrict the enterprise policy.

For more information, see Administer the enterprise;  The enterprise and arrays;  Policy elements.


Displays a list of policies configured for the enterprise.

For more information, see Administer the enterprise;  The enterprise and arrays;  Policy elements.


Specifies whether the array can create publishing rules to make internal servers available to external users.

For more information, see Administer the enterprise;  The enterprise and arrays


Specifies whether packet filtering must be enabled on the array.

For more information, see Administer the enterprise;  The enterprise and arrays;  Applying enterprise policy


Provides a space for you to type the policy name.

An enterprise policy includes site and content rules and protocol rules. It can be applied to any array. An array policy consists of site and content rules, protocol rules, Web publishing rules and IP packet filters. An array policy limits enterprise policy.

 For more information, see Applying enterprise policy


(Optional) Provides a space for you to type a description of the policy.


Displays the date when the policy was created.


Display the date when the policy was last modified.


Displays a list of arrays and specifies which enterprise policy is applied to each array.

An enterprise policy includes site and content rules, and protocol rules. It can be applied to any array. An array policy consists of site and content rules, protocol rules, Web publishing rules and IP packet filters. An array policy limits enterprise policy.

For more information, see Applying enterprise policy


Specifies that only an array policy will be used. No enterprise policy will be set.

For more information, see Applying enterprise policy


Specifies that an enterprise policy will be used.

For more information, see Applying enterprise policy


Provides a space for you to type in the name of an enterprise policy.

For more information, see Applying enterprise policy


Specifies that an array policy may be set in addition to an enterprise policy.

For more information, see Applying enterprise policy


Specifies that Web publishing rules may be created at the array level.

An enterprise policy includes site and content rules, and protocol rules. It can be applied to any array. An array policy consists of site and content rules, protocol rules, Web publishing rules and IP packet filters. An array policy will limit enterprise policy.

For more information, see Applying enterprise policy


Specifies that packet filtering will be used at the array level. An enterprise policy includes site and content rules, and protocol rules. It can be applied to any array. An array policy consists of site and content rules, protocol rules, Web publishing rules and IP packet filters. An array policy will limit enterprise policy.

For more information, see Applying enterprise policy


Select to enable PPTP IP protocol to pass through the firewall.

PPTP is a tunneling protocol used to manage tunnels and encapsulate data.

For more information, see Virtual private network


Displays a list of available servers.


Specifies the name of the server running H.323 Gatekeeper.

H.323 Gatekeeper provides directory and call routing services to registered H.323 clients. It allows calls to be placed using the e-mail address or phone number of the called party, and the transparent use of H.323 proxies and gateways between IP and PSTN networks.

For more information, see To enable the H.323 protocol rule;  Using H.323 Gatekeeper


Specifies a description for this server running H.323 Gatekeeper.


Specifies the time and date that this server running H.323 Gatekeeper was started.


Specifies the build type for this server running H.323 Gatekeeper.


Specifies the build number for this server running H.323 Gatekeeper.


Specifies the build date for this server running H.323 Gatekeeper.


Specifies the network adapters installed on the server running H.323 Gatekeeper. If this server has multiple network adapters installed, you can specify the IP addresses that H.323 Gatekeeper uses to listen for call requests.

H.323 Gatekeeper provides directory and call routing services to registered H.323 clients. Its use allows calls to be placed using the e-mail address or phone number of the called party, and the transparent use of H.323 proxies and gateways between IP and PSTN networks.

For more information, see To enable the H.323 protocol rule;  Using H.323 Gatekeeper


Specifies the amount of time (in seconds) before the registration for this server running H.323 Gatekeeper expires. If there is no activity at the end of the time period, H.323 Gatekeeper queries the server to determine whether it is still active.

H.323 Gatekeeper provides directory and call routing services to registered H.323 clients. Its use allows calls to be placed using the e-mail address or phone number of the called party, and the transparent use of H.323 proxies and gateways between IP and PSTN networks.

For more information, see To enable the H.323 protocol rule;  Using H.323 Gatekeeper


Specifies the amount of time (in seconds) before an active call expires. If there is no activity during this period of time, H.323 Gatekeeper terminates the call.

H.323 Gatekeeper provides directory and call routing services to registered H.323 clients. Its use allows calls to be placed using the e-mail address or phone number of the called party, and the transparent use of H.323 proxies and gateways between IP and PSTN networks.

For more information, see To enable the H.323 protocol rule;  Using H.323 Gatekeeper


Specifies the size of the H.323 Gatekeeper database.


Click to compact the database.


Specifies a gateway, proxy, or Internet firewall as a call destination.

Calls external to your organization are given the IP address of this gateway, proxy, or Internet firewall, and not the IP address of your local computer.

 For more information, see Call routing rules


Specifies a server running Site Server ILS service (as an IP, DNS, or NetBIOS address) as a call destination. This works for an E-mail Address rule only.

When necessary, H.323 Gatekeeper uses name resolution to find the IP address of the server running Site Server ILS service. It then queries the server running Site Server ILS service. If both queries fail and no entries are returned, the next rule (if applicable) is applied.

 H.323 Gatekeeper queries at least once with the complete alias. If the query fails and the alias has the someone@microsoft.com format, the H.323 Gatekeeper extracts the username and queries again for entries beginning with someone]. This provides the client attempting to find someone@microsoft.com with the opportunity to find a Site Server ILS service entry for someone]accounting5.accounting.microsoft.com (a format supported for backward-compatibility).

For more information, see Call routing rules


Specifies an alternative server running H.323 Gatekeeper (specified as an IP, DNS, or NetBIOS address) as a call destination. You can use this to route calls to users connected to the alternative server running H.323 Gatekeeper.

If necessary, H.323 Gatekeeper uses name resolution to find the IP address of the destination H.323 Gatekeeper. It then queries the server running H.323 Gatekeeper with a Location Request message. In response to this message, the  H.323 Gatekeeper being queried  tries to resolve the alias using the registration database only, regardless of  rule specification.  If the call destination H.323 Gatekeeper returns a Q931 address, it is returned to the client. Otherwise, rule processing continues.

For more information, see Call routing rules


Specifies that the destination is a multicast group.

H.323 Gatekeeper sends a Location Request message using multicast. If another H.323 Gatekeeper sends a positive response, the address contained in the response is sent to the client. Otherwise, rule processing continues.

For more information, see Call routing rules


Specifies a destination that cannot be resolved. This destination instructs H.323 Gatekeeper to stop rule processing. Even if there are other matching rules that follow the None rule with lower precedence, H.323 Gatekeeper rejects the request.

For more information, see Call routing rules


Click this to specify a registration database as a destination.

If the alias is of E164 type, H.323 Gatekeeper searches for the phone number string, up to but not including any special characters (For example, if the original string is 95551212#3344, H.323 Gatekeeper uses 95551212).

If the alias is of e-mail-ID or H323-ID type, the lookup uses the complete alias. Otherwise, the two types are interchangeable (for example, a user registered with an e-mail-ID of someone@microsoft.com is successfully resolved when querying for the H323-ID of someone@microsoft.com).

If an entry is found, its Q931 address is returned in the confirmation and processing stops. Otherwise, the processing continues with the next rule.

Note

•	This destination cannot be used for IP aliases.

For more information, see Call routing rules


Specifies an Active Directory server as a destination.

H.323 Gatekeeper uses Active Directory for resolving e-mail address aliases. It extracts the user name portion from the alias if the alias contains an at sign (@).If the alias contains 15 characters or fewer, it uses the entire alias.

If the query returns a fully qualified DNS computer name, H.323 Gatekeeper performs an additional DNS query to find the IP address.

For more information, see Call routing rules


Specifies a local IP address as a destination.

This destination type is valid for IP aliases only.

H.323 Gatekeeper returns the address represented by the alias. In other words, the alias and address do not require a translation. Because the destination is directly reachable, the IP address represented by the requested alias can be used as a Q931 address.

For more information, see Call routing rules


Specifies the IP address or DNS name for this destination.

H.323 Gatekeeper returns the address represented by the alias. This means that the alias and address do not require a translation. Since the destination is directly reachable, the IP address represented by the requested alias can be used as a Q931 address.

For more information, see Call routing rules


Specifies descriptive text for this destination.


Specifies whether this destination is enabled on this server running H.323 Gatekeeper.

H.323 Gatekeeper returns the address represented by the alias. This means that the alias and address do not require a translation. Since the destination is directly reachable, the IP address represented by the requested alias can be used as a Q931 address.

For more information, see Call routing rules


Specifies that this routing rule applies to phone number (E164) addresses.

H.323 Gatekeeper returns the address represented by the alias. This means that the alias and address do not require a translation. Since the destination is directly reachable, the IP address represented by the requested alias can be used as a Q931 address.

For more information, see Call routing rules


Specifies that this routing rule applies to an e-mail or DNS addressH.323 Gatekeeper returns the address represented by the alias. This means that the alias and address do not require a translation. Since the destination is directly reachable, the IP address represented by the requested alias can be used as a Q931 address.

For more information, see Call routing rules


Specifies that this routing rule applies to an IP address.

H.323 Gatekeeper returns the address represented by the alias. This means that the alias and address do not require a translation. Since the destination is directly reachable, the IP address represented by the requested alias can be used as a Q931 address.

For more information, see Call routing rules


Specifies a pattern for which this routing rule searches. If the phone number matches this pattern, the call is routed to the destination specified by this rule.

H.323 Gatekeeper returns the address represented by the alias. This means that the alias and address do not require a translation. Since the destination is directly reachable, the IP address represented by the requested alias can be used as a Q931 address.

For more information, see Call routing rules


Specifies that the number pattern that was specified is treated as a prefix for all phone numbers. This rule applies to all phone numbers beginning with this specified number pattern.

If you do not enable this option, this rule only applies to phone numbers that exactly match the number pattern that you specified.


Specifies a pattern for which this routing rule searches. If the e-mail address or DNS address match this pattern, the call is routed to the destination specified by this rule.


Specifies that the text string specified is used a prefix for all e-mail addresses or DNS addresses. This rule applies to all addresses beginning with the text specified.

If you do not enable this option, this rule only applies to e-mail addresses or DNS addresses that exactly match the text specified.


Specifies a pattern for which this routing rule searches. If the IP address matches this pattern, the call is routed to the destination specified by this rule.


Specifies the subnet mask for this IP address.


Specifies a metric number for this rule.

A metric number prioritizes the rule in the event that an address matches multiple rules. A lower number means that the rule will have a higher priority.


Specifies a name for this rule.


Specifies descriptive text for this rule.


Specifies that digits should be discarded from the beginning of the phone number before it is routed to the next gateway or proxy.


Provides a space for you to type the digits that should  be discarded.


Specifies that a prefix of one or more numbers must be added to this phone number before it is routed to the next gateway or proxy.


Provides a space for you to type the digits that should be added.


Lists the available registered destinations of the type specified.


Specifies the namespace for this pattern.


Provides space to type a pattern. This pattern specifies the range to be used in a rule.


Specifies that all telephone numbers beginning with this number pattern should be included in the rule.


Specifies that the rule is enabled.


Displays a list of all the available gateways and proxies.


Provides a space to type account details.


Provides a space to type phone details.


Displays the Q931 address of the alias.


Provides a space to edit the Q931 address.


Provides a space to type the registration details


Displays ID details


Displays a list of aliases.


Displays the RAS address of the alias.


Displays the time that the alias was registered.


Displays the time that the alias was last refreshed.


Displays an expiry time.


Provides a space to type the name of the computer running Gatekeeper.


Specifies that Gatekeeper is running on this local computer


Specifies that Gatekeeper is running on another computer.


Specifies that receiving and sending audio media through firewalls is allowed.


Specifies that receiving and sending video media through firewalls is allowed.


Specifies that bidirectional data sharing and application sharing through firewalls is allowed.  Remote users can access files, run programs, and manage desktops.


Specifies that calls placed from outside the local network are allowed into the local network.

For more information, see To enable the H.323 protocol rule


Specifies that calls placed from inside the network are allowed out of the local network.

For more information, see To enable the H.323 protocol rule


Specifies that ISA Server will use the H.323 Gatekeeper specified.

To enable the H.323 protocol rule;  H.323 Gatekeeper


Provides a space for you to type the name of the H.323 Gatekeeper that the ISA Server will use.

For more information, see To enable the H.323 protocol rule;  H.323 Gatekeeper


Specifies that DNS does not query for H.323 Gatekeepers on the Internet.  Only type A endpoint, proxy SRV, and proxy TXT queries will be made.

For more information, see To enable the H.323 protocol rule;   H.323Gatekeeper


Provdes space for you to type the name of the dial-up entry.

Dial-up entries specify how the ISA Server will connect to the Internet.

For more information, see Configuring dial-up entries


(Optional) Provides a space for you to type a description of the dial-up entry.


 Provides a space for you to type the name of the network dial-up connection.

Dial-up entries specify how the ISA Server will connect to the Internet. If the server belongs to an array you can only configure dial-up entries for network dial-up connections that are configured on all the ISA Servers in the array.

For more information, see Configuring dial-up entries


Click to select a connection from a list of network dial-up connections.


Specifies that credentials should be provided for permission to access the dial-up connection.


Provides a space for you to type the user name for a user who has permission to access the dial-up connection.


Click to select a user account for use with a dial-up connection.


Click to select a user name for a dial-up connection.


Provides a space for you to type the password for a user who has permission to access the dial-up connection.


Displays a list of network dial-up connections.

Dial-up entries specify how the ISA Server will connect to the Internet. If the server belongs to an array, you can only configure dial-up entries for network dial-up connections that are configured on all the ISA Servers in the array.

For more information, see Configuring dial-up entries


Specifies the anticipated number of daily connections.

Tuning can refine ISA Server performance to your specific needs. You can adjust the performance settings to the number of daily connections that you expect for your site.

For more information, see Tuning performance


Displays a list of application settings for the server copy of the Firewall client configuration file.

Application lists the sections in the file, Key lists the keys that can be included in each section, and Value describes the values to which the keys can be set.

For more information, see Firewall client application settings


Click to add a new application setting for the Firewall client configuration file.


Click to modify an application setting for the Firewall client configuration file.


Click to delete an application setting for the Firewall client configuration file.


Provides a space to type a section in an application entry setting.

Application lists the sections in the file, Key lists the keys that can be included in each section, and Value describes the values to which the keys can be set.

For more information, see Firewall client components


Provides a space to type a key to be included in the section.

Application lists the sections in the file, Key lists the keys that can be included in each section, and Value describes the values to which the keys can be set.

For more information, see Firewall client components


Provides a space to type a value for the key.

Application lists the sections in the file, Key lists the keys that can be included in each section, and Value describes the values to which the keys can be set.

For more information, see Firewall client components


Provides a space to type the name of the user generating the report.

In a situation where ISA Server belongs to a multi-server array, or an ISA Server is being remotely administered, a user generating a report must have appropriate permissions to access and use the reporting mechanism on an array.

For more information, see Scheduling reports


Provides a space to type the name of the domain for the user generating the report.

In a situation where ISA Server belongs to a multi-server array, or an ISA Server is being remotely administered, a user generating a report must have appropriate permissions to access and use the reporting mechanism on an array.

For more information, see Scheduling reports


Provides a space to type a password for the user generating the report.

In a situation where ISA Server belongs to a multi-server array, or an ISA Server is being remotely administered, a user generating a report must have appropriate permissions to access and use the reporting mechanism on an array.

For more information, see Scheduling reports


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


No help is available for the specified topic.


Click to limit the number of log files saved.


Specifies that the filter should check for DNS host name overflow intrusion attempts.

The DNS intrusion detection filter intercepts and analyzes DNS traffic destined for the internal network. A DNS host overflow intrusion occurs when a DNS response for a host name exceeds a certain fixed length.

For more information, see Intrusion detection filters


Specifies that the filter should check for DNS length overflow intrusion attempts.

The DNS intrusion detection filter intercepts and analyzes DNS traffic destined for the internal network. A DNS length overflow intrusion occurs when a DNS response for IP addresses exceeds a specified length of four bytes.

For more information, see Intrusion detection filters


Specifies that the filter should check for DNS zone transfer from privileged ports intrusion attempts

The DNS intrusion detection filter intercepts and analyzes DNS traffic destined for the internal network. A DNS zone transfer from privileged ports (1-1024) intrusion occurs when a client system uses a DNS client application to transzer zones from an internal DNS server.

For more information, see Intrusion detection filters


Specifies that the filter should check for DNS zone transfer from high ports intrusion attempts

The DNS intrusion detection filter intercepts and analyzes DNS traffic destined for the internal network. A DNS zone transfer from high ports (above 1024) intrusion occurs when a when a client system uses a DNS client application to transzer zones from an internal DNS server

For more information, see Intrusion detection filters


Specifies that Hypertext Transfer Protocol (HTTP) requests from Firewall and SecureNAT clients should be redirected to the Web Proxy service on the local ISA Server computer.

The HTTP redirector filter provided with ISA Server forwards HTTP requests from Firewall and SecureNAT clients to the Web Proxy service, thus enabling caching of the object, even if the client does not configure a Web browser to use ISA Server.

For more information, see HTTP redirector filter


Specifies that if the local ISA Server computer is unavailable, that requests should be directed to the requested Web server. This means that the request will not be cached.

The Hypertext Transfer Protocol (HTTP) redirector filter provided with ISA Server forwards HTTP requests from Firewall and SecureNAT clients to the Web Proxy service, thus enabling caching of the object, even if the client does not configure a Web browser to use ISA Server.

For more information, see HTTP redirector filter


Specifies that the request should be sent directly to the specified Web server, bypassing the Web Proxy service. This means that the request will not be cached.

The Hypertext Transfer Protocol (HTTP) redirector filter provided with ISA Server forwards HTTP requests from Firewall and SecureNAT clients to the Web Proxy service, thus enabling caching of the object, even if the client does not configure a Web browser to use ISA Server.

For more information, see HTTP redirector filter


Specifies that requests from Firewall and SecureNAT clients should be rejected. This forces clients who want to use Hypertext Transfer Protocol (HTTP) to be set up as Web Proxy clients.

The Hypertext Transfer Protocol (HTTP) redirector filter provided with ISA Server forwards HTTP requests from Firewall and SecureNAT clients to the Web Proxy service, thus enabling caching of the object, even if the client does not configure a Web browser to use ISA Server.

For more information, see HTTP redirector filter


Provides space to type the port number on which ISA Server should listen for requests from SOCKS clients.

The SOCKS filter provided with ISA Server forwards requests from SOCKS applications to the Firewall service.

For more information, see SOCKS filter


Specifies that the media stream should not be accessible from a local Windows Media Technologies (WMT) server.

The Streaming media filter provided with ISA Server allows Firewall and SecureNAT clients to use selected Streaming Media protocols to access media streaming servers. Live stream splitting refers to the ability of filters to obtain information once from the Internet, and then make it available locally for access by other clients.

For more information, see  Streaming media filter


Specifies that the media stream should be accessible from a single local Windows Media Technologies (WMT) server. This option should only be selected if a single ISA Server computer allows client access to WMT servers.

The Streaming media filter provided with ISA Server allows Firewall and SecureNAT clients to use selected Streaming Media protocols to access media streaming servers. Live stream splitting refers to the ability of filters to obtain information once from the Internet, and then make it available locally for access by other clients.

For more information, see Streaming media filter


Specifies that the media stream should be accessible from more than one local Windows Media Technologies (WMT) servers.

The Streaming media filter provided with ISA Server allows Firewall and SecureNAT clients to use selected Streaming Media protocols to access media streaming servers. Live stream splitting refers to the ability of filters to obtain information once from the Internet, and then make it available locally for access by other clients.

For more information, see Streaming media filter


Provides a space to type the IP address of the local Windows Media Technologies (WMT) server.

The Streaming media filter provided with ISA Server allows Firewall and SecureNAT clients to use selected Streaming Media protocols to access media streaming servers. Live stream splitting refers to the ability of filters to obtain information once from the Internet, and then make it available locally for access by other clients.

For more information, see Streaming media filter


Click to enter a server name and find its related IP address


Displays a list of IP addresses of local Windows Media Technologies (WMT) servers.

The Streaming media filter provided with ISA Server allows Firewall and SecureNAT clients to use selected Streaming Media protocols to access media streaming servers. Live stream splitting refers to the ability of filters to obtain information once from the Internet, and then make it available locally for access by other clients.

For more information, see Streaming media filter


Click to add a Windows Media Technologies (WMT) server address


Click to remove a Windows Media Technologies (WMT) server address


Click to edit a Windows Media Technologies (WMT) server address


Specifies details of the administrator for the WMT server.


Provides a space to type the user name for the WMT server administrator..

The user must be a member of the Netshow Adminstrators groups on each WMT server.


Provides a space to type the password for the WMT server administrator.


Provides a space to type the password again, for confirmation.


Click to find user account details.


Displays a list of attachments that the SMTP filter should check for. Attachments can be specified by priority order, category and value. An action, such as delete, hold, or forward the message, can be specified.

The Simple Mail Transfer Protocol (SMTP) filter intercepts all SMTP traffic that arrives on port 25 of the ISA Server computer. The filter inspects the traffic and only passes it on if the rules allow. The SMTP filter can filter incoming mail based the type of attachments included with the message.

For more information, see SMTP filter


Click to add a new attachment type that should be checked by the Simple Mail Transfer Protocol (SMTP)  filter.


Click to remove an attachment type so that the Simple Mail Transfer Protocol (SMTP) filter no longer checks for it.


Click to edit details of an attachment type checked by the Simple Mail Transfer Protocol (SMTP)  filter.


Click to move an attachment type up in order of prioirity. This changes the order in which actions should be applied when these attachments are found.


Click to move an attachment type down in order of prioirity. This changes the order in which actions should be applied when these attachments are found.


Specifies that the Simple Mail Transfer Protocol (SMTP) filter should check for specified attachments in incoming mail.  Actions can be specified based on the SMTP filter detecting these attachments. Attachments can be specified by priority order, category and value.

The Simple Mail Transfer Protocol (SMTP) filter intercepts all SMTP traffic that arrives on port 25 of the ISA Server computer. The filter inspects the traffic and only passes it on if the rules allow. The SMTP filter can filter incoming mail based the type of attachments included with the message.

For more information, see SMTP filter


Specifies that the Simple Mail Transfer Protocol (SMTP) filter should filter incoming messages according to the name of attachments.


Specifies that the Simple Mail Transfer Protocol (SMTP) filter should filter incoming messages according to attachment extensions.


Specifies that the Simple Mail Transfer Protocol (SMTP) filter should filter incoming messages in accordance with a specified size limit.


Provides a space to type the name of an attachment that should be filtered by the Simple Mail Transfer Protocol (SMTP) filter.


Provides a space to type an attachment extension that should be filtered by the Simple Mail Transfer Protocol (SMTP) filter.


Provides a space to type a size limit for attachments. Anything above this limit should be filtered by the Simple Mail Transfer Protocol (SMTP) filter.


Specifies what action should be taken if a attachment is detected by the Simple Mail Transfer Protocol (SMTP) filter.


Provides space for you to type the name of a user who is denied access to the Simple Mail Transfer Protocol (SMTP) server.

The Simple Mail Transfer Protocol (SMTP) filter intercepts all SMTP traffic that arrives on port 25 of the ISA Server computer. The filter inspects the traffic and only passes it on if the rules allow. The SMTP filter can filter incoming mail based on source users, or domain and recipient.

For more information, see SMTP filter


Click to add a user to the list of users denied access to the Simple Mail Transfer Protocol (SMTP) server.


Click to remove a user from the list of users denied access to the Simple Mail Transfer Protocol (SMTP) server.


Displays a list of users who are denied access to the Simple Mail Transfer Protocol (SMTP) server.


Provides space for you to type the name of a domain that is denied access to the Simple Mail Transfer Protocol (SMTP) server.

The Simple Mail Transfer Protocol (SMTP) filter intercepts all SMTP traffic that arrives on port 25 of the ISA Server computer. The filter inspects the traffic and only passes it on if the rules allow. The SMTP filter can filter incoming mail based on source users, or domain and recipient.

For more information, see SMTP filter


Click to add a domain to the list of domains denied access to the Simple Mail Transfer Protocol (SMTP) server.


Click to remove a domain from the list of domains denied access to the Simple Mail Transfer Protocol (SMTP) server.


Displays a list of domains that are denied access to the Simple Mail Transfer Protocol (SMTP) server


Displays a list of keywords that should be checked for in incoming mail.  Actions can be specified based on the Simple Mail Transfer Protocol (SMTP) filter finding these keywords.

The SMTP filter intercepts all SMTP traffic that arrives on port 25 of the ISA Server computer. The filter inspects the traffic and only passes it on if the rules allow. The SMTP filter can filter mail based on keywords found in incoming messages.

For more information, see SMTP filter


Click to add a new keyword.


Click to remove a keyword


Click to edit a keyword.


Click to move a keyword up in order of prioirity. This changes the order in which actions should be applied when keywords are found.


Click to move a keyword down in order of prioirity. This changes the order in which actions should be applied when keywords are found.


Specifies that the Simple Mail Transfer Protocol (SMTP) filter should check for specified keywords in incoming mail.  Actions can be specified based on the SMTP filter finding these keywords.

The SMTP filter intercepts all SMTP traffic that arrives on port 25 of the ISA Server computer. The filter inspects the traffic and only passes it on if the rules allow. The SMTP filter can filter mail based on keywords found in incoming messages.

For more information, see SMTP filter


Provides a space to type a keyword that should be filtered by the Simple Mail Transfer Protocol (SMTP) filter.


Specifies that action should be taken if the keyword is found in the header or body of the message.


Specifies that action should be taken if the keyword is found in the message header.


Specifies that action should be taken if the keyword is found in the body of the message.


Specifies what action should be taken if a keyword is detected by the Simple Mail Transfer Protocol (SMTP) filter.


Displays a list of Simple Mail Transfer Protocol (SMTP) commands, including the name of the command, whether it is enabled and its maximum length.

The SMTP filter can check for buffer overrun attacks, which occur when SMTP commands are specified with a line length exceeding their specified value.

For more information, see SMTP filter


Click to add a Simple Mail Transfer Protocol (SMTP) command.


Click to remove a Simple Mail Transfer Protocol (SMTP) command.


Click to edit a Simple Mail Transfer Protocol (SMTP) command.


Specifies that the Simple Mail Transfer Protocol (SMTP) command is enabled.


Provides a space to type the name of a Simple Mail Transfer Protocol (SMTP) command.


Provides a space to type the maximum length (in bytes) of a Simple Mail Transfer Protocol (SMTP) command.


No help is available for the specified topic.


Provides space to type the user name for the account.


Click to select a user account.


Provides space to type the account password.


Provides space to retype the password.


Specifies that Internet access will be limited by users and groups.

Choosing only this option means that Internet access cannot be limited by specific IP address. This may have repercussions for SecureNAT clients, which are identified by IP address.


Specifies that Internet access will be limited by computer names or IP address


Specifies that Internet access will be limited by scheduled times.


Specifies that Internet access will be limited by destination sets.


Specifies the effective bandwidth for sending data to the external network, for example the Internet.

ISA Server uses this effective bandwidth as the basis for determining the actual bandwidth that will be assigned to the network connection. Based on this value, outgoing traffic sent by servers or arrays on this network connection will be prioritized according to any applicable bandwidth rules that may exist.

For more information, see Determining effective bandwidth


Specifies the effective bandwidth for sending data to the external network, for example the Internet.


Specifies that the bandwidth control is enabled for this network connection.


Specifies the effective bandwidth for this network connection.

The effective bandwidth for an array will be determined by how many modems are on all the servers in the array.

For more information, see Determining effective bandwidth


Provides a space for you to type the effective bandwidth for this network connection.

The effective bandwidth for an array will be determined by how many modems are on all the servers in the array.

For more information, see Determining effective bandwidth


Specifies the configuration of the effective bandwidth for a network connection.

ISA Server uses this effective bandwidth as the basis for determining the actual bandwidth that will be assigned to a particular connection. Based on this value, outgoing traffic sent by this connection will be prioritized according to any applicable bandwidth rules.which may exist.


Specifies the configuration of the effective bandwidth for a network connection


Specifies that the bandwidth control is enabled for this network connection.


Specifies the effective bandwidth, in Kbit/Sec, for this network connection.

The effective bandwidth specified is based on the maximum bandwidth of the connection, which will be determined by several factors. For a modem these include the actual speed of the modem and compression. You should consider the lowest maximum bandwidth available for the devices on the ISA Server.

For more information, see Determining effective bandwidth


Provides a space for you to type the effective bandwidth, in Kbit/Sec, for this network connection.

The effective bandwidth specified is based on the maximum bandwidth of the connection, which will be determined by several factors, which for a modem include the actual speed of the modem and compression. You should consider the lowest maximum bandwidth available for the devices on the ISA Server.

For more information, see Determining effective bandwidth


Specifies that no enterprise policy should be applied to the array.  With this setting, the array administrator can create any access rule.

Note: If you choose this setting, you cannot subsequently modify settings for this array to be enterprise-only.

For more information, see Applying enterprise policy


Specifies that an enterprise policy will be applied to the array.

If only an enterprise policy is applied to the array, then no new rules can be added at the array level.

Note: Packet filtering cannot be enabled at the enterprise level, though the enterprise administrator can determine whether the array administrator will have packet filtering available.  Similarly, publishing rules cannot be created at the enterprise level, but the enterprise administrator can specify whether an array is allowed to create publishing rules in order to publish servers.

For more information, see Applying enterprise policy


Displays a list of enterprise policies that can be applied to the array.


Specifies that an array-level policy should be used.

If a combined enterprise and array policy is used, then the enterprise policy overrides the array policy. This means that the array policy can limit enterprise policy, but cannot be more permissive.


Specifies that publishing should be allowed at array level.

Publishing rules cannot be created at the enterprise level, but the enterprise administrator can specify whether an array is allowed to create Web publishing rules in order to securely publish Web content to the Internet, and server publishing rules to make internal servers available to external clients.


Specifies that packet filtering should be enabled at the array-level.

Packet filtering cannot be enabled at the enterprise level, but the enterprise administrator can determine whether to enable packet filtering at the array level.


Provides a space for you to type the name of the server.

For more information, see ISA Server Overview


Displays ISA Server type.


Displays a list of dial-up entries that are configured on the ISA Server computer. If no dial-up entries are configured, this list is empty.

For more information, see Routing requests from Firewall and SecureNAT clients


Displays a list of dial-up entries configured on the ISA Server computer. If no dial-up entries are configured, this list is empty.

For more information, see Routing requests from Firewall and SecureNAT clients


Applies the rule to destinations.

All internal destinations applies the rule to all computers that are specified in the local address table or the local domain table. All external destinations applies  the rule to all computers that are not specified in the local address table or the local domain table. Selected destination set applies the rule to all computers included in the destination set specified. All destinations except selected set applies the rule to all computers except for those in the specified destination set.

For more information, see Configuring destination sets


Displays a list of defined schedules.

A schedule is a predefined policy element that determines when a rule is put into effect.

For more information, see Configuring schedules


Displays a list of content groups.

Content groups specify a set of file and MIME types. These content groups are used when defining site and content rules, to control Web access. A complete list of MIME types and file extensions can be found on the linked page.

For more information, see Configuring content groups


Displays a list of dial-up entries configured on the ISA Server computer. If no dial-up entries are configured, this list is empty.

For more information, see Routing Web requests


Displays a list of dial-up entries configured on the ISA Server computer. If no dial-up entries are configured, this list is empty.

 For more information, see Routing Web requests


Displays a list of servers. Select a computer whose routing table should be used in determining the LAT

A routing table contains internal network addresses. The Windows 2000 routing table defines all the IP addresses available in your internal network.


Provides a space for you to type the name of the network dial-up connection.

Dial-up entries specify how the ISA Server will connect to the Internet.

For more information, see Configuring dial-up entries


Displays a list of network dial-up connections.

Dial-up entries specify how the ISA Server will connect to the Internet.

For more information, see Configuring dial-up entries


Provides a space for you to type the name of the mail server.


Click to find Internet Protocol (IP) addresses that correspond to the specified mail server.


Displays a list of Internet Protocol (IP) addresses that correspond to the specified mail server.


More information about this topic can be found in ISA Server Help.