04-22-2020 01:25 AM
hi everyone i am setting up a lab on cisco packet tracer to create an access via ssh. I created both a dns server (from which the encryption keys will be generated via ssh), two PCs and a switch in the center. On the switch I configured the vlan 1 (the only vlan), with ip 192.168.1.5 while the dns server, pc1 and pc 2 respectively 1.2, 1.3 and 1.4.
Pings work properly.
When I go to pc1 from the telnet / ssh icon and try to connect with ssh with ip 192.168.1.5 it always gives me this message:
The current session has closed. Do you want restablish a new session with the previous session options?
However in the ssh configuration I set username and password as per exercise in the initial ssh configuration
What did I do wrong?
Solved! Go to Solution.
04-22-2020 04:28 AM - edited 04-22-2020 04:29 AM
Are you trying to ssh to the switch?
there is no ip address configured on the switch
try this on switch -
int vlan 1 ip add 192.168.1.5 255.255.255.0 no sh exit line vty 0 4 transport input ssh exit
Then use the telnet/ssh client to connect to 192.168.1.5 from the PC.
Hope this helps
04-22-2020 06:06 AM
the packet tracer file you gave had vlan 1 administratively shutdown and no ip address
once you assign an ip address you have to do unshut the interface to make it active
thats why i used no shut
04-22-2020 01:35 AM
Hi
Can you share the packet tracer file?
Thanks
04-22-2020 02:37 AM
04-22-2020 02:44 AM
04-22-2020 03:08 AM
04-22-2020 04:28 AM - edited 04-22-2020 04:29 AM
Are you trying to ssh to the switch?
there is no ip address configured on the switch
try this on switch -
int vlan 1 ip add 192.168.1.5 255.255.255.0 no sh exit line vty 0 4 transport input ssh exit
Then use the telnet/ssh client to connect to 192.168.1.5 from the PC.
Hope this helps
04-22-2020 05:11 AM
04-22-2020 06:06 AM
the packet tracer file you gave had vlan 1 administratively shutdown and no ip address
once you assign an ip address you have to do unshut the interface to make it active
thats why i used no shut
04-22-2020 08:35 AM
04-22-2020 08:46 AM
04-22-2020 05:15 AM
12-20-2025 03:21 PM
Looks like a common Packet Tracer SSH setup issue—usually missing ip domain-name, RSA key generation, or VTY lines not set to login local and transport input ssh. Threads like this are really helpful to troubleshoot labs step by step, just like guides people rely on when getting into a 666w game and want things to work smoothly.
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