Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
gboyce wrote: > On Thu, 16 Feb 2006, Bill Horne wrote: > >> I'm getting an error when attempting to access my home server with ssh: >> >> "Server unexpectedly closed network connection" >> >> I'm working through the Google results, but in the meantime I've got >> a customer waiting and I'm on vacation and I would really like to >> solve this problem quickly, so if anyone has a solution please reply. > > > I've seen this happen on servers that have suffered a hardware failure > on occasion. An inline IPS configured to block SSH connections could > also cause this sort of behavior. > > For the first case, there's not too much you can do. For the second > case, if you can find a different source of Internet access you may > have better luck. > > Someone else may have an alternate cause as well though. I've tried using both WiFi and dialup connections, and got the same results either way. I know the iptables rules are good, since I'm getting an error from the ssh daemon, and I put an allow statement into /etc/hosts.allow. Thanks for the suggestion! Bill -- E. William Horne William Warren Consulting Computer and Network Installation and Service 781 784-7287 (Voice) 781 784-0951 (Fax) 339 440-0724 (Cell)
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |