09-21-2007 11:56 AM - edited 03-03-2019 06:52 PM
I have connected 2 cisco routers with back to back DCE/DTE cable. I have configured both serial interfaces with 192.168.2.x range. Also on one router I have configured the ethernet interface to 10.0.0.200 and have a host with ip 10.0.0.4 connected to it. Rip is configured on both routers but from the other router I can only ping 10.0.0.200 but not the host! what is the reason?
09-21-2007 12:09 PM
Andrea
The first things that I would check to investigate this problem is whether the host has the right default gateway configured. If the host is attempting to respond to 192.168.2.x then it needs to have its default gateway be 10.0.0.200.
HTH
Rick
09-21-2007 12:17 PM
yes the host gateway is set to 10.0.0.200
In fact I do not know if it helps but from the router which has the ethernet 10.0.0.200 directly connected and not learned through rip I can ping the host even when connected with telnet on serial interface with 192.168.2.x
09-21-2007 01:21 PM
Are you sure RIP is working?
Are there routes to the 10.0.0.0 network in the remote side router?
Is it RIP version 1?
Could it be a discontiguous netwok issue?
09-22-2007 07:52 AM
remote side router
R 10.0.0.0/8 [120/1] via 192.168.2.250, 00:00:06, Serial0
C 192.168.2.0/24 is directly connected, Serial0
local router
C 10.0.0.0/8 is directly connected, Ethernet0
C 192.168.2.0/24 is directly connected, Serial0
using rip v1, host 10.0.0.4 connected with local router ethernet port and ping ok from local router.
from remote router can ping 10.0.0.200 ethernet interface of local router but cannot ping host
09-22-2007 08:53 AM
It sounds like you have FW enabled in the host that only allows ICMP from devices within the same subnet.
Even telneting to the local router on its serial interface, will produce an ICMP packet sourcing from the ethernet interface.
You can alter this behavior by using this command.
ping 10.0.0.4 source [serial ip]
on the local router and see if the host respond to the ICMP.
If this is WindowsXP, most often Windows FW is enabled. Check for that ...
09-23-2007 11:11 AM
Thank You I think this could be the reason. Unfortunately that command gave me an error when I tried from local router;
r2#ping 10.0.0.4 source 192.168.2.250
^
% Invalid input detected at '^' marker.
Tried to disable Windows firewall however it did not fix the problem.
09-24-2007 05:22 PM
Perhaps you have an old IOS.
Try with extended ping... Example,
ping [enter]
and follow the prompts, when you get to the source address, enter it there.
09-24-2007 07:23 PM
When using the extended ping command (ping [enter]), in order to specify a source address or interface you need to hit y when asked about extended commands.
hth
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide