RRAS: The Routing and Remote Access server must be running

  • 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

The Routing and Remote Access service is either stopped or paused.

Impact

If the Routing and Remote Access service is in a stopped or paused state, then the server cannot provide routing or remote access services to remote clients.

Resolution

Use 'Routing and Remote Access' in Server Manager to start the Routing and Remote Access service.

The RRAS service should automatically start whenever you start the computer. If it is stopped or paused, you can use this procedure to restart the service. See the next procedure for steps to ensure the service is configured to automatically start when the server starts.

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

To start the RRAS service

  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, click All Tasks, and then click Start.

To ensure that the RRAS service starts every time you start your computer, you must configure the service entry to “Automatic”.

To configure RRAS to automatically start

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

  2. In the navigation tree, expand Configuration, and then click Services.

  3. In the Services list, double-click Routing and Remote Access to display the service Properties page.

  4. On the General tab, change the Startup type list entry to Automatic (Delayed Start).

  5. Click OK to save your changes.

Additional references

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.