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

Guest

btw winscp is very good! thanks
martin

OK, thanks for the suggestion.
Guest

The company firewall Admin told me that.
But i checked it as you mentioned it, WinSCP keeps the connection open. :-)
Maybe the maximum transfer limit should be setable per server.
e.g. 1-2 for the limited company and 3 for all others.

Because running 1x PuTTY and up to 3 WinSCP Sessions will lock me out ;-)
martin

Re: multiconn. should be hold instead of dropped after transfer

WinSCP does that. Can you post a log file showing your problem?
Guest

multiconn. should be hold instead of dropped after transfer

in fact of restrictive firewalls in front of ssh servers, the winscp client should not close the transfer session after a transfer.

instead it should keep the management session (for browsing) and the transfer sessions 1-n open after transfering files.

example: the firewall blocks an ip after 3 new ssh connections per minute.