Routing and remote access

J

Jim

Hey,

I am trying to get routing and remote access going on my
server and have come across a wall.

Everytime I try to add my server to the list it adds it.
And I can see the service running, but when I look at the
properties it says "I do not have the required
permissions". No other items pop up like they should
under it for policies etc.

I am logged on as Administrator and we have active
directory. Is there some other group that isn't default I
need to ad Administrator to?

Help!
 
S

Shilpa Sinha [MSFT]

Hi

Maybe the following helps:

Reference Link:
=============
http://support.microsoft.com/default.aspx?scid=kb;en-us;254192&Product=win20
00

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

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
o 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.
o Resetting the Routing and Remote Access service does not reset your
remote access policies.

MORE INFORMATION
=========================
Make sure the following services are started:

o Remote Access Auto Connection Manager
o Remote Access Connection Manager
o Routing and Remote Access
o Telephony

The information in this article applies to:

o Microsoft Windows Server 2003, Standard Edition
o Microsoft Windows Server 2003, Enterprise Edition
o Microsoft Windows Server 2003, Datacenter Edition
o Microsoft Windows 2000 Server
o Microsoft Windows Small Business Server 2003, Premium Edition
o Microsoft Windows Small Business Server 2003, Standard Edition
o Microsoft Small Business Server 2000


Reference Link:
==============
http://support.microsoft.com/default.aspx?scid=kb;en-us;867518&Product=win20
00

You cannot view the Routing and Remote Access server properties after you
install the Hisecweb.inf security template on a Microsoft Windows 2000
Server-based computer

SYMPTOMS
===============
After you apply the Hisecweb.inf security template to Microsoft Windows
2000 Server, you cannot view the Routing and Remote Access server
properties. When you open Routing and Remote Access, and then you try to
view the Routing and Remote Access server properties, you receive the
following error message:

You do not have the required permissions to view the properties.

CAUSE
========
This problem typically occurs when one or more of the following services
have not started:

o Remote Access Auto Connection Manager
o Remote Access Connection Manager
o Remote Registry Service
o Routing and Remote Access
o Telephony

RESOLUTION
================
To resolve this problem, make sure that these services are started, and
make sure that the startup type is set to Automatic. To do this, follow
these steps:

1. Click Start, point Programs, point to Administrative Tools, and then
click Services.
2. Make sure that the following services are started:
o Remote Access Auto Connection Manager
o Remote Access Connection Manager
o Remote Registry Service
o Routing and Remote Access
o Telephony
3. If one or more of these services are stopped, right-click the stopped
service, and then click Start.
4. If the startup type is not set to Automatic, right-click the service,
and then click Properties. On the General tab, click the list next to
Startup Type, select Automatic, and then click OK.

The information in this article applies to:

o Microsoft Windows 2000 Datacenter Server
o Microsoft Windows 2000 Advanced Server
o Microsoft Windows 2000 Server



Shilpa Sinha
This posting is provided "AS IS" with no warranties, and confers no rights.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top