Differences
This shows you the differences between the selected revisions of the page.
| 2011-12-14 | 2011-12-28 | ||
| old revision restored, hint with password is already on message_unexpected_close (martin) | no summary (220.255.2.149) (hidden) | ||
| Line 11: | Line 11: | ||
| - | If you see this message, it means that WinSCP has not seen this host key before, and has no way of knowing whether it is correct or not. You should attempt to verify the host key by other means, such as asking the machine's administrator. | + | If you see this message, it means that WinSCP has not seen this host key before, and has no way of knowing whether it is correct or not. You should attempt to verify the host key by other eans, such as asking the machine's administrator. |
| If you see this message and you know that your installation of WinSCP has connected to the same server before, it may have been recently upgraded to SSH protocol version 2. SSH protocols 1 and 2 use separate host keys, so when you first use SSH-2 with a server you have only used SSH-1 with before, you will see this message again. You should verify the correctness of the key as before. ((&puttydoccite)) | If you see this message and you know that your installation of WinSCP has connected to the same server before, it may have been recently upgraded to SSH protocol version 2. SSH protocols 1 and 2 use separate host keys, so when you first use SSH-2 with a server you have only used SSH-1 with before, you will see this message again. You should verify the correctness of the key as before. ((&puttydoccite)) | ||
| Line 42: | Line 42: | ||
| * //Français - // Erreur réseau : connexion refusée | * //Français - // Erreur réseau : connexion refusée | ||
| * //Italiano - // Errore di rete: connessione rifiutata | * //Italiano - // Errore di rete: connessione rifiutata | ||
| - | |||
| - | ===== [[connection_refused_ftp]] No connection could be made because the target machine actively refused it ===== | ||
| - | The same as [[message_connection_refused|"Network error: Connection refused"]]. | ||
| - | |||
| - | ===== [[connection_timed_out]] Network error: Connection timed out ===== | ||
| - | All reasons and hints for [[message_connection_refused|"Network error: Connection refused"]] apply to this error too. | ||
| - | |||
| - | ===== [[no_route_to_host]] Network error: No route to host ===== | ||
| - | All reasons and hints for [[message_connection_refused|"Network error: Connection refused"]] apply to this error too. | ||
| - | It may also be worth trying again later as this error can be due to temporary network issue. | ||
| - | |||
| - | ===== [[timeout_detected]] Timeout detected ===== | ||
| - | If you are getting the error while logging in or while initiating file transfer, all reasons and hints for [[message_connection_refused|"Network error: Connection refused"]] apply to this error too. | ||
| - | |||
| - | With [[ftp|FTP protocol]] you can also try to use [[ui_login_connection#connection|passive mode]]. | ||
| - | |||
| - | ===== [[software_caused_connection_abort]] Network error: Software caused connection abort ===== | ||
| - | ==== While Connecting ==== | ||
| - | You may get this message when connecting to a server for following reasons: | ||
| - | * Connection was blocked by firewall. Please refer to [[faq_connection_refused|FAQ]]. | ||
| - | * All reasons and hints for [[message_unexpected_close|"Server unexpectedly closed network connection"]] apply to this error too. | ||
| - | |||
| - | ==== In a Middle of Session ==== | ||
| - | If you are getting the error in the middle of session, it means that Windows network code killed an established connection for some reason. For example, it might happen if you pull the network cable out of the back of an Ethernet-connected computer, a DHCP IP address renewal fails or changes the computer's IP address, or if Windows has any other similar reason to believe the entire network has become unreachable. | ||
| - | |||
| - | Windows also generates this error if it has given up on the machine at the other end of the connection ever responding to it. If the network between your client and server goes down and your client then tries to send some data, Windows will make several attempts to send the data and will then give up and kill the connection. In particular, this can occur even if you didn't do anything, if you are using SSH-2 and WinSCP attempts a [[ui_login_kex#reexchange|key re-exchange]]. | ||
| - | |||
| - | The problem can be caused also by the firewall. Try to disable it temporarily to see if the problem persists. Refer to [[faq_connection_refused|FAQ]]. | ||
| - | |||
| - | 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)) | ||
| - | |||
| - | If you find DHCPNACK errors in the Event Viewer, your DHCP server may be briefly denying your IP address, causing your existing connections to fail. Where possible, this can be addressed by reserving a specific IP address on the DHCP server (e.g. cable modem/router), setting that as the static IP address, and disabling the DHCP client service. | ||
| - | |||
| - | ===== [[host_does_not_exist]] Host does not exist ===== | ||
| - | You may get this message when connecting to a server for following reasons: | ||
| - | * You may have typed a wrong hostname on Login dialog. | ||
| * Your domain name is new and is not fully distributed to DNS servers yet. | * Your domain name is new and is not fully distributed to DNS servers yet. | ||
| * Connection was blocked by firewall. Please refer to [[faq_connection_refused|FAQ]]. | * Connection was blocked by firewall. Please refer to [[faq_connection_refused|FAQ]]. | ||