Question

PuTTY gives "Network error: Software caused connection abort" and closes....why?

I want to use PuTTY with username and password instead of ssh keys.

I edited /etc/ssh/sshd_config and uncommented '#PasswordAuthentication yes ’

Then I restarted ssh with ‘service ssh restart’

But, when I try and use PuTTY to log into server PuTTY does not connect and gives the “Network error: Software caused connection abort” message.

What am I screwing up?

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

If you are continually encountering this issue I would recommend attempting to log into the console in the control panel. If you have a password and shell set for your user you will be able to log in there as it does not depend on your ssh service. I would then recommend checking /var/log/auth.log and the other log files in /var/log for your ssh login attempts and you should find more information on why they failed.

I had this problem, the problem was the router. Configure Putty to send “Keepalives”. This solution works for me: i had used keep alive time. with this solution https://www.hostingride.in/content/solved-network-error-software-caused-connection-abort-winscp-error-putty-keepalives

but last i used url or official winscp website and it;s worked for me https://winscp.net/eng/docs/message_software_caused_connection_abort

This may even happen if there is IP conflict in the network. Try to turn of the network service in the machine by manually loggingin to that eaither via console or direct keyboard then stop the network service.

Now after that try to ping the same IP there may be some loss but still if ping works then for sure it is having IP conflict