Skip navigation
Cisco Learning Home > Certifications > Routing & Switching (CCNA) > Discussions

_Communities

This Question is Answered
9694 Views 7 Replies Latest reply: Aug 27, 2013 2:16 AM by Malcolm RSS

Currently Being Moderated

Cannot telnet | closed by foreign host | GNS3

Jan 28, 2012 1:55 PM

Alaa Ali 36 posts since
Jan 14, 2012

Hello.

So I'm studying for my ICND2 exam.

  • I downloaded GNS3
  • Topology of R2 connected to SW1 (this is of course a router using the etherswitch interface, the NM-16ESW)
  • Configuration is done on both devices
  • Pinging is successful from R2 to SW1 and vice versa
  • BUT, I cannot telnet from one to the other. I get:
    • Trying 192.168.1.2 ... Open
    • [Connection to 192.168.1.2 closed by foreign host]
  • SSH does not work either (actually, SSH keeps telling me Authentication failed even if I'm typing the correct password)

 

line vty 0 4 is configured for login, and has a password on both devices

transport input telnet ssh is configured

 

I'm already coming over from Packet Tracer and everything is working smoothly over there, but I've decided to move to a more realistic approach of studying; and here I am, stumbling upon my first tiny rock =D.

 

Also, another tiny question: why is it that I have to enable the interface on SW1 which is connected to R2? I thought that once I enable int vlan 1 and connect anything to any switchport, those switchports are automatically enabled. Or is that just in Packet Tracer?

 

*SW1 and R2 configs are attached

Attachments:
  • Martin 13,067 posts since
    Jan 16, 2009
    Currently Being Moderated
    1. Jan 28, 2012 2:17 PM (in response to Alaa Ali)
    Re: Cannot telnet | closed by foreign host | GNS3

    that is strange;

    your switch is actualy router with switching module, right ?

    where is GNS3's  .net file  ?

  • rtbauer05 218 posts since
    Sep 9, 2010
    Currently Being Moderated
    4. Jan 31, 2012 2:51 PM (in response to Alaa Ali)
    Re: Cannot telnet | closed by foreign host | GNS3

    Hey Alaa,

     

    When you configure an IDLE PC value for a specific router it is attached to that IOS image. So if you create an IDLE PC value for one 3700 router it will automatically be used by the succesive routers using the same image. No need to configure it multiple times.

  • Martin 13,067 posts since
    Jan 16, 2009
    Currently Being Moderated
    5. Jan 31, 2012 2:53 PM (in response to Alaa Ali)
    Re: Cannot telnet | closed by foreign host | GNS3

    OK, I forgot about this problem, glad you solved it;

     

    do idle pc on 1 running router and just  once with console window open and login, set no exec-timeout so the window never times out; otherwise,  when console window times out, your CPU usage will raise a bit;

     

    at some point, depends on RAM and GNS3 settings, adding next router will create a new dynamips process. then you could do another idle pc but this is not necessary

    or small improvment (unless your pc is old)

     

    see gns tips https://learningnetwork.cisco.com/thread/23445

  • Malcolm 3 posts since
    Jun 28, 2012
    Currently Being Moderated
    7. Aug 27, 2013 2:16 AM (in response to Alaa Ali)
    Re: Cannot telnet | closed by foreign host | GNS3

    I'm getting the same error although I have set exec-timeout to 30 minutes.

    Pfa attached conf of both the routers.

    Attachments:

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)