06-06-2005 03:42 AM
I have an Cisco 1711 router and i want loggin to it by telnet trough an external network ( remote management ) so i configure the line VTY 0 4 if i am in internal i can to connect to it , but i cant from external .
someone can help me please
06-06-2005 04:27 AM
Set up an ACL to allow the remote network telnet access to the router.
access-list 1 permit x.x.x.x y.y.y.y
x= network y= subnet mask
line vty 0 4
access-class 1 in
login
HTH
06-06-2005 05:37 AM
Peter's suggestion of creating an access list and applying it to the vty ports using access-class is a very good suggestion and is the appropriate way to control who has access to the router.
But I do not think that it will help with the original problem. As I understand the posting if you are on a device internal to your network you can successfully telnet to the router but from devices outside your network you can not telnet. I believe that there are several possible explanations for this:
- it may be that external devices do not have a correct route to your router. Perhaps one way to check this is to do a traceroute and see how the data would flow.
- it may be that your router does not have a correct route to the external devices. Perhaps onw way to check this is to do a traceroute and see how the data would flow.
- it may be that there is filtering or a firewall at the edge of your network which does not allow inbound telnet from outside devices.
Check into those and let us know if one of them turns out to be the problem.
HTH
Rick
06-12-2005 11:48 AM
agree with-------->rburts
06-15-2005 05:41 AM
I have the exact same issue with some Cisco SOHO97 routers.
I can ping and traceroute the Dialer IP address, but telnet and HTTPS fails, I understand that telnet may be blocked by the ISP, but expect HTTPS to work, anybody an ideas???
06-15-2005 09:44 AM
If you can ping and traceroute then it would seem that you have proved that it is not an IP connectivity issue. I will suggest to you, as I suggested to the original post, that it would be logical to look for some kind of firewall or access list filtering. This could be at the edge of your network or could be at the edge of the remote network.
It might also be an issue with what is permitted if the remote router has been configured with access-class on its vty ports.
HTH
Rick
06-20-2005 12:49 AM
If you are using PAT you might need to add this:
ip nat inside source static tcp ip_of_your_router 23 interface your_dialer 23
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