PrashantGP
Posts: 6
Joined: Sun Jan 07, 2018 7:03 pm

Network error: Software caused connection abort - PuTTY Fatal Error

Sun Jan 07, 2018 7:07 pm

I have performed the steps mentioned in the below URL,
https://www.raspberrypi.org/documentati ... /README.md

also followed the steps mentioned in the below URL,
https://www.raspberrypi.org/documentati ... -config.md

I have downloaded Putty from the link mentioned below,
https://www.raspberrypi.org/documentati ... windows.md

and ensured I am reffering to the correct IP address.
I am connected through ethernet cable, I have installed the latest RASPBIAN STRETCH LITE version.
I have updated and upgraded to the latest version.

I am still facing the error when I try to connect to the PI from my laptop which is connected to the same router throgh wifi,
---------------------------
PuTTY Fatal Error
---------------------------
Network error: Software caused connection abort
---------------------------
OK
---------------------------
Same issue is also faced by the some other user as mentioned in the below URL,
https://imgur.com/a/t78wl

I did try to google quite a lot but I couldn't find any solution can you please assist.

User avatar
neilgl
Posts: 959
Joined: Sun Jan 26, 2014 8:36 pm
Location: Near Aston Martin factory

Re: Network error: Software caused connection abort - PuTTY Fatal Error

Mon Jan 08, 2018 10:42 pm

OK your laptop is connected to the router via wifi and the pi is connected via ethernet cable
Have you copied a file named "ssh" to the raspbian stretch lite microSD card when you did the install?

What is the ip address of your pi e.g.192.168.1.144
and what router are you using?
is that router blocking port 22?

PrashantGP
Posts: 6
Joined: Sun Jan 07, 2018 7:03 pm

Re: Network error: Software caused connection abort - PuTTY Fatal Error

Tue Jan 09, 2018 4:40 am

Thanks Neil.

My laptop is connected via WIFI and my PI is connected via Ethernet cable, I had copied the ssh file in the boot folder. After the boot this file had been removed by the OS (I think it’s does this cleaning activity).
I have enabled SSH through rasp-config.
My IP range is 192.168.0.10 - 192.168.0.254
I am using a Technicolor route TC7000
It is possible that the router could block port 22; how do I check that? I am able to ping the PI from my laptop.

User avatar
bertlea
Posts: 296
Joined: Wed Dec 07, 2016 6:33 am
Location: Hong Kong

Re: Network error: Software caused connection abort - PuTTY Fatal Error

Tue Jan 09, 2018 8:05 am

So did you tried to ping the Pi from the desktop? If ping failed from Desktop to Pi, did you tried to ping the router from Desktop? If ping to router is successful but failed to ping Pi then it seems the router is not blocking this. Some wifi router got "guest" account settings. user connected to the router using guest account can only access external network but other internal systems connected to that router. You can check if your desktop accidentally using guest account to login the wifi router.

PrashantGP
Posts: 6
Joined: Sun Jan 07, 2018 7:03 pm

Re: Network error: Software caused connection abort - PuTTY Fatal Error

Tue Jan 09, 2018 9:10 am

bertlea wrote:
Tue Jan 09, 2018 8:05 am
So did you tried to ping the Pi from the desktop? If ping failed from Desktop to Pi, did you tried to ping the router from Desktop? If ping to router is successful but failed to ping Pi then it seems the router is not blocking this. Some wifi router got "guest" account settings. user connected to the router using guest account can only access external network but other internal systems connected to that router. You can check if your desktop accidentally using guest account to login the wifi router.
Yes I pinged IP of the PI from my laptop and it was successful. I am able to view all the active connections from my laptop without any issues.
How can I check if my desktop is accidentally using the guest account to connect to the route?

pcmanbob
Posts: 6939
Joined: Fri May 31, 2013 9:28 pm
Location: Mansfield UK

Re: Network error: Software caused connection abort - PuTTY Fatal Error

Tue Jan 09, 2018 10:44 am

You need to log in to your router and look at the wifi setup pages if you have a guest network it will normally have a different name to the main network, you will also be able to see if it has wifi isolation activated , will say something like let users see the rest of my network, which will be un-ticked. some routers do this on the main network as well.
I have not see a domestic router that blocks port 22 on the local LAN so you should not have any problems with port 22 being blocked.
We want information… information… information........................no information no help
The use of crystal balls & mind reading are not supported

PrashantGP
Posts: 6
Joined: Sun Jan 07, 2018 7:03 pm

Re: Network error: Software caused connection abort - PuTTY Fatal Error

Tue Jan 09, 2018 12:29 pm

