LinuxQuestions.org - Configuring sshd - Cannot remote from other linux

- SUSE / openSUSE (https://www.linuxquestions.org/questions/suse-opensuse-60/)

- - Configuring sshd - Cannot remote from other linux (https://www.linuxquestions.org/questions/suse-opensuse-60/configuring-sshd-cannot-remote-from-other-linux-458651/)

Configuring sshd - Cannot remote from other linux

Hi.. Im really new into the use of linux systems. Can someone help me on my problem.

I have two computers.. One is using a FEDORA as OS and the other is using SUSE.. I have a problem connecting to my SUSE Linux using SSH but if I use SUSE to connect to FEDORA I can easily connect..

I tried modifying the /etc/ssh/sshd_config file... but still I cannot connect to the SUSE linux.

Are there other files that I should me modifying..?..?..

what's the error message?
are you trying to connect using root? often connecting with root user is not allowed (for security reasons)

this is the command that I used

Code:

ssh 192.168.1.100 -l ethnicme

and this is the error that comes out

Code:

ssh: connect to host 192.168.1.100 port 22: No route to host

can you ping the machine?

yes I can ping the SUSE linux and vice versa...

are there any other files I should be modifying..

I also set the hosts.deny and the hosts.allow to proper settings.. but still I cannot log into the SUSE linux..

don't you have a default firewall setup? iptables or somethin?

Have you tried SSH-ing into the same box. IE if your pc you are ssh-ing from is 192.168.1.45, then try to ssh to that box.

Yes I do think I have a firewall..
because when I try to restart the network..

Code:

Setting up network interfaces:

    lo

    lo        IP address: 127.0.0.1/8                                done

    eth0      device: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91)

    eth0      configuration: eth-id-00:11:5b:fc:db:86

    eth0      (DHCP) . . . . . IP/Netmask: 192.168.1.152 / 255.255.255.0 ('pixelstream')

Error while executing:

  Command 'ip route replace to 192.168.1.2/24 via 192.168.1.2 dev eth0' returned:

  RTNETLINK answers: Invalid argument

  Configuration line: 192.168.1.2 192.168.1.2 255.255.255.0 eth-id-00:11:5b:fc:db:86

Error while executing:

  Command 'ip route replace to 192.168.1.1/24 via 192.168.1.1 dev eth0' returned:

  RTNETLINK answers: Invalid argument

  Configuration line: 192.168.1.1 192.168.1.1 255.255.255.0 eth-id-00done5b:fc:db:86

Setting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  .  done

SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.

SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...

SuSEfirewall2: batch committing...

SuSEfirewall2: Firewall rules successfully set

it can connect to other linux computer using ssh..

Sorry I don't know anything about firewalling with linux
somebody else, maybe?

yes I have allowed the sshd service in the firewall..

but still when I logged..

an error stating that..

Code:

No error could be made because the target machine actively refused it

are there other configuration files on where I can modify the allow of access through SSH..?..

Quote:

Originally Posted by ethnicme

No error could be made because the target machine actively refused it

A simple Google (or clusty.com if you prefer) on "because the target machine actively refused it" shows a strong tendancy towards it being a Microsoft (dot net whatever crap) error message,

I was wondering about such a use of words: "No error could be made...". That's either hyper-geek or hyper-loonie.

Anyhow, you could perhaps try on a MS forum. Or two.

As for SuSE, I set up lots of virtual machines (9.3 and 10.0) and I enable ssh and there's absolutely nothing to it. If you can ping, you can ssh. Between Linux machines, that is.

Quote:

Originally Posted by carcassonne

....
....
I was wondering about such a use of words: "No error could be made...". That's either hyper-geek or hyper-loonie.
....
....

I forgot I was using a a ssh software runned by widows xp..

the software was [b]bitwise tunnelier[b]..

anyway.. guys I got it running already..

thank for the offered help guys..