SSH Connection Refused

[mlarkin]

Anyone else have issues with SSH?

I originally had it working with OpenSTLinux. Came back the next day and can only get SSH Connection Refused.

I have now tried the Debian image also and it too does the same thing.

I am using Windows 10 and have tried with Putty/Powershell/WSL2; none of them work.

I can confirm that the device appears in Network connections as Remote NDIS device. I haven’t worked with NDIS before, but I can ping 192.168.7.1 regardless if the device is plugged in or not, not sure if that is expected.

[Erik Welsh]

First, you should check your network configuration settings to ensure that the adapter is configured correctly.  In Windows 10, if you go to “Settings” –> “Network & Internet” and select “Change adapter options“, this will pop up a new window with all of the adapters.  In your Network Adapters window, if you right click on the adapter for the board and select “Properties“.  In the center window of the “Properties” pop up, select “Internet Protocol Version 4 (TCP/IPv4)” and click “Properties“.  Generally, you should be able to use “Obtain an IP address automatically“, but sometimes windows will not provide an IP address on the proper subnet, so you can always select “Use the following IP address:” and enter “192.168.7.2” for the IP address and “255.255.255.0” for the Subnet mask.  Once you have made the updates, select “OK” and then “Close” to make sure the settings are applied to the system.

If that does not fix the problem, one other thing you should check is the “known_hosts” file in the the “.ssh/” directory (this may be a hidden directory usually found in the “C:/Users/<username>/” directory so make sure you can see hidden items which is a checkbox in the “View” menu of the File Explorer window).  The “known_hosts” file contains the key fingerprints used to authenticate the SSH connection and if something changes, this can get out of sync at which point SSH will refuse to connect to the host.  If you open up the “known_hosts” file with a text editor and delete the line for “192.168.7.1“, this will force SSH to prompt you to accept the new key fingerprint and you should be able to connect.

Please let us know if you have any additional questions.

 

 

[Author]

Posts