Prev: Weird happening to openSUSE
Next: Windows network
From: mike-yue on 6 May 2008 06:44
My suse is Opensuse10.0
My client box is Windows server 2003, the ssh tunnel is putty.

from the windows side, the suse is ping-able, but ssh connection can't
be estabilished. The putty gave message "Network error: Connection
timed out".

from the suse side, the windows is NOT ping-able. I tried ssh from
suse to itself, both root and other users work fine.

The suse network adapter works fine, I can access internet with
firefox without any problem.
The windows network is working without problem.

Can someone give me some hits?

(I've set the PasswordAuthentication to yes in /etc/ssh/sshd_config;
The Protocol set to 2.)

Thanks a lot
From: whitemice on 6 May 2008 07:00
On May 6, 6:44 am, mike-yue <needpass...(a)gmail.com> wrote:
> My suse is Opensuse10.0
> My client box is Windows server 2003, the ssh tunnel is putty.
> from the windows side, the suse is ping-able, but ssh connection can't
> be estabilished. The putty gave message "Network error: Connection
> timed out".
> from the suse side, the windows is NOT ping-able. I tried ssh from
> suse to itself, both root and other users work fine.
> The suse network adapter works fine, I can access internet with
> firefox without any problem.
> The windows network is working without problem.
> Can someone give me some hits?
> (I've set the PasswordAuthentication to yes in /etc/ssh/sshd_config;
> The Protocol set to 2.)

Open the SSH port on the firewall of your SuSE box; and make sure the
service is enabled (chkconfig sshd on; service sshd start)
From: mike-yue on 7 May 2008 02:34
On 5ÔÂ6ÈÕ, ÉÏÎç4ʱ00·Ö, whitemice <adamtaunowilli...(a)gmail.com> wrote:
> On May 6, 6:44 am, mike-yue <needpass...(a)gmail.com> wrote:
>
> > My suse is Opensuse10.0
> > My client box is Windows server 2003, the ssh tunnel is putty.
> > from the windows side, the suse is ping-able, but ssh connection can't
> > be estabilished. The putty gave message "Network error: Connection
> > timed out".
> > from the suse side, the windows is NOT ping-able. I tried ssh from
> > suse to itself, both root and other users work fine.
> > The suse network adapter works fine, I can access internet with
> > firefox without any problem.
> > The windows network is working without problem.
> > Can someone give me some hits?
> > (I've set the PasswordAuthentication to yes in /etc/ssh/sshd_config;
> > The Protocol set to 2.)
>
> Open the SSH port on the firewall of your SuSE box; and make sure the
> service is enabled (chkconfig sshd on; service sshd start)

port 22 is opened, and sshd is running.
from suse side, ssh root(a)127.0.0.1 is working fine; ssh
mike(a)192.168.0.3 also works. so it is neither an issue of the port,
nor the sshd daemon.
From: mike-yue on 7 May 2008 04:07
I just solved the issue.
The solutions is: modify /etc/sysconfig/SuSEfirewall2 as the /usr/
share/doc/packages/SuSEfirewall2/EXAMPLES sample 2. Small home
network.
The sample settings are:
FW_DEV_EXT="dsl0"
FW_DEV_INT="eth0"
FW_ROUTE="yes"
FW_MASQUERADE="yes"
FW_MASQ_NETS="192.168.10.0/24"

after I reboot the suse(should I restart sth instead of reboot?) the
ssh works good from windows side.
I know it is a little risk, but, I just want the ssh connection
working for a couple of hours, then I will change all settings back.

Thank you guys for your time.
From: Gary Gapinski on 7 May 2008 12:23
mike-yue wrote:
> (should I restart sth instead of reboot?)

No need to reboot - just execute "rcSuSEfirewall2 restart".
 | 
Pages: 1
Prev: Weird happening to openSUSE
Next: Windows network