Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Cannot administer Routing and Remote Access service when the Remote Registry service is stopped

Cannot administer Routing and Remote Access service when the Remote Registry service is stopped

Symptoms

When you disable the Remote Registry service beforestarting the Routing and Remote Access service, you cannot view or change the Routing and Remote Access service configuration. If you disable the Remote Registry service while the Routing and Remote Access service is running, the Routing and Remote Access service may appear to function correctly and then experience intermittent connection failures.

When you try to view the properties of the Routing and Remote Access service server, you may receive an error message that is similar to one of the following messages:
You don't have the required permissions to view the properties.
You do not have the required permissions to view the properties.

↑ Back to the top

Cause

This behavior occurs if you have disabled the Remote Registry service and you try to configure the Routing and Remote Access service. The Routing and Remote Access service Microsoft Management Console (MMC) snap-in reads and writes registry values. (This dependency also exists when you use NetShell to configure the Routing and Remote Access service.) Any situation that requires the Routing and Remote Access service to access configuration data, such as restarting the service or rebooting the system, causes the Routing and Remote Access service to stop functioning when the Remote Registry service is disabled.

↑ Back to the top

Resolution

To resolve this behavior, stop the Routing and Remote Access service, start Remote Registry service, and then restart the Routing and Remote Access service. To do this, follow these steps:
  1. On the Start menu, point to Programs, point to Administrative Tools, and then click Services.
  2. Click Routing And Remote Access, and then click the Stop symbol.
  3. Click Remote Registry Service, and then click the Start symbol.
  4. Click Routing And Remote Access, and then click the Start symbol.

In Windows Server 2003, if the service is disabled, you may have to reset the Routing and Remote Access service. To do this, follow these steps.

Note To perform this procedure, you must be a member of the Administrators group.
  1. Open Routing and Remote Access.
  2. Right-click the computer name that you want to reset the Routing and Remote Access service for.
  3. Click Disable Routing and Remote Access.
  4. Right-click the computer name that you want to reset the Routing and Remote Access service for.
  5. Click Configure and Enable Routing and Remote Access.
  6. Follow the instructions on the screen in the setup wizard.
  7. When you are prompted to start the Routing and Remote Access service, click Yes.
Notes
  • This procedure resets the current configuration back to the default values, based on your selection of options in the Routing and Remote Access wizard. This includes removing all the IP routing protocols and their configurations.
  • Resetting the Routing and Remote Access service does not reset your remote access policies.

↑ Back to the top

More Information

Make sure the following services are started:
  • Remote Access Auto Connection Manager
  • Remote Access Connection Manager
  • Routing and Remote Access
  • Telephony

↑ Back to the top

Keywords: kb, public, nt5prb, kbprb, kbwinnetswept

↑ Back to the top

Article Info
Article ID : 254192
Revision : 6
Created on : 8/20/2020
Published on : 8/20/2020
Exists online : False
Views : 146