SSH Protocol Error: expected packet type 61, got 50 FIXED
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2025 12:18 PM - edited 05-06-2025 12:19 PM
Hello,
I have been migrating some company switches from RADIUS to TACACS+ authentication and authorization, and ran into the above error a few times. I could not find, quite literally, any information on this specific error but, I have now found the cause of the "expected packet type 61, got 50" error so I thought I would share how to fix it since it is unbelievably simple.
I use SecureCRT as my main SSH client for all of our switches, and while migrating the switches to TACACS+ authentication, I would sometimes get the error written in the title. Off of a pure guess, I wondered if my saved username had anything to do with this as the current switch I was working on had a saved username, and the one before did as well.
As soon as I deleted the username from the properties of the switch session stored in the left, I can successfully log in with every account included in the TACACS+ authorization profile.
Hopefully this works for some of you
- Labels:
-
Network Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2025 02:46 PM
Thanks for sharing your experience with this issue. Glad that you were able to find the solution to your own problem.
Rick
