From: Jose J. Cintron (jcintronmitre.org)
Date: Tue Feb 24 2004 - 09:23:56 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I'll stick with the obvious... Since you are able to connect when you
disable the FW it is safe to assume that the FW is the problem and not
SSH or the clients...

Checke the following line in /etc/sysconfig/SuSEfirewall2

FW_SERVICES_EXT_TCP=""

and make sure that it has either ssh or 22 as one of the untries between
the ""

Richard Farla wrote:
> Op maandag 23 februari 2004 23:11, schreef u:
>
>>I'm just going to state the obvious here, but it's a start... Have you
>>tried turning off the FW to make sure that is not the source of your
>>problem? Any error messages on the client side, when you try to connect?
>>Are you sure that both the client and the server are using the same SSH
>>protocol?
>>
>>
>
>
> Hello again,
>
> I turned off FW and then I can access it using SSH, so probably not a v1 or v2
> issue. Yes sshd is running.
> Strange is that I setup FW with yast2 and surely allowe SSH as added service,
> I also accept port 22 to be open. This is confermed to be open using nmap
> scanning localhost (127.0.0.1)
>
> Looking in /var/log/messages I notice that the boxes that want to gain access
> will be DROPPED by SuSE FW.
>
>
> Richard.
>

--

+------------------------------------------
| José J. Cintrón - <jcintronmitre.org>
+------------------------------------------

--
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-helpsuse.com
Security-related bug reports go to securitysuse.de, not here

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]