Differences
This shows you the differences between the selected revisions of the page.
| 2009-12-04 | 2009-12-08 | ||
| old revision restored (martin) | noted DHCP related cause of Software caused connection abort (24.22.208.184) | ||
| Line 5: | Line 5: | ||
| ===== [[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 54: | Line 55: | ||
| ==== In a Middle of Session ==== | ==== 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, or if Windows has any other similar reason to believe the entire network has become unreachable. | + | 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]]. | 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]]. | ||
| Line 61: | Line 62: | ||
| 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)) | ||
| + | |||
| + | 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 ===== | ===== [[host_does_not_exist]] Host does not exist ===== | ||