pcmanbob wrote:
Tue Jan 09, 2018 10:44 am
You need to log in to your router and look at the wifi setup pages if you have a guest network it will normally have a different name to the main network, you will also be able to see if it has wifi isolation activated , will say something like let users see the rest of my network, which will be un-ticked. some routers do this on the main network as well.
I have not see a domestic router that blocks port 22 on the local LAN so you should not have any problems with port 22 being blocked.
I dont think there is a guest network stuff on my router I will double check since you have pointed it out. I will wait for 2-3 days if I dont get any solution, I will try to redo everything from scratch(format the SD card and install a fresh downloaded rasbian stretch).
I will also try to connect through VNC in the mean time(haven't tried that yet).

Lets see how it goes will post my finding on this forum.I am hopeful that I might get some solution :) which would lead me to the fix.

User avatar
bertlea
Posts: 296
Joined: Wed Dec 07, 2016 6:33 am
Location: Hong Kong

Re: Network error: Software caused connection abort - PuTTY Fatal Error

Wed Jan 10, 2018 2:08 am

If the ping from PC to Pi is fine, then it should not be the "guest" account issue. Also, as pacmanbob said, it is unlikely a home router blocks port 22 for internal device access. If possible, you can try some more simple tests before you re-install everything.

1. If you able to connect the Pi to the router via LAN, do have able to ssh it? If yes, then it must be the router settings prevent ssh via wifi...... You can also try another router if you have a different router.
2. Did your PC (Windows) got any firewall settings prevent port 22 access to external device?
3. If you have alternative place that can setup a simple network to test ssh, such as a school, office or a friend's home, you can try to bring the Pi there and try ssh from other environment. If success, then you can be certain the issue is not at the Pi at least.

PrashantGP
Posts: 6
Joined: Sun Jan 07, 2018 7:03 pm

Re: Network error: Software caused connection abort - PuTTY Fatal Error

Wed Jan 10, 2018 4:30 am

bertlea wrote:
Wed Jan 10, 2018 2:08 am
If the ping from PC to Pi is fine, then it should not be the "guest" account issue. Also, as pacmanbob said, it is unlikely a home router blocks port 22 for internal device access. If possible, you can try some more simple tests before you re-install everything.

1. If you able to connect the Pi to the router via LAN, do have able to ssh it? If yes, then it must be the router settings prevent ssh via wifi...... You can also try another router if you have a different router.
2. Did your PC (Windows) got any firewall settings prevent port 22 access to external device?
3. If you have alternative place that can setup a simple network to test ssh, such as a school, office or a friend's home, you can try to bring the Pi there and try ssh from other environment. If success, then you can be certain the issue is not at the Pi at least.
Thanks
1. I dont have a different router but I will check it on my friends network.
2. I will also try with other laptop just to confirm its not the Windows firewall that is causing the issue.
3. Will try this out as mentioned in point 1.
Will post my findings by this weekend.

User avatar
bertlea
Posts: 296
Joined: Wed Dec 07, 2016 6:33 am
Location: Hong Kong

Re: Network error: Software caused connection abort - PuTTY Fatal Error

Wed Jan 10, 2018 6:12 am

Actually for test 1, you may not need another router, all you need is a LAN cable to connect that to your Pi, instead of using wifi. This is just try to isolate the cause of issue if it is only affecting wifi. Good luck on your weekend testing!

PrashantGP
Posts: 6
Joined: Sun Jan 07, 2018 7:03 pm

Re: Network error: Software caused connection abort - PuTTY Fatal Error

Wed Jan 10, 2018 6:52 am

bertlea wrote:
Wed Jan 10, 2018 6:12 am
Actually for test 1, you may not need another router, all you need is a LAN cable to connect that to your Pi, instead of using wifi. This is just try to isolate the cause of issue if it is only affecting wifi. Good luck on your weekend testing!
Ok got you point will try that out.

User avatar
bonzadog
Posts: 236
Joined: Wed Apr 25, 2012 9:40 am
Location: Rietberg/Germany

Re: Network error: Software caused connection abort - PuTTY Fatal Error

Mon Jul 02, 2018 9:17 pm

I have this problem too.

WH: RPi 3 B+ (lastest HW)
Stretch version 06-2018
Pi IP : 192.168.178.85
ping from pc works 2ms
VNC Works no problem
putty and winscp I get the error "Software caused connection abort."

On an RPI 2B with stretch 6-2018 VNV, putty and winscp works which I took to mean that there is now firewall blocking.

It started a lof on winscp - and it looks as though ssh was found and is ok. The password is the same for the VCN
Can any one advise me on this.
Many thanks


