Dear list This is not directly a security question, but the technologie what I use comes from the security area. So I hope somebody can support me from this list. After a clean shutdown (due maintanence at the 230V system) of the system, it was not possible to connect again via ssh. And of course afew days before was ssh working perfect. I can see in the sniffer files that the tcp 3 way handshake is working fine, but afterwards I get a timeout. No information in any logfiles about ssh failure. I use on a win a putty-client. The ssh daemon is running. I use suse 8.0 with susefirewall2. The system response to port 22 (checked with nmap) And I have physically access to the system. Has anybody an idea how to fix that? thanks in advance Oliver
Oliver Ziltener wrote:
Dear list
This is not directly a security question, but the technologie what I use comes from the security area. So I hope somebody can support me from this list. After a clean shutdown (due maintanence at the 230V system) of the system, it was not possible to connect again via ssh. And of course afew days before was ssh working perfect. I can see in the sniffer files that the tcp 3 way handshake is working fine, but afterwards I get a timeout. No information in any logfiles about ssh failure. I use on a win a putty-client. The ssh daemon is running. I use suse 8.0 with susefirewall2. The system response to port 22 (checked with nmap) And I have physically access to the system. Has anybody an idea how to fix that?
try ssh -P [otheroptions] host Sven
participants (2)
-
Oliver Ziltener
-
Sven 'Darkman' Michels