Thanks for the responses everyone. I found out what the problem was. I was
missing a route on the end router (which I had to add later in place of our
firewall). My 'little' network is working fine.
Thanks everyone,
fartcatcher.
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] ("Erick B.") wrote:
>Well, since these are directly connected networks
>EIGRP isn't used. Check the default gateways of the
>PCs you are pinging and make sure it is set to either
>e0 or e1, or they have a route back to the other
>network with e0 or e1 as the next hop.
>
>If there is another router off e0 or e1 speaking EIGRP
>then you should have a EIGRP neighbor adj formed. If
>you don't have a EIGRP adj formed then routes will not
>be exchanged.
>
>--- fartcatcher <[EMAIL PROTECTED]> wrote:
>> Hello everyone, I have a problem and no it's not
>> personal (hah!).I am having
>> trouble getting a router to route between two
>> networks (10.166.x.x /24 and
>> 10.20.30.x /24). I have a cisco 1605 (running 11.2)
>> that has two ethernet
>> interfaces. On eth0 I have the 10.166.x.x network,
>> on the other
>> 10.20.30.x./24. I have eigrp enabled and in the
>> routing table both networks
>> show up, but I can't ping a host on the 10.166.x.x
>> network from the
>> 10.20.30.x.
>>
>> I know this is very simple, but I am a simple man.
>>
>> Thanks,
>> F.
>[EMAIL PROTECTED]
>
>
>__________________________________________________
>Do You Yahoo!?
>Get email at your own domain with Yahoo! Mail.
>http://personal.mail.yahoo.com/
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
