Re: Feeling a bit dumb today, need help with routing problem. -> dumbness solved!

2001-04-03 Thread fartcatcher
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.") w

Re: Feeling a bit dumb today, need help with routing problem.

2001-04-03 Thread Erick B.
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 EIG

Re: Feeling a bit dumb today, need help with routing problem.

2001-04-03 Thread Rik
Fartcatcher (great name!), the previous 2 posts have good info in them, so check that stuff out. If everything is kosher (no offense to those members of the Jewish faith!), then you might check that the router is setup to for classless addressing. I can't remember if that version of IOS has "ip

RE: Feeling a bit dumb today, need help with routing problem.

2001-04-03 Thread Daniel Cotts
Sometimes it's best to question the hosts. Do they have the correct default gateway for their subnet? Can they ping their local interface? Can they ping the other interface? > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 03, 2001 10:42 AM

Re: Feeling a bit dumb today, need help with routing problem.

2001-04-03 Thread John Neiberger
If both of those networks are directly attached, your choice of routing protocol is irrelevant. I would check the usual: host configurations, IP addresses, subnet masks, etc. If this isn't a production router, turn on debugging and see if that gives you any clues. debug ip packet will show you