Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 615 Source: Security
|Type: Failure Audit|
IPSec Services: IPSec Services failed to get the complete list of network interfaces on the machine. This can be a potential security hazard to the machine since some of the network interfaces may not get the protection as desired by the applied IPSec filters. Please run IPSec monitor snap-in to further diagnose the problem.
|English: This information is only available to subscribers. An example of English, please!|
According to T733278, yes, you can use the IP Security Monitor to see which network adapters are not protected, but you cannot resolve the problem by using that program. See the article for the full details about how to proceed further (what to verify).
In one case this event appeared only once on Windows 2003 SP1. It was on a computer that had been restored from an image of another computer from another domain and was not connected to the network. The event can be ignored in this case.
From a newsgroup post: "I found MS article ME912023, which helped me solve the problem. Though I didn't even have the registry key that the article refers to, I skipped the first steps and ran the reload process. It reloaded the missing keys and ipsec was back up and running".
See ME816514 for information on how to configure IPSec tunneling in Windows Server 2003.
From a newsgroup post: "We haven't seen very often, but have seen it happen in laptops when PNP network interfaces are added and removed. Devices that can PNP may not be loaded before IPsec initializes".
See MSW2KDB for additional information regarding this event.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated