Post a reply

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: Remote side sent disconnect message type 2 (too many connections): "Too many connections"

@Guest: The error comes from the server. So there must be a server-side limit.
Guest

Re: Remote side sent disconnect message type 2 (too many connections): "Too many connections"

Martin wrote:

What is the SSH/SFTP server?

SFTP server hosted in GoAnywhere solution.

How is it configured to limit the connections?

I hope there is no limited. If you think there is limited then let me know configuration.

What kind of diagnostics does it provide for the problem/tracking connections?

No idea.

Why do you think it is a WinSCP (client) problem?

You pls confirm this.
martin

Re: Remote side sent disconnect message type 2 (too many connections): "Too many connections"

@SP: What is the SSH/SFTP server? How is it configured to limit the connections? What kind of diagnostics does it provide for the problem/tracking connections? Why do you think it is a WinSCP (client) problem?
SP

Remote side sent disconnect message type 2 (too many connections): "Too many connections"

Hi,
The SFTP user frequently getting this error(Remote side sent disconnect message type 2 (too many connections): "Too many connections") while, the SFTP user try to login the SFTP server.
I have validated the user account status, which was enabled.And connection from user system to SFTP server also enabled.

But why the user sometime getting this error, What is the reason behind this error and how it'll resolved.

Please update all in properly.
Guest

Thanks again – I set up a test account on our server and emailed the user, host and pass to your email address listed on your personal web page.
martin

May I have a test account on your server?
ljtjr

I tried it with FileZilla, Core FTP and Windows command line – none of them had the problem. I am hoping to use WinSCP you guys have a great program. The XML logging is an excellent feature (among others) that is one of the only ways I have seen to get standardized dir/ls output.
martin

Ok. Do you have the problem with other FTP clients?
ljtjr

No actually I realize I misspoke in a previous post – after further testing it happens with both the GUI and the command line app. The log is from the GUI.
martin

I've understood that when login on/off using GUI, the problem does not occur. Am I wrong?
ljtjr

The following log was created (Debug Level 2 to txt file) by logging on and off the server through the GUI until the time out occurred on the last attempt. Thanks!
martin

Can you post a log file showing script execution, where connection is not terminated correctly on the server; and another log file fron GUI, where connection is terminated correctly?
ljtjr

Thank you for the replay and sorry for the delay. I tried this with 4.2.7 and 4.2.8 using the portable exe and the command line tool. Both versions cause the same problem. I confirmed in task manager that no WinSCP related application or process is running (as far as I could tell) after I terminate each session.
martin

What version are you using? Can you try 4.2.7?
ljtjr

Too Many Simultaneous Connections Error

Hello,

I have a "Too many simultaneous connections error" when using a
batch file. The batch file is:
open ftp://" & strUser & ":" & strPass & "@" & strHost

ls " & Chr(34) & strRemoteDir & Chr(34)
close
exit

Winscp.com is executed from shell within VB with XML logging enabled. When I run this script the first 8 times against a register.com FTP site it seems to work fine. On the 9th try the script is unable to retrieve the ls listing. When I try to log in to that site manually via winscp.exe after the script stops working I get a "too many simultaneous connections" error, which also occurs with other FTP clients. The script will start working again in 15 minutes or so (presumably when sessions which should have been closed by the script are not actually closed, and timeout at the server). I have tried logging in to the FTP site manually 9 times at once, and get the same error, but as soon as the number of simultaneous connections are reduced to less than 8, additional sessions can be opened immediately. This script is only called once at a time. It is almost as if the close then exit commands are not actually terminating the session with the server. Any help would be much appreciated!