AIX

We are poking around in the dark. I suggest you do not tell us what you see but show us what you see. We cannot look directly at your system and obviously something escaped your attention, otherwise it would work. So show us and maybe it won't escape our recognition. What i mean is: post dumps of the relevant configuration files, the actual commands you tried, the mentioned lsuser output, etc., instead of telling us you can't see anything wrong.

There is a saying, "all scientists are from Missouri". One of their Congressmen, Mr. Vandiver, in 1899 hold a speech at a naval banquet, where he said: "I come from a state that raises corn and cotton and cockleburs and Democrats, and frothy eloquence neither convinces nor satisfies me. I am from Missouri. You have got to show me."

So, please: show us.

I hope this helps.

bakunin

When you say you can "rsh" to the machine, and then do things, we are assuming that you are getting a shell. Is that what you mean to say as well?

i.e., instead of doing $ rsh machine date or you simply using $ rsh machine?

Additional question: is is not working from all systems, or only from one? I am thinking that there may be a problem with the contents of ~/.ssh/known_hosts

Ahem, this is the AIX forum. It is fair to assume that the thread-o/p uses the AIX-variants of all the commands involved.

bakunin

I was just suggesting the poster run a diagnostic option. They eventually did.

So, I guess we need the same from the AIX ssh version he is using. The client "should not" matter. Famous last words, perhaps?

I haven't used the r-commands for a long time, but last time i checked "rsh" was a program of its own and not some alias for "ssh". This might be different in other *nix-flavours (including the Linux distro hanson44 seems to be using) but in AIX "rsh" will execute /usr/bin/rsh, which is an executable with the expectable function.

Among the things worth posting would be the hosts.equiv files and the relevant parts of their contents too. It would also help to know if there is a Kerberos-domain set up or not (and if there is, how it is configured, of course), because "rsh" can be run Kerberos-aware too.

I hope this helps.

bakunin

as his client quotes openssh i am assuming it is connecting to port 22 which will waken the openssh sshd daemon, not the rshd.

what has been left unsaid is if he is using the same user name in all situations.

as stated before, too much guessing needed by us. problem is not clear enough to me to be more specific in my answer.