| Event Id | 319 |
| Source | PolicyAgent |
| Description | IPSEC PolicyAgent Service couldnt be started: Oakley failed to start |
| Event Information | "This information from some newsgroups may help you: ------------------------------------------------------------------------------ I had this error, and managed to fix it. After reinstallation of the windows 2000 high encryption pack I was able to start the ipsec policy agent again. I think this error was caused after installing a random number generator on my machine (egads). Reinstallation of the tcp/ip protocol under windows 2000 fixed this problem. ------------------------------------------------------------------------------ Cause 1: The IPSec Policy Agent service isnt started. Solution: Start the IPSec Policy Agent service. Cause 2: The IPSec Policy Agent service cant be started. It fails with event ID 319 (as described above). Solution : If PGPNet is installed on the machine this could be the source of the problem. Try removing PGPNet. I guess that PGPNet makes some changes to the IPSec Service on the machine. This is valid for other programs, like VPN clients. ------------------------------------------------------------------------------ I installed PGP 7.03 for Windows on my Win2k Pro (with IPSEC) machine and I received events 319 and 321. My solution was to uninstall the TCP/IP protocols, reboot, reinstall TCP/IP, and reinstall Win2k SP4. After this, the problem did not appear anymore. ------------------------------------------------------------------------------ Failed to obtain Kerberos server credentials for ISAKMP/Oakley service. Kerberos authentication will not function. The most likely reason for this is lack of domain membership. This is normal if your computer is a member of a workgroup. ------------------------------------------------------------------------------ " |
| Reference Links |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.