RRAS: The network interface <adapter name> on the RRAS server should be reachable

Updated: August 3, 2009

Applies To: Windows Server 2008 R2, Windows Server 2012, Windows Storage Server 2012

This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the Network Policy and Access Service (NPAS) Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer.

 

Operating System

Windows Server 2012, Windows Server 2008 R2

Product/Feature

Routing and Remote Access Service (RRAS)

Severity

Warning

Category

Configuration

The interface <adapter name> is in an unreachable state.

If a network interface is in an unreachable state, then clients cannot communicate with the RRAS server by using that interface.

Review the 'Unreachability Reason' in 'Routing and Remote Access' in Server Manager, and then take corrective steps.

RRAS routing requires a minimum of two reachable network interfaces. Remote access requires one reachable interface; two, if remote access clients must access resources on a private network. If one of your network interfaces is reported as unreachable by RRAS, then it cannot be used for routing or remote access.

You can examine the reason RRAS reports an interface as unreachable by using the Routing and Remote Access MMC snap-in.

Membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure.

  1. Start Server Manager. Click Start, click Administrative Tools, and then click Server Manager.

  2. In the navigation tree, expand Roles, expand Network Policy and Access Services, and then expand Routing and Remote Access.

  3. Click Network Interfaces.

  4. In the Network Interfaces list, right-click the network interface that is unreachable, and then click Unreachability reason.

  5. Based on the reason reported, take the appropriate corrective actions to restore the network interface to operation.

For more about the Routing and Remote Access role service, see Routing and Remote Access (http://go.microsoft.com/fwlink/?linkid=153482) on TechNet, and Routing and Remote Access Service in the Windows Server Technical Library.

Community Additions

ADD
Show: