Event ID - 30033

Event Id30033
SourceMicrosoft-Windows-RasRoutingProtocols-IPRIP2
DescriptionIPRIPv2 is ignoring a route to: %1 with next-hop: %2 which was advertised by a neighbor with IP address: %3, because the interface on which the route was received has a filter configured which excluded this route.
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 Routing Information Protocol version 2 (RIPv2):
  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.


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:
  • 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 .
  • In the details pane, right-click a server name, point to All Tasks , and click Restart .
  • 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 .
  • Verify that the route has been added.
Reference LinksEvent ID 30033 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.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.