multiconn. should be hold instead of dropped after transfer

Advertisement

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.

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
27,253
Location:
Prague, Czechia

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

WinSCP does that. Can you post a log file showing your problem?
_________________
Martin Prikryl

Reply with quote

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 ;-)

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
27,253
Location:
Prague, Czechia

OK, thanks for the suggestion.
_________________
Martin Prikryl

Reply with quote

Advertisement

You can post new topics in this forum