|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Sven 'Darkman' Michels (sven_at_darkman.de)
Date: Wed Jul 24 2002 - 14:42:26 CDT
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
-- To unsubscribe, e-mail: suse-security-unsubscribesuse.com For additional commands, e-mail: suse-security-help
suse.com Security-related bug reports go to security
suse.de, not here
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
suse.com
For additional commands, e-mail: suse-security-help