Why This Error Happens
Error 1342 typically occurs when the Routing and Remote Access (RRAS) service or a related network server component is in a conflicting state where the system reports it as “enabled” but the underlying service handler cannot properly acknowledge or reinitialize the connection. This usually stems from a corrupted service configuration in the registry, a stale lock left over from an improper shutdown, or a permissions mismatch preventing the Local System account from re-negotiating the server state. In some cases, a third-party VPN or firewall tool interferes with the native RRAS/Server service handshake, triggering this error message.
Step-by-Step Resolution Guide
Step 1: Verify Current Service Status
- Open Services.msc (Win + R, type
services.msc, press Enter). - Locate Routing and Remote Access and check if the Status column shows “Running” despite the feature being disabled in Server Manager or Network Settings.
- Right-click the service and select Stop.
Step 2: Reset the Service Configuration
- Open Command Prompt as Administrator.
- Run:
sc config RemoteAccess start= demand - Run:
net stop RemoteAccessfollowed bynet start RemoteAccess - If the command returns Error 1342 again, proceed to registry validation.
Step 3: Validate Registry Keys
- Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemoteAccess - Check the Start value; it should be set to
3(Manual) or2(Automatic), not4(Disabled). - Export the key as a backup before making any changes.
- Correct the value if it conflicts with the intended state, then restart the machine.
Step 4: Check for Conflicting Third-Party Software
- Temporarily disable any third-party VPN, antivirus, or firewall software that hooks into network services.
- Re-attempt enabling the server feature through Control Panel > Network and Sharing Center > Change Adapter Settings or via Server Manager if applicable.
- If the error disappears, whitelist the RRAS process in the third-party tool’s exclusion list.
Step 5: Reinstall the Network Role/Feature
- Go to Settings > Apps > Optional Features (or Server Manager > Remove Roles and Features on server SKUs).
- Remove the Routing and Remote Access or related networking role.
- Restart the PC, then reinstall the feature to force a clean configuration rebuild.
Alternative or Verification Steps
- After completing the steps, run
sc query RemoteAccessin an elevated Command Prompt — the state should correctly reflect either “STOPPED” or “RUNNING” without triggering Error 1342. - If the issue persists, use the System File Checker (
sfc /scannow) and DISM (DISM /Online /Cleanup-Image /RestoreHealth) to rule out deeper system file corruption affecting the service manager.