Received a packet over a security association with a low sequence number. IPsec inbound packet replay check failed. This may indicate a either network or hardware problem or that a replay attack is in process. Check your IPsec peer network for errors. To check for a replay attack shutdown the peer device and check if these messages persist. If the messages persist it may indicate a replay attack.: Packet Source: %1 Inbound SA: %2 Number of Packets: %3
Real-Time Protection agent has taken action to protect this machine from spyware or other potentially unwanted software. ...
Real-Time Protection checkpoint has encountered an error and failed to start. User:%b%8\%9 Checkpoint ID:%b%3 Error Code:%b%4 ...
Realm trust If the server is not a Windows Active Directory Domain Controller, you can create a trust to an interoperable ...
Receive-Side Scaling State : %1!s! Chimney Offload State : %2!s! Receive Window Auto-Tuning Level : %3!s! Add-On Congestion ...
Received a packet over a security association with a low sequence number. IPsec inbound packet replay check failed. This ...
received. From: %2. CallerId: %3. To: %4. Pages: %5. Transmission time: %6. Device Name: %7. Please check the activity log ...
Receives activation requests over the net.msmq and msmq.formatname protocols and passes them to the Windows Process Activation ...
Receives trap messages generated by local or remote Simple Network Management Protocol (SNMP) agents and forwards the messages ...
Recommended only for disks with a backup power supply. This setting further improves disk performance, but it also increases ...