Re: ipsec policy agent brings machine to its knees

From: rockfox212 (rockfox212_at_netscape.net)
Date: 02/03/05 

Date: 3 Feb 2005 13:52:59 -0800

Thanks for the suggestion. Event viewer said "IPSEC driver service
failed to start due to the the following error: Cannot create a file
when that file already exists". There was a subsequent error "Unable
to create device object \Device\IPSEC. Initialization failed." Then
"IPSEC Policy Agent Service: Ipsec Driver failed to start."

Any thoughts as to what that all means?

I tried another experiment: start the IPsec policy agent first (no
problem, event viewer reports nothing) then assign the vpn policy rules
(instant death).
Baffled.

Steven L Umbach wrote:
> Normally ipsec polices do not cause such a problem though if
configured to
> "require" ipsec network services can come to a crawl if other network

> connections can not negotiate the ipsec security. Look in Event
Viewer to
> see any pertinent errors are recorded. If you have some sort of
corruption
> with the ipsec service you can try to uninstall and reinstall tcp/ip
as
> shown in the link below. --- Steve
>
> http://support.microsoft.com/?id=285034
>
> "rockfox212" <rockfox212@netscape.net> wrote in message
> news:1107461785.885258.75110@f14g2000cwb.googlegroups.com...
> > Hi all
> > I tried turning on the IPsec policy agent on my win2k machine in
> > preparation for getting a VPN setup working, but the machine
> > immediately slowed to a crawl. The mouse pointer moves 10 seconds
> > after the mouse is moved, applications take 2-3 minutes to start,
etc.
> > This happened after I tried following the detailed instructions
on
> > the microsoft web page (more fool me?) for VPN. I recovered by
booting
> > in safe mode and turning of the IPsec policy agent and getting rid
of
> > the new policies. Then I found a similar set of instructions in
the
> > back of the manual for a Linksys router, and I followed them very
> > carefully to make sure it wasn't an error the first time around.
As
> > soon as I turn on IPsec policy agent, boom, the machine is dead and
I'm
> > going to have to boot again in safe mode. Any thoughts as to what
> > could be going on? Any ideas appreciated.
> > -C
> >

Relevant Pages

  • IPSec Services will NOT Start
    ... Found the following Error by checking Event Viewer; "The IPSEC Services ... Then checked IPSec, RPC, and TCP/IP Netbios Helper in Services. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Connection Keeps Dropping
    ... > This is what I get from the Event Viewer: ... > IPSec Services: IPSec Services failed to get the complete list of ... > network interfaces on the machine. ...
    (microsoft.public.windowsxp.customize)
  • Re: event viewer
    ... Your logs are too large, ... Using Event Viewer, set your logs to ... Set your overwrite policy to ... > desired by the applied IPSec filters. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: ipsec policy agent brings machine to its knees
    ... manually start the ipsec service. ... Event viewer said "IPSEC driver service ... start the IPsec policy agent first (no ...
    (microsoft.public.win2000.security)
  • Re: XP looses connectivity after IPSEC policy change
    ... IPSEC is tha only thing in event viewer at the time of the instance. ... But what is so stange is we have identical systems runnings Win2K ... > are having network interface issues, ...
    (microsoft.public.windowsxp.security_admin)
Loading