- Nov 20, 2009
- 8,410
- 1,617
- 136
Morning All,
I use WinSCP as the company (or center) designated FTP program to use for file transfer. When I got my last lease roll laptop back late last Spring the version that got installed was WinSCP 5.9.5. Previously, I had been using a much older version, but I cannot uninstall and install again any other version.
The problem is that this version has a feature enabled that remembers the exact remote path location for the last session for a given profile. I have tons of profiles for a variety of network elements and servers and would be a beast having to rebuild them all under any reinstall scenario.
My problem is that I logged into a server and accidentally double-clicked back on directory level, which took forever to present on the remote panel of the app. Now when I try to re-establish a new FTP session on this profile it tried to access that last directory level and reading that directory level exceeds the timeout of the application.
I thought I knew where in the app to get it to stop remembering the exact last path location for the profile, but it doesn't seem to be working. Every time I try to launch a session on this profile it tried to read the directory contents and exceeds the maximum allow time of 300 seconds and aborts, retries, aborts, retries.
Conversely I can use SSH applications like SecureCRT just fine for access this specific server, and I can access other elements and servers using WinSCP. Anyone know how to clear the app's cache to it no longer remembers the last path location for the given profile?
I use WinSCP as the company (or center) designated FTP program to use for file transfer. When I got my last lease roll laptop back late last Spring the version that got installed was WinSCP 5.9.5. Previously, I had been using a much older version, but I cannot uninstall and install again any other version.
The problem is that this version has a feature enabled that remembers the exact remote path location for the last session for a given profile. I have tons of profiles for a variety of network elements and servers and would be a beast having to rebuild them all under any reinstall scenario.
My problem is that I logged into a server and accidentally double-clicked back on directory level, which took forever to present on the remote panel of the app. Now when I try to re-establish a new FTP session on this profile it tried to access that last directory level and reading that directory level exceeds the timeout of the application.
I thought I knew where in the app to get it to stop remembering the exact last path location for the profile, but it doesn't seem to be working. Every time I try to launch a session on this profile it tried to read the directory contents and exceeds the maximum allow time of 300 seconds and aborts, retries, aborts, retries.
Conversely I can use SSH applications like SecureCRT just fine for access this specific server, and I can access other elements and servers using WinSCP. Anyone know how to clear the app's cache to it no longer remembers the last path location for the given profile?
Facebook
Twitter