Ertaz wrote: » Did you generate the keys?
rob42 wrote: » What does your show ip ssh look like?
rob42 wrote: » Doesn't look right to me. What about your show sshedit to add... I'd go through the SSH configuration process again if I were you. Are you sure of the command sequence? If you let me know which Switch you're using (I'm assuming CPT v7), I'll go through it also if you like and we can compare the results?
rob42 wrote: » It seems to be okay my end... Topology PC [ip 192.168.1.20] fa0 connected to SW1 fa/01 Switch>en Switch#conf t Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#hostname SW1 SW1(config)#int vlan 1 SW1(config-if)#ip address 192.168.1.10 255.255.255.0 SW1(config-if)#no shutdown SW1# SW1#ping 192.168.1.20 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.1.20, timeout is 2 seconds: .!!!! Success rate is 80 percent (4/5), round-trip min/avg/max = 0/0/0 ms SW1# SW1#show ssh %No SSHv2 server connections running. %No SSHv1 server connections running. SW1#show ip ssh SSH Disabled - version 1.99 %Please create RSA keys (of atleast 768 bits size) to enable SSH v2. Authentication timeout: 120 secs; Authentication retries: 3 SW1# C:\>ssh -l admin 192.168.1.10 Open [Connection to 192.168.1.10 closed by foreign host] C:\> SW1#conf t Enter configuration commands, one per line. End with CNTL/Z. SW1(config)#line vty 0 15 SW1(config-line)#login local SW1(config-line)#exit SW1(config)#username admin password cisco SW1(config)#ip domain-name techexams.net SW1(config)#crypto key generate rsa The name for the keys will be: SW1.techexams.net Choose the size of the key modulus in the range of 360 to 2048 for your General Purpose Keys. Choosing a key modulus greater than 512 may take a few minutes. How many bits in the modulus [512]: 1024 % Generating 1024 bit RSA keys, keys will be non-exportable...[OK] SW1(config)#ip ssh version 2 SW1(config)#line vty 0 15 SW1(config-line)#transport input ssh SW1(config-line)#^z SW1# C:\>ssh -l admin 192.168.1.10 Open Password: SW1> If you compare your command sequence with mine, you'll see that you've missed a couple of things, namely, 'login local' and 'username'. Try it again, bud'
... I am still unable to access via SSH. If i change the command to # transport input all in vty line config, I can telnet into the switch , but not SSH. Thanks for helping BTW
rob42 wrote: » No probs and you're very welcome. I can't understand why it's not working for you. The fact that you can use TELNET demonstrates that you've got a valid IP connection (as no doubt you understand), so it has to be an issue with the SSH configuration. If you want to made your CPT file available, I'll gladly have a look at it. Cheers for now.
sub-zero wrote: » Thanks Rob, still confused myself. As soon as I add the #transport input all command in line vty , it allows me to telnet into the switch.