Скачати 326.71 Kb.
After you have installed NPS, you can use this procedure to manage the local NPS server by using the NPS Microsoft Management Console (MMC).
The NPS console differs from use of the NPS MMC snap-in in the following ways:
The NPS console is installed by default when you install NPS.
The NPS console is used to manage the local NPS server only; you cannot use the NPS console to manage remote NPS servers.
You can use the NPS MMC snap-in to create a custom MMC console that allows you to manage remote NPS servers in addition to managing the local NPS server.
To complete this procedure, you must be a member of the Administrators group.
To configure the local NPS server by using the NPS console
A computer with multiple network adapters installed is known as a multihomed computer. When you use multiple network adapters in an NPS server, you can configure the following:
The network adapters that do and do not send and receive RADIUS traffic.
On a per-network adapter basis, whether NPS monitors RADIUS traffic on Internet Protocol version 4 (IPv4), IPv6, or both IPv4 and IPv6.
The UDP ports over which RADIUS traffic is sent and received on a per-protocol (IPv4 or IPv6), per-network adapter basis.
By default, NPS listens for RADIUS traffic on ports 1812, 1813, 1645, and 1646 for both IPv6 and IPv4 for all installed network adapters. Because NPS automatically uses all network adapters for RADIUS traffic, you only need to specify the network adapters that you want NPS to use for RADIUS traffic when you want to prevent NPS from using an adapter for RADIUS traffic.
If you uninstall either IPv4 or IPv6 on a network adapter, NPS does not monitor RADIUS traffic for the uninstalled protocol.
On an NPS server that has multiple network adapters installed, you might want to configure NPS to send RADIUS traffic only on a specific adapter.
For example, one network adapter installed in the NPS server might lead to a network segment that does not contain RADIUS clients, while a second network adapter provides NPS with a network path to its configured RADIUS clients. In this scenario it is important to direct NPS to use the second network adapter for all RADIUS traffic.
In another example, if your NPS server has three network adapters installed, but you only want NPS to use two of the adapters for RADIUS traffic, you should configure port information for the two adapters only. By excluding port configuration for the third adapter, you prevent NPS from using the adapter for RADIUS traffic.
When you use the procedure in ^ , you can configure NPS to listen for and send RADIUS traffic on a network adapter by using the following syntax:
IPv4 traffic syntax: IPAddress:UDPport, where IPAddress is the IPv4 address that is configured on the network adapter over which you want to send RADIUS traffic, and UDPport is the RADIUS port number that you want to use for RADIUS authentication or accounting traffic.
IPv6 traffic syntax: [IPv6Address]:UDPport, where the brackets around IPv6Address are required, IPv6Address is the IPv6 address that is configured on the network adapter over which you want to send RADIUS traffic, and UDPport is the RADIUS port number that you want to use for RADIUS authentication or accounting traffic.
The following characters can be used as delimiters for configuring IP address and UDP port information:
Address/port delimiter: colon (:)
Port delimiter: comma (,)
Interface delimiter: semicolon (;)
Make sure that your network access servers are configured with the same RADIUS UDP ports that you configure on your NPS servers. The RADIUS standard UDP ports defined in RFCs 2865 and 2866 are 1812 for authentication and 1813 for accounting; however, some access servers are configured by default to use UDP port 1645 for authentication requests and UDP port 1646 for accounting requests.
If you do not use the default RADIUS ports, you must configure exceptions on the firewall for the local computer to allow RADIUS traffic on the new ports.
|Step-by-Step Guide for Configuring Network Load Balancing with Terminal Services: Windows Server 2008||Step-by-Step Guide for Configuring a Two-Node File Server Failover Cluster in Windows Server 2008|
|Step-by-Step Guide for Configuring a Two-Node Print Server Failover Cluster in Windows Server 2008||Server Core Installation Option of Windows Server 2008 Step-By-Step Guide|
|Step-by-Step Guide for File Server Resource Manager in Windows Server 2008||Step-by-Step Guide for Windows Deployment Services in Windows Server 2008|
|Step-by-Step Guide for Storage Manager for sans in Windows Server 2008||Services for nfs step-by-Step Guide for Windows Server 2008|
|Windows Server 2008 Active Directory Certificate Services Step-By-Step Guide||Windows Server 2008 ts licensing Step-By-Step Guide|