Remote Access Connection Manager hangs

Hi all.

I am trying to set-up a VPN connection from a Windows 2000 Server to another
machine but found I could not select VPN connection from the network
connection wizard. Subsequent searching on the web revealed that this was
because the Remote Access Connection Manager service was disabled (don't
know why). So anyway, I re-enabled it but it will not start no matter what
I do, including rebooting. Sometimes I get 7022 error in the system log
saying that the service hung on starting. Other times it will just stay in
the "starting" state and never report a problem or successfully start. Any
suggestions of how to fix this? Can this component be re-installed?
Apologies if wrong ng.

TIA.

John.

 

You need to have all of these services enabled
Telephony
Remote Access Connection Manager
Remote Access Auto Connection Manager

If you enable all of them and still have the problem, try start~run~sfc /scannow and see if that helps things out.

 

All are enabled already. I tried what you suggested and it asked for the 2000 Server CD. Does this mean that it is restoring original files over files updated from Service Packs? Need to reboot to test as the service is jammed in the starting state at the moment. Will try later tonight when people are not using it.

Thanks for the help.

 

If it finds a damaged file (which it sounds like yours has) and replaces it, the replacement will be whatever version was on your CD. If it is slipstreamed with a SP then that's the file version you will get. And you may then need to reapply any later updates.

However, the utility will not simply see a newer file version and decided it is bad.

 

OK. Just completed the reboot and the service has again got stuck in the "starting" state. Really got me puzzled this one. Help!

 

start~run~cmd
chkdsk /r

May help. Can't hurt.

 

OK, did that and no joy. Someone in a Microsoft forum suggested that I enable tracing to see what is going on. Unfortunately they didn't say how to do this. I worked out that there is a registry setting to control tracing - HKLM\Software\Microsoft\Tracing\RASMAN - but setting EnableFileTracing and EnableConsoleTracing to 1 followed by a reboot did not seem to have any effect.

Then I saw in another ng post that you could do

netsh ras set tracing * enabled

Tried that but it is too late, as the service has already stopped responding. How can I get tracing switched on in time to log the problem as it occurs?

TIA.