Differences
This shows you the differences between the selected revisions of the page.
| 2009-03-20 | 2009-03-20 | ||
| revert vandalism (martin) (hidden) | divide software_caused_connection_abort to subchapters, referece unexpected_close (martin) | ||
| Line 45: | Line 45: | ||
| ===== [[software_caused_connection_abort]] Network error: Software caused connection abort ===== | ===== [[software_caused_connection_abort]] Network error: Software caused connection abort ===== | ||
| - | If you are getting the error while logging in, your connection may have been blocked by firewall. Please refer to [[faq_connection_refused|FAQ]]. | + | ==== 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 [[messages#unexpected_close|"Server unexpectedly closed network connection"]] below apply to this error too. | ||
| - | Even 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. | + | ==== 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. | ||
| 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 54: | Line 58: | ||
| 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)) | ||
| - | |||
| - | The error is also caused by wrong ownership rights for ChrootDirectory in openssh sshd_config file. Changing the ChrootDirectory to anything other then the users home directory causes ownership conflict and hence the error code. | ||
| ===== Host does not exist ===== | ===== Host does not exist ===== | ||