Access denied in routing and remote access MMC

  • Thread starter Thread starter Nick-V
  • Start date Start date
N

Nick-V

About a year ago I posted a problem and now have the solution (RRAS
and EMWAC) - hope it helps others.

MY ORIGINAL MESSAGE
For some reason it appears that the Routing and Remote Access MMC is
being
denied access (administrator) to the Routing Interfaces details - they
are
blank.

Also, when I try to set up a new Demand-Dial Interface I eventually
get
"access denied".

NAT was set up long ago and still works fine allowing LAN clients to
connect
to The Internet. Also when I use netsh (in a basic manner!) I can see
certain interfaces etc. are still set up.

I can still change the remote access details (e.g. ports) so some
registry
details are OK.

When I disable the server it stops but I cannot then configure and
enable it
(greyed out - still shows disable). So I start the server and am asked
if I
want to enable and configure. After starting I am back to the same
position
as above.

Another clue unrelated to RRAS ... EMWAC mail server works fine but I
have
to use regedit as the control panel applet appears to be denied
access.

I'm using Win2K SP3 and all updates on a home network. Its a domain
controller with SQL (I already fixed the outbound packets rejected NAT
problem caused by SQL SP2).

Any ideas much appreciated.

THE EVENTUAL SOLUTION
My thanks to Leo Schröer who searched his emails from a year ago and
got back to me by email with this:

I looked up in my e-mail from last year and I remembered there was
also an issue with installing McAfee Groupshield for Exchange on the
same server I tried to run RRAS on. I received an e-mail from Network
Associates support, to reset permissions in the registry. When that
was done, I could install Groupsheld and I noticed RRAS also worked
fine.

Maybe it could help to reset the permissions on your server. I
received the following procedure from Network Associates:

Open the registry with REGEDT32.
Highlight HKEY_LOCAL_MACHINE.
Select 'Security | Permissions' from the menu.
Click 'Add' and add the account that is logged on while performing the
installation of GroupShield.
Give the account "Full Control" permissions.
Click 'Advanced...' and check the option 'Reset permissions on all
child objects and enable propagation of inheritable permissions'.

Click 'Apply'.
Select 'Yes' for the security pop-up message.
Click 'OK' when the "Registry Editor could not set security in key
currently selected, or some of its subkeys" message displays.

Click 'OK' twice to return to the HKEY_LOCAL_MACHINE window.
Highlight 'HKEY_LOCAL_MACHINE\SOFTWARE' and repeat Steps 3 - 10.
Highlight 'HKEY_LOCAL_MACHINE\SYSTEM' and repeat Steps 3 - 10.
Close the registry.
Run the setup for GroupShield 5.2 for Exchange 2000.

Of course you don't have my problem with Groupshield, but you can try
this anyway.

Good luck
 
Back
Top