SOLVED SSH Putty - Can't login to new install via Putty SSH
#1
XBMCbuntu 12

Hey guys, I just did a format and fresh install of XBMCbuntu using from the xbmcbuntu-12_xvba-fglrx_legacy.iso that I downloaded. Problem is that I went to start setting some things up by logging into the XBMCbuntu machine via Putty/SSH, which I do all of the time and was working fine before reformatting, and I get this error in Putty

Quote:"Network error: Software caused connection abort"

What the heck? I do have an onboard LAN card which is disabled in BIOS and I am using a PCI Ethernet adapter to connect wired. It is the same setup I had before reformatting and worked just fine. So I have no idea what is going on. I can SSH into my NAS just fine using Putty, but the new install is blocking this for some reason. Any help or suggestions would be greatly appreciated
Reply
#2
To clarify, I can view files on the xbmcbuntu machine from my windows pc. I can also ping my xbmcbuntu machine with response.
Reply
#3
Is sshd running?
Code:
ps -ef | grep sshd
Reply
#4
@pumkinut: It is. I was an idiot. All I had to do was delete the keys on the machines I was using to login with ssh and it solved the problem. Thanks for the suggestion.
Reply
#5
I'm having the same problem as OP, but I'm unable to resolve it so far.

XBMCbuntu 12. I'm able to see the network shares (pictures, music, ...) via Windows 7 client. However I can not SSH via putty. I tried deleting all Putty settings and keys from the registry in Win7. (putty -cleanup). I removed/reinstalled putty. I still get the same "Network error: Software caused connection abort".

Any help appreciated.
Reply
#6
1. Open the registry (regedit)
2. Go to HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys

There you should see Putty’s cache of host keys.
The ‘name’ column tells you which key is for which server.
For example, it will have the format of <something>@<port>:<host> [[email protected]]

3. Delete the rows that you need and profit.

http://www.chiark.greenend.org.uk/~sgtat...aq-cleanup

putty -cleanup is not gonna do it is it? <- not a question.

uNi
Reply
#7
(2013-02-02, 17:12)uNiversal Wrote: HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys

Thanks for the reply. I tried this as well. I deleted everything \SimonTatham and below before uninstalling/reinstalling. I'm still getting the same error.
Reply
#8
http://superuser.com/questions/294824/pu...tion-abort

If that doesn't do it, idk what will.

uNi
Reply
#9
At this point I'm pretty sure it's a SSH key authentication problem. I've tried from 2 different systems. Looking at the logs I see things like:
Failed to read 1st key exchange packet

and on another system

Outgoing packet #0x0, type 20 / 0x14 (SSH2_MSG_KEXINIT)....[then what I suspect is a key]

then: Event Log: Network error: Software caused connection abort


I think I need to tell XBMCbuntu to allow my clients, but I'm unsure how to do so.
Reply
#10
I had the same issue, which was caused by incorrectly generated SSH keys (during first boot). Check this by opening a terminal and going into the /etc/ssh directory. You will see a bunch of files, 6 of them looking like 'ssh_host_###_key'. If these are 0 bytes in size, you are affected by this as well. Follow these steps to fix the issue:

First, remove the old keys:
Code:
rm /etc/ssh/ssh_host_*_key*

Now generate new ones. The command will ask you to set a passphrase or press enter to continue. Do not set a passphrase!
Code:
ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key
Code:
ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key
Code:
ssh-keygen -t ecdsa -f /etc/ssh_host_ecdsa_key

Restart your SSH service (or reboot). You can now log in again.

Code:
service ssh restart
Reply
#11
(2013-03-03, 18:16)bobfw Wrote: I had the same issue, which was caused by incorrectly generated SSH keys (during first boot). Check this by opening a terminal and going into the /etc/ssh directory. You will see a bunch of files, 6 of them looking like 'ssh_host_###_key'. If these are 0 bytes in size, you are affected by this as well. Follow these steps to fix the issue:

First, remove the old keys:
Code:
rm /etc/ssh/ssh_host_*_key*

Now generate new ones. The command will ask you to set a passphrase or press enter to continue. Do not set a passphrase!
Code:
ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key
Code:
ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key
Code:
ssh-keygen -t ecdsa -f /etc/ssh_host_ecdsa_key

Restart your SSH service (or reboot). You can now log in again.

Code:
service ssh restart

Couldn't SSH into my fresh XBMCbuntu installation. This fixed my "connection refused" issues.
Reply
#12
(2013-09-01, 18:49)weimeanz Wrote:
(2013-03-03, 18:16)bobfw Wrote: I had the same issue, which was caused by incorrectly generated SSH keys (during first boot). Check this by opening a terminal and going into the /etc/ssh directory. You will see a bunch of files, 6 of them looking like 'ssh_host_###_key'. If these are 0 bytes in size, you are affected by this as well. Follow these steps to fix the issue:

First, remove the old keys:
Code:
rm /etc/ssh/ssh_host_*_key*

Now generate new ones. The command will ask you to set a passphrase or press enter to continue. Do not set a passphrase!
Code:
ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key
Code:
ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key
Code:
ssh-keygen -t ecdsa -f /etc/ssh_host_ecdsa_key

Restart your SSH service (or reboot). You can now log in again.

Code:
service ssh restart

Couldn't SSH into my fresh XBMCbuntu installation. This fixed my "connection refused" issues.

Thank you for mentioning this; my connection error didn't have the exact same cause as yours but restarting the ssh service did get me on the right track. I needed to reassign permissions to the ssh/ directory to make the server not ignore the keys (which was the problem).
Code:
chmod 600 -R /etc/ssh

After restarting ssh with those permissions in place I had no problem connecting. Big Grin
Reply



Logout Mark Read Team Forum Stats Members Help
SOLVED SSH Putty - Can't login to new install via Putty SSH0
This forum uses Lukasz Tkacz MyBB addons.