| Event Id | 30057 |
| Source | Microsoft-Windows-RasRoutingProtocols-IPRIP2 |
| Description | The peer with IP address: %1 was unable to receive RIP message sent out from interface with IP address: %2. The peer may be rebooting, or the Routing and Remote Access service may not be running on the peer. |
| Event Information | According to Microsoft : Resolution : Check RIP configuration To perform this procedure, you must have membership in Administrators , or you must have been delegated the appropriate authority. To configure RIP version 2: 1.Open Routing and Remote Access. Click Start , click Run, type rrasmgmt.msc , and then press ENTER. 2. In the console tree, expand IPv4 , and then click RIP . 3.In the details pane, right-click the interface you want to configure, and then click Properties . 4. Check the settings on the General, Security, Neighbors, and Advanced tabs. Check that the router is configured to receive packets from the neighboring router and that authentication settings are correct. Verify : To perform this procedure, you must have membership in Administrators , or you must have been delegated the appropriate authority. To verify that the Routing Table Manager (RTM) route has been added: a) Stop and restart the Routing and Remote Access service. 1. Click Start , click Run , type rrasmgmt.msc , and then press ENTER. 2. Open Routing and Remote Access. 3. In the console tree, click Server Status . 4. In the details pane, right-click a server name, point to All Tasks , and click Restart . b)View the routing table. In the Routing and Remote Access snap-in, expand IPv4 or IPv6, right-click Static Routes, and then click Show IP Routing Table. c)Verify that the route has been added. |
| Reference Links | Event ID 3057 from Source Microsoft-Windows-RasRoutingProtocols-IPRIP2 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.