11-21-2008 10:42 AM - edited 03-04-2019 12:26 AM
Ok,
I posted a couple of days ago about a telnet problem that I had where I could ping the router, but couldn't telnet to it. There are NO acls involved at all.
Well today, I figured out that I can telnet to the router from another router, but not from a host behind the router. It looks like this:
Cannot telnet: host -> router -> router
Can telnet: router -> router
This doesn't make any sense to me at all. Any ideas?
--John
11-24-2008 09:01 AM
You need to format your ACL for the interesting traffic from the source to destination and vice-versa.
To make things simple, try a source w/ the problem that is closest to the destination. Initiate the test and see what the debug displays.
Another suggestion will be, if you have a lab, try dumping the configuration from the routers into the lab and see if you can duplicate it there.
__
Edison.
11-24-2008 09:10 AM
I'll have to test it out in a lab. I want to see what I'll have to look for, and I HOPE I can recreate this in a lab. :-)
I'll let you know tomorrow what the results were!
Thank you!
11-25-2008 07:19 AM
Okay, I set up the lab exactly as it is here, and I couldn't duplicate the problem. I give up, and I'm just going to telnet from the box that I know can get to it. It's just a really weird situation that I can ping from both directions, but not telnet. Odd.
--John
11-25-2008 07:45 AM
Usually, when I see issues with no reasoning behind it, a reboot usually fixes it :)
Give it a shot.
__
Edison.
11-21-2008 12:13 PM
i fully agree with edison for checking the route in the target router to host network belongs and check for the default gateway of the host.
Ullas
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