Re: Remote Access Connection Manager auto-starts

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: "Eric" <bauersachs@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 8 May 2006 18:12:21 +0200

Hello Andreas
If rasman is disabled then it isn't anymore possible to make VPN connections
(for whatever reason). So it can't be disabled.
On my machine (also a Windows Server 2003) I also have rasman set to manual
and it doesn't start.at boot-time.

Eric

BTW:
Boot-time Telephony: you're right. But that's another problem (see thread
above, "client impersonation"). Here I'm just looking for a workaround about
the service problem.

.

References:
- Remote Access Connection Manager auto-starts
  - From: Eric
- Re: Remote Access Connection Manager auto-starts
  - From: Andreas Marschall [MVP TAPI]

Prev by Date: Re: Re:TAPI 3.0 - Auto Select Lines
Next by Date: Re: client impersonation
Previous by thread: Re: Remote Access Connection Manager auto-starts
Next by thread: seeking for a papers/books about TAPI programing in Win32
Index(es):
- Date
- Thread

Relevant Pages

Re: Rasman - 20027
... case or there is a mismatch in ndiswan and rasman version. ... "Michael S.Androsov" wrote in message ... > On a Windows Server 2000 server I received in the Event Log next ...
(microsoft.public.win2000.ras_routing)
Rasman - 20027
... On a Windows Server 2000 server I received in the Event Log next message: ... Source: Rasman ... Remote Access Connection Manager could not start because NDISWAN could not be opened. ...
(microsoft.public.win2000.ras_routing)