Export (0) Print
Expand All

Troubleshooting RIP for IP

Updated: January 21, 2005

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Troubleshooting RIP for IP

What problem are you having?

There are improper routes in a mixed RIP v1 and RIP v2 environment.

Cause:  RIP v2 routers are configured to multicast announcements. Multicast announcements are never received by RIP v1 routers.

Solution:  On networks containing RIP v1 routers, verify that RIP v2 is configured to broadcast its announcements on networks that contain RIP v1 routers and verify that the RIP v2 router interfaces are configured to accept both RIP v1 and RIP v2 announcements.

See also:  Configure RIP version 2

Silent RIP hosts are not receiving routes.

Cause:  RIP v2 routers are configured to multicast announcements. Multicast announcements are never received by silent RIP hosts.

Solution:  If there are silent RIP hosts on a network that are not receiving routes from the local RIP router, verify the version of RIP supported by the silent RIP hosts. For example, if the silent RIP hosts only support listening for broadcasted, RIP v1 announcements, you cannot use RIP v2 multicasting.

If you are using the RIP listener component, available on Microsoft Windows NT Workstation version 4.0, Service Pack 4, or the Windows 2000 RIP Listening Service, you must configure your RIP routers for RIP v1 or RIP v2 broadcasting.

See also:  Configure RIP version 2

RIP routers are not receiving expected routes.

Cause:  You are deploying variable length subnetting, disjointed subnets, or supernetting in a RIP v1 or mixed RIP v1 and RIP v2 environment.

Solution:  Do not deploy variable length subnetting, disjointed subnets, or supernetting in a RIP v1 or mixed RIP v1 and RIP v2 environment.

See also:  "Unicast IP Routing" at the Microsoft Windows Resource Kits Web site.

Cause:  Your password is not matched for all the RIP v2 interfaces on a network segment.

Solution:  If authentication is enabled, verify that all interfaces on the same network are using the same case-sensitive password.

See also:  Enable authentication

Cause:  RIP peer filtering is not configured correctly.

Solution:  If RIP peer filtering is being used, verify that the correct IP addresses for the neighboring peer RIP routers are configured.

See also:  Add peer filters

Cause:  RIP route filtering is not configured correctly.

Solution:  If RIP route filtering is being used, verify that the ranges of network IDs for your internetwork are included or are not being excluded.

See also:  Add route filters

Cause:  RIP neighbors are not configured correctly.

Solution:  If RIP neighbors are configured, verify that the correct IP addresses are configured for the unicasted RIP announcements.

See also:  Add a unicast neighbor

Cause:  IP packet filtering is preventing the receiving (through input filters) or sending (through output filters) of RIP traffic.

Solution:  Verify that IP packet filtering on the router interfaces is not preventing the receiving (through input filters) or sending (through output filters) of RIP traffic. RIP traffic uses User Datagram Protocol (UDP) port 520.

See also:  Manage Packet Filters

Cause:  TCP/IP filtering is preventing the receiving of RIP traffic.

Solution:  Verify that TCP/IP filtering on the router interfaces is not preventing the receiving of RIP traffic. RIP traffic uses UDP port 520.

See also:  Configure TCP/IP to use TCP/IP filtering

Cause:  You are using auto-static RIP and you did not do an initial manual update.

Solution:  When you use auto-static RIP on a demand-dial interface, the first time you make a connection, you must manually update routes.

You must also update routes manually on the router for the corresponding interface. The routes then appear in the IP routing table.

See also:  Perform Auto-Static Updates; View routing tables

Auto-static RIP updates are not working.

Cause:  The demand-dial interfaces are configured to broadcast announcements.

Solution:  For dial-up demand-dial interfaces that use auto-static updates, configure the demand-dial interfaces to use RIP v2 multicast as the outgoing packet protocol. When a router calls another router, each router receives an IP address from the IP address pool of the other router, which is on a different subnet. Because broadcasted RIP messages are addressed to the subnet broadcast address, each router does not process the other router's broadcasted request for routes. Using multicasting, RIP requests and announcements are processed regardless of the subnet for the router interfaces.

See also:  Configure RIP version 2

Host or default routes are not being propagated.

Cause:  RIP by default is not configured to propagate host or default routes.

Solution:  If host routes or default routes need to be propagated, change the default settings on the Advanced tab of the properties of a RIP interface.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft