Just to be sure I understand:
- After you restart the machine, your application that uses WinSCP .NET assembly is not able to retrieve directory listing (although it can connect to the FTP server).
- You then connect to the same FTP server using Windows command-line
- The command retrieves the directory listing.
- From that moment on, the application that uses WinSCP .NET assembly is able to retrieve the directory listing too.
Is that correct?
And again, while the application that uses WinSCP .NET assembly is failing, if you connect using any other FTP client that uses passive FTP mode, is the client able to retrieve directory listing or not? Note that
- After you restart the machine, your application that uses WinSCP .NET assembly is not able to retrieve directory listing (although it can connect to the FTP server).
- You then connect to the same FTP server using Windows command-line
ftp.exe
client and issue dir
command.
- The command retrieves the directory listing.
- From that moment on, the application that uses WinSCP .NET assembly is able to retrieve the directory listing too.
Is that correct?
And again, while the application that uses WinSCP .NET assembly is failing, if you connect using any other FTP client that uses passive FTP mode, is the client able to retrieve directory listing or not? Note that
ftp.exe
uses an active mode.