Questions

Catalyst 4500 Series Switch Cisco

+
0 Votes
Locked

Catalyst 4500 Series Switch Cisco

kenneth.w.jones
I have a 4506 Catalyst Switch that I can no longer telnet to. It comes back with the statement:

"Could not open connection to the host, on port 23: Connet failed"

The line vty has a password, login, and transport input telnet configured.

It worked previously, not sure what has happened. Any suggestions?

Tks in advance for any help.

Ken
  • +
    0 Votes
    Fregeus

    ..but I have to ask, can you still ping the switch?

    If not, then you need physical access to the switch, a laptop and a console cable.

    If you can ping the device, can you telnet to other switches from your location (other switches or servers)? If yes, then you need physical access to the switch, something has changed in its configuration and you need to investigate.

    If not, then there is probably something wrong with your set up or your telnet application.


    TCB

    +
    0 Votes
    kenneth.w.jones

    I can ping the switch from another switch but when I try to telnet from the same switch I get "%connection refused by remote host"

    I have several switches inside a Pixs firewall that I manage and I can connect to everyone but this one.

    There has to be something in the configuration that is preventing the connection - I just don/t know what....

    Tks for reply

    +
    0 Votes
    John.Schupp

    You will need to access the console of the switch with a laptop and a console cable. Then you can check the log to see if there are any errors in the switch, and you can double check the configuration to see if any changes have been made recently.

    +
    0 Votes
    Fregeus

    You'll have to go to the switch and log on to the console. Check the vty config. Make sure you have sessions configured. Check the sessions too to be sure you don't have some hanging. I am assuming that its not a firewall configuration, but it all else fails, I would double check that too.


    TCB

    +
    0 Votes
    kenneth.w.jones

    Tks for the replies.

    I had verified the vty line configurations and all looked correct.

    Powered off switch and restarted. Whatever change that was applied was not saved to the startup-config. (Good or bad - good in this case). When switch came back up - telnet was available again.

    Still not sure what the problem was - but now have a backup file of running-config in case this happens again. Also will configure user logon accounts and track what changes are made by who.

    Tks again for all replies.

    Ken

  • +
    0 Votes
    Fregeus

    ..but I have to ask, can you still ping the switch?

    If not, then you need physical access to the switch, a laptop and a console cable.

    If you can ping the device, can you telnet to other switches from your location (other switches or servers)? If yes, then you need physical access to the switch, something has changed in its configuration and you need to investigate.

    If not, then there is probably something wrong with your set up or your telnet application.


    TCB

    +
    0 Votes
    kenneth.w.jones

    I can ping the switch from another switch but when I try to telnet from the same switch I get "%connection refused by remote host"

    I have several switches inside a Pixs firewall that I manage and I can connect to everyone but this one.

    There has to be something in the configuration that is preventing the connection - I just don/t know what....

    Tks for reply

    +
    0 Votes
    John.Schupp

    You will need to access the console of the switch with a laptop and a console cable. Then you can check the log to see if there are any errors in the switch, and you can double check the configuration to see if any changes have been made recently.

    +
    0 Votes
    Fregeus

    You'll have to go to the switch and log on to the console. Check the vty config. Make sure you have sessions configured. Check the sessions too to be sure you don't have some hanging. I am assuming that its not a firewall configuration, but it all else fails, I would double check that too.


    TCB

    +
    0 Votes
    kenneth.w.jones

    Tks for the replies.

    I had verified the vty line configurations and all looked correct.

    Powered off switch and restarted. Whatever change that was applied was not saved to the startup-config. (Good or bad - good in this case). When switch came back up - telnet was available again.

    Still not sure what the problem was - but now have a backup file of running-config in case this happens again. Also will configure user logon accounts and track what changes are made by who.

    Tks again for all replies.

    Ken