SCP Log:
2018-07-02 23:02:36.630 --------------------------------------------------------------------------
. 2018-07-02 23:02:36.630 WinSCP Version 5.13.3 (Build 8565) (OS 10.0.17134 - Windows 10 Enterprise)
. 2018-07-02 23:02:36.630 Configuration: HKCU\Software\Martin Prikryl\WinSCP 2\
. 2018-07-02 23:02:36.630 Log level: Normal
. 2018-07-02 23:02:36.630 Local account: PC1\ntrew
. 2018-07-02 23:02:36.630 Working directory: C:\Program Files (x86)\WinSCP
. 2018-07-02 23:02:36.630 Process ID: 1600
. 2018-07-02 23:02:36.630 Command-line: "C:\Program Files (x86)\WinSCP\WinSCP.exe"
. 2018-07-02 23:02:36.630 Time zone: Current: GMT+2, Standard: GMT+1 (W. Europe Standard Time), DST: GMT+2 (W. Europe Summer Time), DST Start: 25.03.2018, DST End: 28.10.2018
. 2018-07-02 23:02:36.630 Login time: Montag, 2. Juli 2018 23:02:36
. 2018-07-02 23:02:36.630 --------------------------------------------------------------------------
. 2018-07-02 23:02:36.630 Session name: [email protected] (Site)
. 2018-07-02 23:02:36.630 Host name: pib3p (Port: 22)
. 2018-07-02 23:02:36.630 User name: pi (Password: Yes, Key file: No, Passphrase: No)
. 2018-07-02 23:02:36.630 Tunnel: No
. 2018-07-02 23:02:36.630 Transfer Protocol: SFTP (SCP)
. 2018-07-02 23:02:36.630 Ping type: Off, Ping interval: 30 sec; Timeout: 15 sec
. 2018-07-02 23:02:36.630 Disable Nagle: No
. 2018-07-02 23:02:36.630 Proxy: None
. 2018-07-02 23:02:36.630 Send buffer: 262144
. 2018-07-02 23:02:36.630 SSH protocol version: 2; Compression: No
. 2018-07-02 23:02:36.630 Bypass authentication: No
. 2018-07-02 23:02:36.630 Try agent: Yes; Agent forwarding: No; TIS/CryptoCard: No; KI: Yes; GSSAPI: Yes
. 2018-07-02 23:02:36.630 GSSAPI: Forwarding: No; Libs: gssapi32,sspi,custom; Custom:
. 2018-07-02 23:02:36.630 Ciphers: aes,chacha20,blowfish,3des,WARN,arcfour,des; Ssh2DES: No
. 2018-07-02 23:02:36.630 KEX: ecdh,dh-gex-sha1,dh-group14-sha1,rsa,WARN,dh-group1-sha1
. 2018-07-02 23:02:36.630 SSH Bugs: Auto,Auto,Auto,Auto,Auto,Auto,Auto,Auto,Auto,Auto,Auto,Auto,Auto
. 2018-07-02 23:02:36.630 Simple channel: Yes
. 2018-07-02 23:02:36.630 Return code variable: Autodetect; Lookup user groups: Auto
. 2018-07-02 23:02:36.630 Shell: default
. 2018-07-02 23:02:36.630 EOL: LF, UTF: Auto
. 2018-07-02 23:02:36.630 Clear aliases: Yes, Unset nat.vars: Yes, Resolve symlinks: Yes; Follow directory symlinks: No
. 2018-07-02 23:02:36.630 LS: ls -la, Ign LS warn: Yes, Scp1 Comp: No
. 2018-07-02 23:02:36.630 SFTP Bugs: Auto,Auto
. 2018-07-02 23:02:36.630 SFTP Server: default
. 2018-07-02 23:02:36.630 Local directory: default, Remote directory: home, Update: Yes, Cache: Yes
. 2018-07-02 23:02:36.630 Cache directory changes: Yes, Permanent: Yes
. 2018-07-02 23:02:36.630 Recycle bin: Delete to: No, Overwritten to: No, Bin path:
. 2018-07-02 23:02:36.630 DST mode: Unix
. 2018-07-02 23:02:36.630 --------------------------------------------------------------------------
. 2018-07-02 23:02:36.693 Looking up host "pib3p" for SSH connection
. 2018-07-02 23:02:36.693 Connecting to 2003:dd:9702:e800:85a3:69df:866:d767 port 22
. 2018-07-02 23:02:36.693 We claim version: SSH-2.0-WinSCP_release_5.13.3
. 2018-07-02 23:02:36.724 Server version: SSH-2.0-OpenSSH_7.4p1 Raspbian-10+deb9u3
. 2018-07-02 23:02:36.724 Using SSH protocol version 2
. 2018-07-02 23:02:36.740 Network error: Software caused connection abort
* 2018-07-02 23:02:36.771 (EFatal) Network error: Software caused connection abort

rickwookie
Posts: 23
Joined: Sat Mar 03, 2012 11:09 am

Re: Network error: Software caused connection abort - PuTTY Fatal Error

Wed Aug 22, 2018 10:48 am

I've had this issue at least twice now. Most recently was certainly a 3B+ using June '18 Stretch Lite.

After messing about for ages, the only thing that fixed it for me on both occasions was simply wiping the microSD card (using the CLEAN command of Windows DISKPART) and re-flashing the Stretch-Lite image. On the second try (after of course also adding the blank 'SSH' file to boot) it just works!

It's very strange, because when it doesn't work, I can clearly ping the device from anything else on my network and also see that port 22 is open on the PI. It's is also not a PuTTY only issue. Any SSH client from any device also fails to connect. It's always an instant fail too/ Weird.

Return to “Beginners”