Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: Server unexpectedly closed network connections

Vicky Agarwal wrote:

I am constantly getting an error message of "Server unexpectedly closed network connections" after logging to WinSCP application after 30 sec.

Please start a new thread for your specific problem and attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
Vicky Agarwal

Server unexpectedly closed network connections

Dear Concern,
I am constantly getting an error message of "Server unexpectedly closed network connections" after logging to WinSCP application after 30 sec.

Kindly help in getting this resolved as I am not able to use the application due to constant failure of network connections.

Regards
martin

Re: Connecting from Server results in Connection failed

Softhak wrote:

< 2018-11-13 10:08:04.670 220 Microsoft FTP Service
> 2018-11-13 10:08:04.670 AUTH TLS
< 2018-11-13 10:08:04.670 502 Command not implemented.
> 2018-11-13 10:08:04.670 AUTH SSL
< 2018-11-13 10:08:04.670 502 Command not implemented.


There's no problem on WinSCP side. Your FTP server does not have TLS/SSL enabled.
Softhak

Re: Connecting from Server results in Connection failed

martin wrote:

Please attach a full session log file showing the problem (using the latest version of WinSCP).


I answered this a guest... see post above.

Still no idea what to do
Guest

Re: Connecting from Server results in Connection failed

martin wrote:

Please attach a full session log file showing the problem (using the latest version of WinSCP).


Here is my log. Thanks in advance for the help
martin

Re: Connecting from Server results in Connection failed

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
Softhak

Connecting from Server results in Connection failed

We have a new installation of WINSCP V 5.13.2 (Build 8455)
The complete Installation runs smooth on one machine that is not behind a Firewall.
Configuration is as
Protocol: FTP
Encryption: TLS/SSL Explicit
Port #21
If started behind firewall on a different Server i get the follwing error messages after starting login on the Windows client:

Connection failed.
Command not implemented.

Port 21 is supposed to be open in Firewall. Could there be any other reason for this messages?
And yes I searched already for this error messages and didnt find any hint where to look for next.

Any help appreciated.