[Gloucs] Lan configuration

[Glyn Davies]

David wrote:
>  As I have mentioned to Guy and others, I have been having problems 
> setting up a simple connection share between two Mandrake boxes.  The 
> hardware is recognised no problem, and both boxes can ping each other.  
> If I then run SSH 192.168.1.252 I get :*Port22 Network unreachable.*
> That is as far as it goes though and as a very simple newbie, I have run 
> out of ideas.
> 
> Ping shows the following  :
> PING 192.168.1.252 (192.168.1.252) from 192.168.1.253 : 56(84) bytes of 
> data.
> 64 bytes from 192.168.1.252: icmp_seq=1 ttl=64 time=0.662 ms
> 64 bytes from 192.168.1.252: icmp_seq=2 ttl=64 time=0.401 ms
> 64 bytes from 192.168.1.252: icmp_seq=3 ttl=64 time=0.406 ms
> 
> --- 192.168.1.252 ping statistics ---
> 3 packets transmitted, 3 received, 0% loss, time 2014ms
> rtt min/avg/max/mdev = 0.401/0.489/0.662/0.124 ms
> 

David,

<Disclaimer>
Not a Mandrake user. The following applies to RedHat. chkconfig, one of 
the commands I suggest you use looks as if it maybe a RedHat supplied 
package. If it is, I'm sure someone can suggest the Mandrake alternative 
(if not only to show Mandrake can do everything RedHat can) or can 
confirm whether a RedHat RPM containing chkconfig can be installed on 
Mandrake.
</Disclaimer>

First thing to check is if the sshd daemon is running on the target machine.

On the TARGET machine run 'ssh localhost'. If you get a response its 
most likely a firewall issue. If not, check to see the ssh server daemon 
starts on boot up with 'chkconfig --list sshd'. You should get a reponse 
like the following (you need to be root):

[root@bollow root]# chkconfig --list sshd
sshd           	0:off	1:off	2:on	3:on	4:on	5:on	6:off
[root@bollow root]#

If sshd is off for level 3 or 5, set it to start at boot time with 
'chkconfig sshd on'.

sshd will now start at boot time. You can start sshd manually (instead 
of rebooting) by typing '/etc/init.d/sshd start'

If the 'ssh localhost' worked fine and it looks like a firewall (on the 
target) issue, the first thing to do is switch off all firewalling and 
just get the stuff working.

Depending on your kernel, firewalling is controlled by ipchains (kernel 
<= 2.2) or iptables (kernel =>2.4). In either case (on RedHat :)) I'd 
switch both off with the following:

chkconfig ipchains off
chkconfig iptables off

Now try ssh from the remote machine. If it works now, let us know and 
the firewall dudes can jump in with their questions and advice.

Don't forget to put your firewall back in place with chkconfig!

HTH

-- 
Best Regards
Glyn Davies