>We've got several Ultras running Solaris 2.5.1 and a Solbourne running SunOS
>4.1.2 . rsh works properly among all the Ultras and from the Solbourne to any
>of the Ultras, but it's exhibiting a strange symptom whenever I try to rsh from
>an Ultra to the Solbourne.
>
>From the Ultra, "rsh solstice" (solstice is the Solbourne) works fine...it acts
>like an rlogin and throws me into the appropriate home account. But whenever I
>try to run "rsh solstice command" it hangs for a minute and returns "connection
>refused". I searched the archives and found a similar problem that was solved
>when the user set up the .rhosts file to include the username field. Been
>there, done that, no effect.
>
>The solbourne is acting as an NIS slave server, with the NIS master server
being
>one of the Ultras. Somebody here was wondering if using the services file on
>the Ultra (through NIS) could cause a problem like this. Would it?
Thanks to the following for their replies:
David Fetrow <fetrow@biostat.washington.edu>
Andreas Ehliar <dt95aneh@forsmark.uu.se>
Stephen Harris <sweh@mpn.com>
Casper Dik <casper@holland.Sun.COM>
There were two suggestions:
1. Make sure that /etc/services has a line like
shell 514/tcp cmd # no passwords used
and /etc/inetd.conf has a line like
shell stream tcp nowait root /usr/etc/in.rshd in.rshd
to enable rsh.
(These were set correctly)
2. This can also happen if one of the machines is running the secure shell
version of rsh.
(As far as I can tell, we're running plain ol' rsh)
So I'm still stuck with a machine which returns "connection refused" whenever I
try to do an "rsh hostname command" to it. Has anybody else run into this?
-- Bill Fenwick Email: fenwick@digicomp.com Digicomp Research Voice: (607) 273-5900 ext 32