I did try to do the rcp as a normal user as well but that still gave
me permission denied... I thought it might have something to do with
.rhosts also so I added that and still to no avail...(ver 4.3.1)
thanks,
Adam
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
Hi Adam. I am assuming that you have entries on BOTH servers for BOTH
servers in the hosts.equiv and .rhosts. I ran into a similar problem
with AIX 4.3.1 where no matter what I got permissons denied with rcp.
The long and the short of the problem was that for whatever reason the
name wouldn't resolve in the .rhosts file without an IP domain name.
In 4.3.1 you must specify a domain for each host in the /etc/hosts file
so that sendmail can successfully resolve email addresses. You need to
create a file (if it doesn't exist) called /etc/netsvc.conf. Assuming
you use /etc/hosts and not DNS, this file simply contains this line:
hosts = local
This specifies the order in which the system will attempt to resolve
names. If you use bind (DNS) or NIS, you will have to change the
order. For example
hosts = bind,local,NIS
Then you need to modify your /etc/hosts file to reflect a domain name
for each host. You can use an alias for each host so that your life
doesn't get too messed up :)
IP host alias
10.198.69.100 spitfire.domain spitfire
The final thing I had to do to get things working was to include the
domain name for each host in the .rhosts file:
spitfire.domain root
I used to be able to just say "spitfire root" (specifies the root user
only can use r-commands) with AIX 4.1.x, and it seems to be fixed in
4.3.2. Oddly enough, some 4.3.1 boxes worked without the domain name.
It is a strange problem, but this domain name trick seems to work.
Anyway, I hope this helps.
Eric
<adam_...@my-deja.com> wrote in message
news:7rjdd5$vfo$1...@nnrp1.deja.com...
You should also check that the permissions for
/etc/hosts.equiv are set to 600 - this also applies to .rhosts
Your root login can be changed (in smit) to allow remote login -
but I prefer to have root accessed only by su from a private id -
then you have an log trail as to who is doing it...
(unless of course they mess with the sulog file)
mikep
AIX SysAdmin
TriZetto Group
Birmingham AL