On Mon, Jul 7, 2008 at 7:31 PM, MHR <mhullrich at gmail.com> wrote: > If I shut off the firewall on sushi (/etc/init.d/iptables stop), the > rsh connections all work fine. I need to go research how to read the > iptables output because right now it's greek to me - I can read the > letters, but the words don't make sense. To open those ports on the firewall, use "system-config-securitylevel-tui", then press the "Customize" button. On the list of ports add 513 and 514 to "Other ports". This should open the ports you need for rsh and rlogin (to the whole world!) in sushi. If you want a more customized firewall than this, you will either do it by hand or look at packages such as shorewall or others (I'm not familiar with them, so I wouldn't know which one to recommend). > Haven't gone the ssh route yet (this is all supposed to be on a secure > internal network, so that shouldn't be needed You should really consider moving to SSH, independently of needing encryption or not. If you really look at it, it requires less setup than rsh/rlogin does, and it's certainly easier to troubleshoot. And ssh-keygen or ssh-agent would solve your issue with typing your password repeatedly. If I were you, I would ditch rsh at once and start to look to SSH. You won't regret it. HTH, Filipe