Very Computer

Yes, I have a .rhosts file. I've put just about everything in it I can
think of, including

            fred
            FRED
            Fred
            fred.acadiau.ca
            FRED.ACADIAU.CA
            Fred.AcadiaU.CA
            <ip #>

But, if I try something like this on fred:

            rcp file barney:file

I always get permissioned denied. Only Barney is acting this way. Other
local hosts I've tried work. The main difference is that Barney is MIPS
box and all the others are Suns. To confuse matters more, earlier today
the rcp command worked for Barney as well. During the day I've installed
DNS and built a new libc.so, on Fred, not on Barney. Something is making
the remote machine barney not see remote copy commands from "fred" as
coming from "fred". The only way I can get it to work is by putting
a "+" sign in the .rhosts file, which of course is undesireable. If any
one has any ideas how I can debug this I appreciate hearing from you.

Thanks.

--

Acadia University, Wolfville, NS   Tel: 902-542-2201   Fax: 902-542-4364

.
.

Quote:> But, if I try something like this on fred:

>        rcp file barney:file

> I always get permissioned denied. Only Barney is acting this way. Other
> local hosts I've tried work. The main difference is that Barney is MIPS
> box and all the others are Suns. To confuse matters more, earlier today
> the rcp command worked for Barney as well. During the day I've installed
> DNS and built a new libc.so, on Fred, not on Barney. Something is making
> the remote machine barney not see remote copy commands from "fred" as
> coming from "fred".

I assume you can telnet from fred to barney OK, so you no that your DNS
name resolution with the new libc.so is working OK.

Idea #1

Take a careful look at the rcp executable on fred (i.e. "file /usr/ucb/rcp")
It may not be "dynamically linked" -- in which case your new libc.so is of
no use.  rcp may still be working with other machines if they happen to
also be in your local /etc/hosts.  For some reason this is the way my Sun
came set up -- telnet and ftp, etc. were dynamically linked, but I had
to swipe (er .. borrow, yeah, that's the ticket) a dynamically linked rcp
from elsewhere.

Idea #2

Name resolution on a MIPS is a little strange.  There is an extra file
/etc/vis.conf that contains special keywords that the system uses to
figure out how to do name resolution.  Mine (I want it to use DNS which
is running elsewhere on a Sun) has one line which reads:

host: dns files

which tells the MIPS to try the name server listed in /etc/resolv.conf first
and then /etc/hosts second.

Note that your MIPS only knows that it is receiving an rcp request from
some a.b.c.d internet address; barney is then trying to "unresolve" this
name either with a name server or locally and then match the name to something
in .rhosts.  

So see if you can figure out what the MIPS thinks its doing. (some help, huh?)

Marc Rossner