IPsec received a packet from a remote computer with an incorrect Security Parameter Index (SPI). This is usually caused by ...

Windows Server 2008

IPsec received a packet from a remote computer with an incorrect Security Parameter Index (SPI). This is usually caused by malfunctioning hardware that is corrupting packets. If these errors persist, verify that the packets sent from the remote computer are the same as those received by this computer. This error may also indicate interoperability problems with other IPsec implementations. In that case, if connectivity is not impeded, then these events can be ignored.

Remote Network Address:	%1
Inbound SA SPI:		%2

IPSec main mode security association established. User mode is not configured. Keying module type: %1 Local address: %2 Remote ... IPSec main mode security association establishment failed. Keying module type: %1 Local address: %2 Remote address: %3 Local ... IPSec main mode security association establishment failed. Keying module type: %1 Local address: %2 Remote address: %3 Local ... IPSec quick mode security association establishment failed. Keying module type: %1 Local address: %2 Local address mask: ... IPsec received a packet from a remote computer with an incorrect Security Parameter Index (SPI). This is usually caused by ... IPSec received inbound clear text packet that should have been secured: Packet Source: %1 Inbound SA: %2 Number of Packets: ... IPsec Services failed to get the complete list of network interfaces on the computer. This poses a potential security risk ... IPsec Services failed to process some IPsec filters on a plug-and-play event for network interfaces. This poses a potential ... IPsec Services has been shut down successfully. The shutdown of IPsec Services can put the computer at greater risk of network ...