RRAS: IPv4 routing should be enabled on the RRAS server for routing protocols like DHCP Relay, RIP and IGMP to run

  • Article

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

Issue

IPv4 routing is disabled on the Routing and Remote Access server.

Impact

If IPv4 routing is disabled, then IPv4 routing protocols like DHCP Relay, RIP, or IGMP cannot run.

RRAS routing protocols and components require that the server be configured as an RRAS router. If IPv4 routing is disabled, then IPv4 routing protocols and components cannot operate.

Resolution

Use 'Routing and Remote Access' in Server Manager to enable IPv4 routing if you want to use IPv4 routing protocols.

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

To enable IPv4 routing on the RRAS server

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

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

  3. Right-click Routing and Remote Access, and then click Properties.

  4. On the General tab, select IPv4 Router, select either Local area network (LAN) routing only or LAN and demand-dial routing per your organization’s design and requirements, and then click OK to save your changes.

  5. Run the NPAS Best Practice Analyzer again. If this rule still displays as non-compliant, then restart the RRAS server by right-clicking Routing and Remote Access, clicking All Tasks, and then clicking Restart.

Additional references

For more information about routing, see Routing Technologies (https://go.microsoft.com/fwlink/?linkid=153799).

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