I'll let Bill continue with his help, but here's just some things for you to
think about, they should help you with this and subsequent routing issues...
Firstly you appear to be giving much too much weight to the use of RIP. If
you are coming from a Netware IPX environment the use of RIP is much
different in TCP/IP. End-stations do not (normally) get involved in RIP
usage unlike in IPX--where servers send out RIP advertisements (including
for their "Internal" network) and are generally actings as routers too, and
where clients sent out RIP queries... If there is only one router in your
IP network, then RIP accomplishes nothing.
When you say "can ping all subnets" does that mean that you can ping a
(separate) machine on that subnet or does it mean that you can ping the
router's address on that subnet? Why can the results of these tests be
different?? Always think about the individual outgoing packets and the
individual returning packets, and think of the paths that they take and the
hops they cross.
When you say "from subnet(1)", do you mean a separate machine on subnet 1 or
the router--which /is/ attached to subnet 1??
Again, when you say "the subnet(1)" does that mean a separate machine on
subnet 1, or the router machine's interface on subnet 1??
I think that if you clarify to yourself what each of the tests is testing
you will see what's not working and thus what needs to be fixed.
Can you think of a way to test each whether you can reach each interface
that the packets need to cross?? How many interfaces are 'crossed'(/used)
between a client on subnet X and a client on subnet Y?? I count four. Can
you check reachability (and reverse reachability) to each using ping??
I have tracert the IPs and it gets to the router but the
router does not do anything and it times out. also, RIP
Your analysis of what the tracert results is likely wrong. Remember that
there are two reasons for the tracert program on your PC to get no response
from the target hop. One is that the outgoing packet never got to the hop,
and second is that the outgoing packet did get to the hop but the hop (or
the network used on the way back) does not manage to deliver the response
packet back to you...
has been enabled on all other routers in different
networks, as tracert shows that the packets are sent to
the right router in the following.
Hmm, do you have other routers...? Then RIP may be doing something, though
likely not to this particular problem...
