Incoming packet was garbled on decryption - WinSCP v 5.1.7

Advertisement

_jre
Joined:
Posts:
4

Incoming packet was garbled on decryption - WinSCP v 5.1.7

Hello,

I'm setting up WinSCP v 5.1.7 for the first time (on Windows Server 2003 R2 SP2).
I've reviewed this website for suggestions on resolving the error "Incoming packet was garbled on decryption".

Turning on the "Ignores SSH-2 maximum packet size" debug option hasn't resolved this error.

I've also moved the "Blowfish" algorythm to the top of the list in the SSH encryption cypher selection policy.

Here are the last 3 lines of the attached log file:

[Tunnel] Incoming packet was garbled on decryption
(EFatal) Incoming packet was garbled on decryption
Authentication failed.

Thanks in advance for any suggestions you may have.

John
Description: Masked Log

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
40,476
Location:
Prague, Czechia

Re: Incoming packet was garbled on decryption - WinSCP v 5.1.7

Thanks for your report.
Any chance of getting a test account on your server?

Reply with quote

_jre
Joined:
Posts:
4

Hello Martin,
Thanks for the reply. The server I'm connecting to belongs to our vendor. I won't be able to provide you with access.

I have made progress with this by tweaking some of my settings. The error message in the subject line no longer applies to my issue. I'm working with the technical contacts at our vendor's office as well as our firewall admin here at our office to see if we can resolve this issue.

Here's an excerpt of some of the log information from my latest attempt to connect.

. 2013-08-30 09:26:56.377 [Tunnel] Host key matches cached key

. 2013-08-30 09:27:05.939 [Tunnel] Access granted

. 2013-08-30 09:27:06.064 Connecting via tunnel interface 127.0.0.1:50000.

. 2013-08-30 09:27:06.174 [Tunnel] Forwarded connection refused by server: Administratively prohibited [open failed]

. 2013-08-30 09:27:06.189 Waiting for the server to continue with the initialization

. 2013-08-30 09:27:06.424 [Tunnel] Closing connection.
. 2013-08-30 09:27:06.424 Server unexpectedly closed network connection

* 2013-08-30 09:27:06.455 (EFatal) Server unexpectedly closed network connection.
* 2013-08-30 09:27:06.455 Error while tunneling the connection.
* 2013-08-30 09:27:06.455
* 2013-08-30 09:27:06.455 Administratively prohibited (open failed).

Reply with quote

_jre
Joined:
Posts:
4

My issue has been resolved -

Turns out that I needed to use IP addresses within my configuration instead of DNS names and I turned off the tunneling feature within WinSCP since this wasn't needed...

John

Reply with quote

Advertisement

You can post new topics in this forum