Connectivity verifiers tab
You can verify connectivity by regularly monitoring connections from the Microsoft Forefront Threat Management Gateway computer to any specific computer or URL on any network. The following table summarizes the available connectivity methods.
| Connectivity method | Details | Usage |
|---|---|---|
PING |
When you configure this method, Forefront TMG sends a Ping request (ICMP ECHO_REQUEST) to the specified server, and waits for an ICMP ECHO_REPLY. |
Use this method to verify that a server is running and can be reached by Forefront TMG. |
TCP connect |
When you configure this method, Forefront TMG tries to establish a TCP connection to a specific port on the specified server. |
Use this method to verify that a specific service is running on the server and can be reached by Forefront TMG. |
HTTP request |
When you configure this method, Forefront TMG sends an HTTP GET request and waits for the reply. |
Use this method to verify that a Web server is running and can be reached by Forefront TMG. |
To use one of these methods to monitor connectivity to a server, you create and configure a connectivity verifier, and place it in one of the following predefined groups: Active Directory, DHCP, DNS, Published Servers, Web (Internet), and Others. For example, suppose you publish servers running FTP, Microsoft SQL Server™, and Microsoft Exchange Server. You can create a connectivity verifier for each server, and group them all in the Published Servers group. In another scenario, you might want to validate that Forefront TMG has connectivity to Web sites on the External network. To do this, you might define HTTP connectivity verifiers for each Web site that you want to verify, and group them in the Web (Internet) group.
Connectivity is verified by default every 30 seconds. You can change this interval, by using the Refresh rate script, described in "Setting the Refresh Rate for Connectivity Verifiers" at the Microsoft TechNet Web site.