SUMMARY: rsh problem

 hello,
   Since I have received a lot of mails in this regard, I am
posting a summary for this...

 hello All,
  Thanks a lot to all who responded. John Leadeham's suggestion
was right on target!!

> When you rsh from A to S, use the who command to see
> precisely what (host) name it thinks A is using. It may be
> that this does not match what is in .rhosts.
>
> John.

I did "who"  after logging in S. It didn't give me a fully
qualified host name (which is what was mentioned in .rhosts).
That was because, the machine had a local /etc/hosts file that
mentioned the nickname first before mentioning the fully
qualified domain name.

 Thanks John for your suggestion. It really saved me from pulling
my hairs out.

 In retrospect, I think a lot of suggestions from other people
pointed in the same direction as John's. It's just that I was not
able to catch on to them.

>>> Problem description:
> > I recently created a .rhosts file in my home directory. The file
> > mentions a number of machines (say, A, B, and C) from where I
> > would like to log onto a solaris 8 machine (say, S). When I do
> > rsh from machine A (running solaris 7) to S, I am prompted for my
> > passwd. However, when I do rsh from machine B (running solaris 8)
> > to S, I am able to get in without entering any passwd. I have
> > checked a number of things (including /etc/pam.conf) but I didn't
> > find any problem.
> >

 Regards,

 Samir Goel
 gsamir@cs.Rutgers.EDU

 -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -
 "To do the expected is duty, is routine, is sometimes boring.
  To do the unexpected is creativity, is fun, is adventure, is rebellion.
  To be able to do both is genius, is balance, is love, is life."
                                                       - K.V. Vihari
 -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -
                    http://www.cs.rutgers.edu/~gsamir/