Differences

This shows you the differences between the selected revisions of the page.

2010-07-10 2010-09-16
[[ssh#verifying_the_host_key|verifying host keys]]. (122.166.173.120) timeout_external_console (martin)
Line 7: Line 7:
===== [[host_key]] The server's host key was not found in the cache ===== ===== [[host_key]] The server's host key was not found in the cache =====
This error message occurs when WinSCP connects to a new [[SSH]] server. Every server identifies itself by means of a host key; once WinSCP knows the host key for a server, it will be able to detect if a malicious attacker redirects your connection to another machine. This error message occurs when WinSCP connects to a new [[SSH]] server. Every server identifies itself by means of a host key; once WinSCP knows the host key for a server, it will be able to detect if a malicious attacker redirects your connection to another machine.
 +
Line 32: Line 33:
  * You may need to connect through proxy server, but you have not specified one on [[ui_login_proxy|login dialog]].   * You may need to connect through proxy server, but you have not specified one on [[ui_login_proxy|login dialog]].
  * Connection was blocked by firewall. Please refer to [[faq_connection_refused|FAQ]].   * Connection was blocked by firewall. Please refer to [[faq_connection_refused|FAQ]].
- 
- 
- 
- 
- 
- 
Line 222: Line 217:
===== [[empty_listing_for_directory]] Server returned empty listing for directory ===== ===== [[empty_listing_for_directory]] Server returned empty listing for directory =====
Check that you have read and execute permissions to the directory. Check that you have read and execute permissions to the directory.
 +
 +===== [[timeout_external_console]] Timeout waiting for external console to complete the command =====
 +This error indicates that ''[[executables|winscp.exe]]'' did not receieve an answer from ''[[executables|winscp.com]]'' in time.
 +
 +Most commonly this happens when ''winscp.com'' has redirected output to a stream with limited buffer. If the stream is not being read from, the buffer gets eventually filled and ''winscp.com'' hangs, when trying to write into it.
 +
 +In turn the above most commonly happens when ''winscp.com'' is run from another program (such as .Net code), which redirect its output into stream. If the program then e.g. waits for ''winscp.com'' to finish without reading from the stream, the ''winscp.com'' eventually hangs, never finishing.
 +
 +See example of [[guide_dotnet|.Net]] or [[guide_automation_advanced#inout|WSH]] code dealing with the problem.
===== [[error_listing_directory]] Error listing directory ===== ===== [[error_listing_directory]] Error listing directory =====

Last modified: by martin