Sudden Putty Connection Issue

[Martinski]

Please read the notes from the author:
from https://github.com/github/putty/blob/master/doc/plink.but

From the same GitHub link you provided:

\H{plink-usage} Using Plink

This section describes the basics of how to use Plink for
interactive logins and for automated processes.

Then the author proceeds to describe how to use Plink for interactive logins.

\S{plink-usage-interactive} Using Plink for interactive logins

To make a simple interactive connection to a remote server, just
type \c{plink} and then the host name:

The point is that the CLI tool *is* designed and can be used for both interactive and automated logins, and there’s absolutely clear evidence for this.

Yes you could run it as a console environment once you set it up.

The official PuTTY installer will do the initial setup automatically.

But you have to set up the connection profile or invoke it on the command line.

Well, it’s a command-line tool. It even says so in the very first line of the link you posted.

I'm just glad I don't have to use toy programs like this for SSH anymore since I primarily use Linux.

It doesn’t change the fact that the first 2 sentences in your post #45 are still wrong.

 

[Digilog]

It doesn’t change the fact that the first 2 sentences in your post #45 are still wrong.

Does it matter? Obviously to you.... I don't come here to argue about something that is a moot point. Nor try to prove anything to anyone. but apparently you have to make it a drama thread for some dumb reason.

 

[Martinski]

Does it matter? Obviously to you....

It matters when you provide technical information or advice that is verifiably & clearly incorrect. This is primarily a technical forum so you should expect to be corrected when you post the wrong technical info so we can avoid spreading misinformation. That you don’t like to be corrected is a separate personal issue that has nothing to do with the technical aspects of this thread.

I don't come here to argue about something that is a moot point. Nor try to prove anything to anyone. but apparently you have to make it a drama thread for some dumb reason.

Ah yes, of course, the classic signs of deflection, avoidance & internal denial that happen when someone is confronted with compelling evidence that goes against what they believe to be true, but they still refuse to consider that they might be wrong, unwilling to reflect on new information, and being completely unable to challenge their own views or opinions, let alone admit that they are mistaken, no matter how trivial or important the subject matter may be.

And no, I’m not going to continue to engage in a "war of words" with someone who seems unable to adapt, learn & change their mind when presented with clear evidence that they hold views or opinions that are inarguably false.

 

[Digilog]

Makes a big fuss about a program designed for scripts (Plink), that is a clumsy command interface (when used manually) and that there are several programs that are much better at it.

 

[bbunge]

I sense a stay on topic warning coming.....

 

[djtech2k]

Well I guess this thread died on the vine lol.

 

[bennor]

Well I guess this thread died on the vine lol.

It is ultimately a problem with that one specific PC as indicated by your prior comment: "The connection to my AC68U is the only putty connection that fails and its only from this laptop." Others have shown examples of the latest Putty working for them when connecting to a RT-AC68U. Try looking at the laptop itself. Check the OS. Check any security programs that are running on the laptop. Try booting the laptop into Safe Mode with Network to see if Putty exhibits the same issue. Completly remove the entire Putty and it's associated programs, download the portable version of Putty and run it from a different location than the previously installed version of Putty to see if the issue persists. When removing Putty make sure to remove all its files to ensure it doesn't carry over any settings to the new downloaded version of Putty.

Other things to try. If using Windows, reset Putty to default by running the following putty.exe -cleanup from the command prompt. In Windows use the Registry Editor to delete any saved sessions in the following Registry Key: Computer\HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions
And you probably may need to also remove any SSH Host Keys for those sessions: Computer\HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys

 

[djtech2k]

It is ultimately a problem with that one specific PC as indicated by your prior comment: "The connection to my AC68U is the only putty connection that fails and its only from this laptop." Others have shown examples of the latest Putty working for them when connecting to a RT-AC68U. Try looking at the laptop itself. Check the OS. Check any security programs that are running on the laptop. Try booting the laptop into Safe Mode with Network to see if Putty exhibits the same issue. Completly remove the entire Putty and it's associated programs, download the portable version of Putty and run it from a different location than the previously installed version of Putty to see if the issue persists. When removing Putty make sure to remove all its files to ensure it doesn't carry over any settings to the new downloaded version of Putty.

Other things to try. If using Windows, reset Putty to default by running the following putty.exe -cleanup from the command prompt. In Windows use the Registry Editor to delete any saved sessions in the following Registry Key: Computer\HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions
And you probably may need to also remove any SSH Host Keys for those sessions: Computer\HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys

It turns out the issue is with putty v0.82 connecting to my Asus, which is running an older version of dropbear. I do not know what in putty is causing it to fail but v0.81 works fine from everywhere and v0.82 fails from everywhere.

 

[bennor]

It turns out the issue is with putty v0.82 connecting to my Asus, which is running an older version of dropbear. I do not know what in putty is causing it to fail but v0.81 works fine from everywhere and v0.82 fails from everywhere.

Contact the developer of Putty if you haven't done so already to see what they say. Otherwise you are likely stuck with the previous version of Putty if you don't (for what ever reason) want to update the two year old 384.19 (14-Aug-2020) firmware on your RT-AC68U to the latest 386.14_2 (17-Nov-2024) firmware.

I would still clean out any Putty install (including from the registry) and try again as a troubleshooting step just to rule out a corrupted install or setting being an issue.

 

[djtech2k]

Contact the developer of Putty if you haven't done so already to see what they say. Otherwise you are likely stuck with the previous version of Putty if you don't (for what ever reason) want to update the two year old 384.19 (14-Aug-2020) firmware on your RT-AC68U to the latest 386.14_2 (17-Nov-2024) firmware.

I would still clean out any Putty install (including from the registry) and try again as a troubleshooting step just to rule out a corrupted install or setting being an issue.

Agreed and I did that. I sent a message to the bug submit process but never heard back.

I uninstalled and removed all of the registry entries but no change. Its exactly the same on 2 different laptops in terms of the behavior and the versions.

Its not a major issue for me now because once my pfsense box is ready, I will be replacing the Asus with it. I was just curious why it happened and it was interesting to look into at the very least.