IPSEC Policy Agent Error

  • Thread starter Thread starter Jim
  • Start date Start date
J

Jim

When trying to start the IPSEC Policy Agent Service,
The following error is displayed.
"Could not start the IPSEC Policy Agent service on Local
Computer. The service did not return an error. This could
be an internal Windows error or an internal service error.
If the problems persists, contact your system
administrator."
OK, I'm the sysadmin and have no clue where to start!
Running W2K Pro SP4. Have found numerous configuration
tips; however, unable to find troubleshooting tips.
Please lead me in the right direction.
Thanks
 
I would look in Event Viewer for any pertinent clues and then run netdiag on
that machine looking for any failed tests that may help pinpoint the
problem. Also be sure I have read where other people with similar problems
have had luck uninstalling and then renistalling tcp/ip. Another time I
read that this may be caused by corrupt ipsec policies. You could try
deleting all your policies of which there are three by default, backing up
any custon policy first of course and then restoring the default policies by
selecting all tasks/restore default policies. I would reboot before
restoring policies though. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;zh-tw;285034
 
-----Original Message-----
I would look in Event Viewer for any pertinent clues and then run netdiag on
that machine looking for any failed tests that may help pinpoint the
problem. Also be sure I have read where other people with similar problems
have had luck uninstalling and then renistalling tcp/ip. Another time I
read that this may be caused by corrupt ipsec policies. You could try
deleting all your policies of which there are three by default, backing up
any custon policy first of course and then restoring the default policies by
selecting all tasks/restore default policies. I would reboot before
restoring policies though. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;zh- tw;285034




.
Uninstalling and renistalling TCPIP fixed the problem.
Click to expand...
Thank you Steven!
 
Thanks for posting back Jim. Apparently that seems like it should be the
first thing to try. -- Steve
 
Back
Top