SCIENTIFIC-LINUX-USERS Archives

January 2009

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jan Iven <[log in to unmask]>
Reply To:
Date:
Wed, 21 Jan 2009 12:18:28 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
On 21/01/09 10:47, Honest Guvnor wrote:
> Greetings,
> 
> With Scientific Linux 5.1/5.2 on i386/x86_64 we are struggling a bit
> to get rsh running. The current situation:
> 
> [andy@horst2 ~]$ /usr/bin/rlogin -l andy meyer
> Last login: Wed Jan 21 10:00:06 from bolt
> [andy@horst2 ~]$ /usr/bin/rsh -l andy horst2 date
> Wed Jan 21 10:25:34 CET 2009
> [andy@horst2 ~]$ /usr/bin/rsh -l andy meyer date
> poll: protocol failure in circuit setup
> [andy@meyer ~]$
> 
> Summary:
> - rlogin to another machine works.
> - rsh to the local machine works.
> - rsh to another machine fails.
> - rsh to another machine works if the firewall is disabled on the
> local/client machine (not shown).

rsh and rlogin use two different ports (513, 514), check whether the
appropriate holes are in your server firewall (/etc/syconfig/iptables).
Then make sure the client accepts the callback traffic (on some random
port) from the server.

And then forget about it and use ssh :-) , unless you'll never have any
untrusted machine on your network..

Cheers
Jan

ATOM RSS1 RSS2