That's what I'm having a problem with. RtrB can ping the PC & RtrA can ping
the RtrB e0 interface, but won't ping the PC. It was mentioned to make the
default gateway on the PC the RtrB e0 address.
I'll try that & see what happens... thanx to all your help.
That was exactly the answer I needed. B
Can router B ping the PC? From what you've said, (that there isn't a route
there) I doubt it. Until B can ping it, A won't be able to...
HTH
:-{)]
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=21025&t=20759
--
FAQ, list archive
Hey Paul, I'm not getting any communication between s0(192.1.1.3) & e0
(192.168.1.10) on RtrB using an extended ping with e0 as the destination and
s0 as the source. I entered "ip route 192.168.1.0 255.255.255.0 e0" and it
doesn't show up in the route table.
I entered "ip route 0.0.0.0 0.0.0.0 e0
You would need to configure a static route from RtrA towards
the ethernet segment of RtrB.
Something like ip route 192.168.1.0 255.255.255.0 192.168.1.1.3 configured
on RtrA.
What is happening is that RtrA does not know how to route packets to B's
ethernet segment. The only route it knows abou
You dont have to add any static routes as your routers are directly
connected and as you can ping B from A. If your ethernet interface is
configured correctly you would be able to ping the pc if it is set with the
default gateway as the address of etherrnet 0 of Router B
syam
- Original Mess
5 matches
Mail list logo