Windows Server 2022 — RAS Gateway stops forwarding traffic after reboot — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

RRAS on Windows Server 2022 intermittently stops forwarding traffic. Users report failed remote access and site-to-site routing interruption. Monitoring shows packet loss and elevated latency.

Environment & Reproduction

Issue appears after service restart, patching, or network stack rebind. Reproduce by restarting RRAS and validating route propagation.

Get-Service RemoteAccess
Get-NetRoute -AddressFamily IPv4 | Sort-Object RouteMetric
Get-WinEvent -LogName System -MaxEvents 50 | ? {$_.Message -match 'RemoteAccess|RRAS'}

Root Cause Analysis

Typical causes include stale route entries, interface metric drift, service dependency race, or conflicting static route policy.

Quick Triage

Confirm service health, route table consistency, and next-hop reachability before making persistent changes.

Test-NetConnection -ComputerName 
Get-NetIPInterface | Sort-Object InterfaceMetric

Step-by-Step Diagnosis

Validate interface binding, RRAS configuration, and route advertisement behavior.

Get-RemoteAccess
Get-NetAdapterBinding -Name '*' | ? {$_.ComponentID -match 'ms_tcpip'}

Solution — Primary Fix

Re-apply interface metrics, restart dependent services in order, and clear stale routes.

Restart-Service RasMan
Restart-Service RemoteAccess
route -f
Restart-Computer -Force

Solution — Alternative Approaches

Use persistent static routes and enforce startup ordering with service dependencies for stability.

Verification & Acceptance Criteria

Traffic flows across all expected subnets for 30+ minutes with zero packet-loss alarms.

Get-NetRoute
Test-NetConnection -ComputerName  -Port 3389

Rollback Plan

Restore exported RRAS configuration and prior route table snapshots if behavior regresses.

Prevention & Hardening

Standardize metric policy, baseline route checks, and include RRAS health probes in monitoring.

Related Errors & Cross-Refs

Often paired with BGP neighbor flaps, GRE tunnel drops, and firewall profile misapplication.

Related tutorial: View the step-by-step tutorial for Windows Server 2022.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn: RRAS and routing diagnostics, route management, and RemoteAccess service guidance.