up vote -2 down vote favorite
share [g+] share [fb]

I have two servers that I have been able to connect fine as s1.website.com and s2.website.com

I connected to s1.website.com earlier today without any issues, however, when I connected to s2.website.com it gave me the "Server Unexpectedly Closed Network Connection"

I have researched this elsewhere and someone concluded it to a "brute force attempt" However, I know this is not the case.

If anyone else has had this issue please let me know. Thanks

link|improve this question
38% accept rate
1  
Is this before or after you enter your credentials? – Scott Lundberg Jul 6 '10 at 14:25
1  
Output from the SSH logs on s2.website.com might be useful, too. – RainyRat Jul 6 '10 at 15:29
feedback

1 Answer

up vote -1 down vote

@Scott: Before credentials are entered.
@RainyRat: Not sure what you mean, does every website have a s2 subdomain that shows SSH logs O_o?

Restarted SSH and everything was good.

link|improve this answer
s2.website.com is the machine you were SSHing into, right? – Bill Weiss Jul 14 '10 at 15:14
Not sure why someone down-voted this, I guess "restarting" your service isn't exactly a fix... but it worked. @Bill, no I was not SSH'ing into s2.website.com, just website.com – Austin Jul 14 '10 at 18:40
Well, I took that from you saying 'I connected to s1.website.com earlier today without any issues, however, when I connected to s2.website.com it gave me the "Server Unexpectedly Closed Network Connection"' The downvote is probably from the combination of a question without enough data to provide a useful answer, and the edit of "oh, I restarted and it went away" – Bill Weiss Jul 15 '10 at 14:35
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.