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
Rebuilding the index might take a long time to complete. Some views and search results might be incomplete until rebuilding ...
Receive Bytes/sec is the rate at which data is being received from the network. This value includes application data as well ...
Receive Indications/sec is the average rate, in incidents per second, at which NDIS received a receive indication call from ...
Receive-Side Scaling State : %1!s! Chimney Offload State : %2!s! NetDMA State : %7!s! Direct Cache Access (DCA) : %8!s! Receive ...
Received a packet over a security association with a low sequence number. IPsec inbound packet replay check failed. This ...
received a timeout error while applying IP settings on adapter '%3'. Check the guest network configuration to verify whether ...
Received bits per second at each interval, logging latest 60 samples at each interval defined in IntervalSeconds (second). ...
received for ChannelId %2 and AppUserModelId %3 with TrackingId %4, X-WNS-MSG-ID %5, timestamp %6 and expiration %7 tag: ...
Received remoting fragment. Object Id: %1 Fragment Id: %2 Start Flag: %3 End Flag: %4 Payload Length: %5 Payload Data: %6 ...