The hostname & the user name are already present in AIX box. As I said I am able to get the remote shell using "rsh <hostname>" from Solaris box to AIX box. The only problem which I am facing is while running the remote shell commands like "rsh <hostname> date" etc from Solaris box to AIX box.
Note : Let me clear that from the same AIX box, I can run remote shell commands for Solaris system & even from all AIX box to AIX box, remote shell commands are working.
Kindly suggest if something needs to be done OR change at Solaris side.....
Yes after getting the AIX remote shell using "rsh AIX-Host" command, I am able to run all the AIX commands on remote shell of AIX system.
Solaris10>rsh AIX-Host
AIX>date
AIX>ls -l
AIX>df -k
All the commands works fine.
Even I have tried by adding the host entry of AIX system in /etc/inet/ipnodes file on Solaris 10 system. As per the documents, in Solaris 10 system checks for /etc/inet/ipnodes prior to /etc/hosts. But then also I am getting the same error.
Solaris10# rsh AIX-Host df -k ----- it fails with an error;
" rshd:0826-826 -- The host name for your address is not known."
Can someone suggest is there anything needs to be change at Solaris 10 system side i.e kerborse security config files (krb5.conf) etc...???
was it in a production??
do you have any other alternative to connect to it from your solaris box??
because - i can see it still have the same problem rising from your solaris box.
Both (Solaris 10 & AIX) systems are production system. I am not able to give the output's of the /etc/hosts & $HOME/.rhosts files, because the customer is not ready to provide with the information. The only thing which is bothering me is that I am able to get the remote shell.....so why the remote shell commands are not working directly from Solaris10..???
Sounds like your systems using IPV6 , not IPV4.
There was a bug in earlier releases of Solaris 10 where rsh <hostname><command> doesn't work in IPV6 systems,
but rsh <hostname> does. I think was fixed is Solaris 10_23
cat /etc/release to see what release you have.
BUGID 4760974 was logged about this.
In IPv6 systems, rsh a hosts with "ls" doesn't print out anything.
# uname -a
SunOS fourunner 5.10 s10_20 sun4m sparc SUNW,SPARCstation-10
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
le0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.29.78.32 netmask ffffff00 broadcast 192.29.78.255
ether 8:0:20:1a:bc:fc
lo0: flags=2000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6> mtu 8252 index 1
inet6 ::1/128
le0: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2
ether 8:0:20:1a:bc:fc
inet6 fe80::a00:20ff:fe1a:bcfc/10
#
# rsh tercel ls /
# echo $?
1
#
# rsh tercel
Last login: Thu Oct 10 00:29:02 from fourunner
Sun Microsystems Inc. SunOS 5.10 s10_20 Oct. 08, 2002
SunOS Internal Development: gk 2002-10-08 [on10_20]
# ls
autohome electron import opt shared vol
bin etc kernel platform small ws
cdrom etc.tar lib proc src xfn
dev etc.tar.ssh lost+found results syncNwait
devices export medium sbin tmp
doe getUtil mnt scde usr
earth home net share var
#
In IPv4 systems, rsh a host with a UNIX command works.
# uname -a
SunOS ficus 5.10 s10_20 sun4u sparc SUNW,Ultra-1
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
le0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.29.79.113 netmask ffffff00 broadcast 192.29.79.255
ether 8:0:20:8d:1f:3b
# rsh bolyai pwd
/
# echo $?
0
#
Good call I completely forgot about that becasue we don't use IPv6, 23 was a problematic release, I would go to 24, which has a few dependencies. If you have an entitlement, the EIS 3.0.11 patch cluster seem to be a good release.
