Saturday, August 22, 2020

Add authorized host

For static routes to function properly, the address of the next hop computer in the static route must be recognized by the pool as an authorized host. Use this dialog box to add an authorized host.

Server

This is the address that servers in the pool use to identify the authorized host.

FQDN

Click to enter the fully qualified domain name (FQDN) of the authorized host.

Note: Enter the FQDN of the authorized host if you configured a static route on the pool that specifies the next hop computer using its FQDN.

IP address

Click to enter the IP address of the authorized host. The IP address 0.0.0.0 is not allowed. Multicast addresses ranging from 224.0.0.0 to 239.255.255.255 are also not allowed. All other IP addresses are allowed.

Note: Enter the IP address of the authorized host if you configured a static route on the pool that specifies the next hop computer using its IP address.

Settings

These settings are applied to connections made from servers in the pool to the authorized host.

Outbound Only

When selected, this setting specifies that the authorized host cannot open a connection to the servers in this pool. When cleared, this setting specifies that the authorized host can open connections to the servers in this pool.

Note: This setting is only used in conjunction with static routes.

Throttle As Server

When selected, this setting specifies that greater throughput to the authorized host is enabled than is allowed when connecting to a client computer. When cleared, this setting specifies that greater restrictions are imposed on connections made from servers in this pool to the authorized host.

Treat As Authenticated

When selected, this setting specifies that clients that are connected to the authorized host are considered to have already been authenticated and are therefore not challenged by the servers in the pool.

Learn More Online

Click to expand or collapse

When you add an authorized host that is treated as authenticated, you should mitigate the risks by implementing additional security measures, such as a firewall or IPsec, around the authorized host.

For details, see the Operations section of the Office Communications Server Technical Library.

No comments:

Post a Comment