extremely slow WinSCP when re-connected via RDP
hello, we are experiencing huge issues with WinSCP not responding to opened sessions when we reconnect via RDP (on Windows 10)
how to reproduce:
- open a few winscp sessions via RDP (ssh or ftp, it does not play a role)
- close RDP without unlogging
- re-connect via RDP
- try to browse directories via opened sessions in WinSCP
the main reason why we use RDP on Windows 10 is the store of the opened sessions + text files + browser and else which makes it very comfortable to return to the same work state as RDP was closed.
in recent (in last cca 1 year) of upgrades of WinSCP this bacame a huge problem for us, it just takes a few minutes for WinSCP to get working after RDP reconnect.
we have about 7000 ftp/ssh accounts set up in our WinSCP, using AES encryption with master password. cleaning session cache in WinSCP solves the problem until another few tens of connections is made.
best regards, stan
how to reproduce:
- open a few winscp sessions via RDP (ssh or ftp, it does not play a role)
- close RDP without unlogging
- re-connect via RDP
- try to browse directories via opened sessions in WinSCP
the main reason why we use RDP on Windows 10 is the store of the opened sessions + text files + browser and else which makes it very comfortable to return to the same work state as RDP was closed.
in recent (in last cca 1 year) of upgrades of WinSCP this bacame a huge problem for us, it just takes a few minutes for WinSCP to get working after RDP reconnect.
we have about 7000 ftp/ssh accounts set up in our WinSCP, using AES encryption with master password. cleaning session cache in WinSCP solves the problem until another few tens of connections is made.
best regards, stan