Microsoft KB Archive/254192

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

Article ID: 254192

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows 2000 Server
 * Microsoft Windows Small Business Server 2003 Premium Edition
 * Microsoft Windows Small Business Server 2003 Standard Edition
 * Microsoft Small Business Server 2000 Standard Edition

-



This article was previously published under Q254192



SYMPTOMS
When you disable the Remote Registry service before starting 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.



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.



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.



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

Additional query words: win2krelnotes unable manage rras "configure and enable routing and remote access" greyed grayed out

Keywords: kbprb KB254192

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.