PuTTY Fatal Error - Software caused connection abort
up vote
0
down vote
favorite
I'm using Putty 0.70 64bit client on my windows 10 to connect to odroidXU4 running ubuntu 18.04 minimal(XU4-20180531) and openssh-server (>= 1:7.6p1-4ubuntu0.1)
I am able to constantly replicate the PuTTY Fatal Error (Network Error: Software caused connection abort) by two ways:
The first way is by using cat on a 70kb text file with 450 lines. PuTTY will partially display the output, hang for awhile, before showing the error.
The second way is to open up vi/vim/nano on a 9kb config file with 263 lines and hold the pageDownKey/RightArrowKey for some seconds. In this case, PuTTY also hangs before showing the error.
However, the disconnect can be avoided when i use less instead of cat. Similarly, it can also be avoided by pressing the pageDownKey/RightArrowKey slowly, one key at a time.
My guess is that there could be a problem in the bufferring, transmission or display, where a larger amount of input/output than usual being send/received in small bursts might be causing the software error.
Does anybody face the similar issue?
Are there any configurations or workarounds that can potentially solve this issue?
Update 1:
I used the windows built in ssh client to no avail.
Openssh-server 1:6.7pl-5 on an OMV3 image (debian jessie) doesn't have this issue. Will try to install an older version of openssh-server.
putty openssh
asked Nov 16 at 4:57
akgren_soar
11
add a comment |
up vote
0
down vote
favorite
I'm using Putty 0.70 64bit client on my windows 10 to connect to odroidXU4 running ubuntu 18.04 minimal(XU4-20180531) and openssh-server (>= 1:7.6p1-4ubuntu0.1)
I am able to constantly replicate the PuTTY Fatal Error (Network Error: Software caused connection abort) by two ways:
The first way is by using cat on a 70kb text file with 450 lines. PuTTY will partially display the output, hang for awhile, before showing the error.
The second way is to open up vi/vim/nano on a 9kb config file with 263 lines and hold the pageDownKey/RightArrowKey for some seconds. In this case, PuTTY also hangs before showing the error.
However, the disconnect can be avoided when i use less instead of cat. Similarly, it can also be avoided by pressing the pageDownKey/RightArrowKey slowly, one key at a time.
My guess is that there could be a problem in the bufferring, transmission or display, where a larger amount of input/output than usual being send/received in small bursts might be causing the software error.
Does anybody face the similar issue?
Are there any configurations or workarounds that can potentially solve this issue?
Update 1:
I used the windows built in ssh client to no avail.
Openssh-server 1:6.7pl-5 on an OMV3 image (debian jessie) doesn't have this issue. Will try to install an older version of openssh-server.
putty openssh
asked Nov 16 at 4:57
akgren_soar
11
It could be a problem with the MTU along the way.
– RalfFriedl
Nov 16 at 7:39
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm using Putty 0.70 64bit client on my windows 10 to connect to odroidXU4 running ubuntu 18.04 minimal(XU4-20180531) and openssh-server (>= 1:7.6p1-4ubuntu0.1)
I am able to constantly replicate the PuTTY Fatal Error (Network Error: Software caused connection abort) by two ways:
The first way is by using cat on a 70kb text file with 450 lines. PuTTY will partially display the output, hang for awhile, before showing the error.
The second way is to open up vi/vim/nano on a 9kb config file with 263 lines and hold the pageDownKey/RightArrowKey for some seconds. In this case, PuTTY also hangs before showing the error.
However, the disconnect can be avoided when i use less instead of cat. Similarly, it can also be avoided by pressing the pageDownKey/RightArrowKey slowly, one key at a time.
My guess is that there could be a problem in the bufferring, transmission or display, where a larger amount of input/output than usual being send/received in small bursts might be causing the software error.
Does anybody face the similar issue?
Are there any configurations or workarounds that can potentially solve this issue?
Update 1:
I used the windows built in ssh client to no avail.
Openssh-server 1:6.7pl-5 on an OMV3 image (debian jessie) doesn't have this issue. Will try to install an older version of openssh-server.
putty openssh
asked Nov 16 at 4:57
akgren_soar
11
I'm using Putty 0.70 64bit client on my windows 10 to connect to odroidXU4 running ubuntu 18.04 minimal(XU4-20180531) and openssh-server (>= 1:7.6p1-4ubuntu0.1)
I am able to constantly replicate the PuTTY Fatal Error (Network Error: Software caused connection abort) by two ways:
The first way is by using cat on a 70kb text file with 450 lines. PuTTY will partially display the output, hang for awhile, before showing the error.
The second way is to open up vi/vim/nano on a 9kb config file with 263 lines and hold the pageDownKey/RightArrowKey for some seconds. In this case, PuTTY also hangs before showing the error.
However, the disconnect can be avoided when i use less instead of cat. Similarly, it can also be avoided by pressing the pageDownKey/RightArrowKey slowly, one key at a time.
My guess is that there could be a problem in the bufferring, transmission or display, where a larger amount of input/output than usual being send/received in small bursts might be causing the software error.
Does anybody face the similar issue?
Are there any configurations or workarounds that can potentially solve this issue?
Update 1:
I used the windows built in ssh client to no avail.
Openssh-server 1:6.7pl-5 on an OMV3 image (debian jessie) doesn't have this issue. Will try to install an older version of openssh-server.
putty openssh
putty openssh
asked Nov 16 at 4:57
akgren_soar
11
asked Nov 16 at 4:57
akgren_soar
11
edited Nov 16 at 8:29
asked Nov 16 at 4:57
akgren_soar
11
asked Nov 16 at 4:57
akgren_soar
11
asked Nov 16 at 4:57
akgren_soar
11
11
It could be a problem with the MTU along the way.
– RalfFriedl
Nov 16 at 7:39
add a comment |
It could be a problem with the MTU along the way.
– RalfFriedl
Nov 16 at 7:39
It could be a problem with the MTU along the way.
– RalfFriedl
Nov 16 at 7:39
It could be a problem with the MTU along the way.
– RalfFriedl
Nov 16 at 7:39
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1375883%2fputty-fatal-error-software-caused-connection-abort%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It could be a problem with the MTU along the way.
– RalfFriedl
Nov 16 at 7:39