Differences

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

2009-04-24 2009-04-24
~~SPLIT~~ (martin) anchors (martin)
Line 12: Line 12:
Read more about [[ssh#verifying_the_host_key|verifying host keys]]. Read more about [[ssh#verifying_the_host_key|verifying host keys]].
-===== Warning - Potential security breach! =====+===== [[security_breach]] Warning - Potential security breach! =====
This message, followed by "The server's host key does not match the one WinSCP has is cache", means that WinSCP has connected to the SSH server before, knows what its host key should be, but has found a different one. This message, followed by "The server's host key does not match the one WinSCP has is cache", means that WinSCP has connected to the SSH server before, knows what its host key should be, but has found a different one.
Line 31: Line 31:
If you are trying to use WinSCP to connect to your iPhone or iPod Touch, please refer to [[faq_iphone|FAQ]]. If you are trying to use WinSCP to connect to your iPhone or iPod Touch, please refer to [[faq_iphone|FAQ]].
-===== No connection could be made because the target machine actively refused it =====+===== [[connection_refused_ftp]] No connection could be made because the target machine actively refused it =====
The same as [[messages#connection_refused|"Network error: Connection refused"]]. The same as [[messages#connection_refused|"Network error: Connection refused"]].
-===== Network error: Connection timed out =====+===== [[connection_timed_out]] Network error: Connection timed out =====
All reasons and hints for [[messages#connection_refused|"Network error: Connection refused"]] above apply to this error too. All reasons and hints for [[messages#connection_refused|"Network error: Connection refused"]] above apply to this error too.
-===== Network error: No route to host =====+===== [[no_route_to_host]] Network error: No route to host =====
All reasons and hints for [[messages#connection_refused|"Network error: Connection refused"]] above apply to this error too. All reasons and hints for [[messages#connection_refused|"Network error: Connection refused"]] above apply to this error too.
It may also be worth trying again later as this error can be due to temporary network issue. It may also be worth trying again later as this error can be due to temporary network issue.
-===== Timeout detected =====+===== [[timeout_detected]] Timeout detected =====
If you are getting the error while logging in or while initiating file transfer, all reasons and hints for [[messages#connection_refused|"Network error: Connection refused"]] above apply to this error too. If you are getting the error while logging in or while initiating file transfer, all reasons and hints for [[messages#connection_refused|"Network error: Connection refused"]] above apply to this error too.
Line 61: Line 61:
It can also occur if you are using [[ui_login_connection#keepalives|keepalives]] in your connection. Other people have reported that keepalives fix this error for them. ((&puttydoccite)) It can also occur if you are using [[ui_login_connection#keepalives|keepalives]] in your connection. Other people have reported that keepalives fix this error for them. ((&puttydoccite))
-===== Host does not exist =====+===== [[host_does_not_exist]] Host does not exist =====
You may get this message when connecting to a server for following reasons: You may get this message when connecting to a server for following reasons:
  * You may have typed a wrong hostname on Login dialog.   * You may have typed a wrong hostname on Login dialog.
Line 104: Line 104:
All reasons and hints for [[messages#unexpected_close|"Server unexpectedly closed network connection"]] above apply to this error too. All reasons and hints for [[messages#unexpected_close|"Server unexpectedly closed network connection"]] above apply to this error too.
-===== Host is not communicating for more than 15 seconds. Still waiting... Warning: Aborting this operation will close connection! =====+===== [[host_is_not_communicating]] Host is not communicating for more than 15 seconds. Still waiting... Warning: Aborting this operation will close connection! =====
You get this message when WinSCP is waiting for response from the server for more than [[ui_login_connection#server_response_timeout|configured time]]. Note that this is not an error message, WinSCP still keeps waiting. If the server responds finally, the message goes away automatically. The message box is shown only to give you a chance to break the connection and reconnect, if you do not want to wait anymore. You get this message when WinSCP is waiting for response from the server for more than [[ui_login_connection#server_response_timeout|configured time]]. Note that this is not an error message, WinSCP still keeps waiting. If the server responds finally, the message goes away automatically. The message box is shown only to give you a chance to break the connection and reconnect, if you do not want to wait anymore.
Line 120: Line 120:
It may help to check log file of your server to see an actual reason, it denied you an access. It may help to check log file of your server to see an actual reason, it denied you an access.
-===== Server sent disconnect message type 2 (protocol error): "Too many authentication failures for root" =====+===== [[too_many_authentication_failures]] Server sent disconnect message type 2 (protocol error): "Too many authentication failures for root" =====
This message is produced by an OpenSSH (or Sun SSH) server if it receives more failed authentication attempts than it is willing to tolerate. This message is produced by an OpenSSH (or Sun SSH) server if it receives more failed authentication attempts than it is willing to tolerate.
This can easily happen if you are using Pageant and have a large number of keys loaded into it, since these servers count each offer of a public key as an authentication attempt. This can be worked around by specifying the key that's required for the authentication in the [[ui_login_session|session configuration]]; WinSCP will ignore any other keys Pageant may have, but will ask Pageant to do the authentication, so that you don't have to type your passphrase. ((&puttydoccite)) This can easily happen if you are using Pageant and have a large number of keys loaded into it, since these servers count each offer of a public key as an authentication attempt. This can be worked around by specifying the key that's required for the authentication in the [[ui_login_session|session configuration]]; WinSCP will ignore any other keys Pageant may have, but will ask Pageant to do the authentication, so that you don't have to type your passphrase. ((&puttydoccite))
-===== Unable to use this private key file, Couldn't load private key, Key is of wrong type =====+===== [[key_is_of_wrong_type]] Unable to use this private key file, Couldn't load private key, Key is of wrong type =====
If you see one of these messages, it often indicates that you've tried to load a key of an inappropriate type into WinSCP. If you see one of these messages, it often indicates that you've tried to load a key of an inappropriate type into WinSCP.
Line 173: Line 173:
You can also try to run the respective command from terminal (with the same account that you use with WinSCP), to verify that you can execute it. You may not have sufficient permissions, or the command dependencies may not be installed. You can also try to run the respective command from terminal (with the same account that you use with WinSCP), to verify that you can execute it. You may not have sufficient permissions, or the command dependencies may not be installed.
-===== WinSCP was not able to determine application that was started to open the file. WinSCP cannot watch for changes in the file and thus it will not upload the changed file back =====+===== [[not_able_to_determine_application_started]] WinSCP was not able to determine application that was started to open the file. WinSCP cannot watch for changes in the file and thus it will not upload the changed file back =====
See [[task_edit#mdi|documentation]]. See [[task_edit#mdi|documentation]].
Line 180: Line 180:
This error is typically associated with another error. If there is no other error in the message, try searching a [[logging|log file]]. This error is typically associated with another error. If there is no other error in the message, try searching a [[logging|log file]].
-===== 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.
-===== Error listing directory =====+===== [[error_listing_directory]] Error listing directory =====
This is high-level error, and it is typically associated with another error, such as: This is high-level error, and it is typically associated with another error, such as:
  * [[messages#timeout_detected|Timeout detected]];   * [[messages#timeout_detected|Timeout detected]];
  * [[messages#unexpected_directory_listing|Unexpected directory listing line '...']].   * [[messages#unexpected_directory_listing|Unexpected directory listing line '...']].
-===== Invalid access to memory =====+===== [[invalid_access_to_memory]] Invalid access to memory =====
This error message is not useful for you as an end-user. It generally means that there is a bug in the software. Please [[reporting|report the bug]]. This error message is not useful for you as an end-user. It generally means that there is a bug in the software. Please [[reporting|report the bug]].

Last modified: by martin