|
Posted by Jack Kohn on July 6, 2006, 4:17 pm
Please log in for more thread options
Eric -
Did you ever get any response to this? I'm seeing the same thing on a
handful of my servers (both Win 2000 and Win 2003.)
I also can't shut the RASMAN service down. If I try to stop it, I get
a message: "Could not stop the Remote Access Connection Manager
service on <BOXNAME>." If I try to Disable the service *and* try to
stop it, I get an error 1053 message. Nothing in Event Viewer in
either case.
Closest thing I found to a clue was this, which indicates it might be
a Java/APC issue:
http://www.chicagotech.net/troubleshooting/apc1.htm
But that doesn't seem to be the issue here.
My apologies for crossposting - but I've been hunting the internet for
hours with not much luck. (I include the mpw.server.security group
because this relates to MS06-025.)
TIA.
-jmk
On Fri, 12 May 2006 13:14:53 +0200, "Eric"
>I have the problem that the "Remote Access Connection Manager" (rasman)
>service automatically starts when booting the system, although this service
>is set to start "manual". It is dependent only of "Remote Access Auto
>Connection Manager" which is also set to "manual" and does NOT start at
>boot-time.
>It is important that is doesn't start because this causes dependent services
>to start that I don't want (longer story).
>I cannot set it to "disabled" because I need VPN and then (when connecting)
>it should start. Problem is only boot-time.
>Q: Why does "Remote Access Connection Manager" start at boot-time although
>it is set to start manual? Any ways to avoid this?
>
>Eric
>(repost, earlier already posted to TAPI newsgroup without an answer)
>
| 
XML Sitemap