Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 254192 - Last Review: December 3, 2007 - Revision: 5.4
Cannot administer Routing and Remote Access service when the Remote Registry service is stopped
This article was previously published under Q254192
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.
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.
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:
- On the Start menu, point to Programs, point to Administrative Tools, and then click Services.
- Click Routing And Remote Access, and then click the Stop symbol.
- Click Remote Registry Service, and then click the Start symbol.
- 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.
- Open Routing and Remote Access.
- Right-click the computer name that you want to
reset the Routing and Remote Access service for.
- Click Disable Routing and Remote
Access.
- Right-click the computer name that you want to
reset the Routing and Remote Access service for.
- Click Configure and Enable Routing and Remote
Access.
- Follow the instructions on the screen in the setup
wizard.
- 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.
Make sure the following services are started:
- Remote Access Auto Connection Manager
- Remote Access Connection Manager
- Routing and Remote Access
- Telephony
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
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate