unable to remsh

[Mike Spencer]

I have two HP-UX 11.0 systems (Host A and Host B). I'm able to remsh from Host A to Host B as "user1", but unable to remsh from Host B to Host A as "user1".

1) the "user1" ID has been set up on both hosts
2) both hosts (A & B) are in the .rhosts file in both $HOME's; the permissions and ownership are also the same on both .rhosts
3) I have set up another ID (user2) on both hosts and given him remsh access in the same way as user1. I'm able to remsh in both directions using this ID.

I'm really not sure what else to check. If you have any ideas on what I might be neglecting, please let me know.

Thanks in advance.


Mike

[Pete Randall]

Mike,

Are the home directories correct in the two passwd entries for user1?


Pete

[Jeff Schussele]

Hi Mike,

Make sure HostA does *not* have any rules in /var/adm/inetd.sec preventing either user1, the host user1 is using or the subnet that the host user1 is using is on from connecting. You should also check whether HostA has tcpwrappers installed & is using /etc/hosts.allow and/or /etc/hosts.deny

Rgds,
Jeff

[steven Burgess_2]

Hi

Have you checked the account on the server you are trying to remsh to that you are having a problem with ? ensure it's not expired etc

what message do you receive ?

HTH

Steve

[Uday_S_Ankolekar]

Try adding users /etc/hosts.equiv file

-USA..

[Mike Spencer]

Pete,

Yes, the home dir's are correct in both passwd files. I just double-checked.

Jeff,

That's one thing I neglected to mention. I did check the inetd.sec on both hosts and there don't appear to be any rules that would prevent my remsh

[Michael Steele_2]

This is 'remsh' and not 'rlogin', so 'rlogin' works, right?

is there any flag in your command to insist on interactive usage?

You should be seeing an error but I don't see any posting of it. I.e., login incorrect.

Can you use the fully qualified host name and succeed? I.e. host@domain.com.

[Mike Spencer]

Michael,
Yes, perhaps I was unclear about what the precise problem is. I am able to remsh to host A as user1, but I have to supply the passwd in order to do so (which kinda defeats the purpose of using remote shell). Note: I can remsh (without supplying a password) from A to B, under the user2 ID.

[Michael Steele_2]

Please run a 'pwck' and 'grpck' on your /etc/passwd and /etc/group files.

# pwck

# grpck

Perhaps remove and add in the problem user.

Any you've checked all the permissions? Right?

$HOME dir.s are executable?

[Mark Grant]

One more thing, does the user have the same shell on each host?

[Bryan D. Quinn]

Hey Mike,

Check your host file on both systems. Make sure that everything is ok in there. Specifically look at the host file on HOSTA, since that is the one asking for a password. I had the same problem with one of my servers. The server asking for the password did not have an entry in it's host file for the other server.

Hope this helps!
-Bryan

[Mike Spencer]

I appreciate all of the responses and suggestions, but nothing has been successful thus far. Based on the behavior, I think it's fairly reasonable to assume that this is not a "host-specific" problem, rather an "id-specific" problem. I set up the exact same scenario for another user (remsh'ing between the same 2 hosts), and that works fine. I have also tried everything that has been proposed, but to no avail.

If you have any other suggestions, please submit. I'm obviously at a loss.

[Pete Randall]

Mike,

Last guess: re-create the .rhosts files for user1 on both hosts.


Pete

[Sam_83]

Mike,

Check the entry for 'shell' in /etc/inetd.cfg
It should not have "-l" at the end because that disables the /home/*/.rhosts functionality.

-Sam

[Sam_83]

correction:
/etc/inetd.conf iso /etc/inetd.cfg

[Jakes Louw]

Use rlogin to connect to the server that prompts you for a password, then enter the password so that you can log in.
Then run "finger -l | more", and find the entry for the user you have just logged in as. Check the "Login name:" against the "In real life:" user name. Then check the server name in the line that looks something like :
"On since Oct 10 08:48:23 on pts/38 from host.domain".

Check that the username and the "host.domain" is correctly recorded in your .rhosts for the server and user yoiu have just logged into (or in hosts.equiv if you are using that).

I've had weird problems like this due to vagueries in DNS lookup sequences, duplicate entries for a specific IP in /etc/hosts, and so on.

[F. X. de Montgolfier]

Hi,

since this doesn't seem to be related to inetd.sec, would you perchance have an ip filter on your B machine?
The easiest way to check if you may have one is to check if you have an /etc/rc.comnfig.d/ipfconf script with the variable IPF_START set to 1.
In which case, you may want to look at the $IPF_CONF file defined in the same script and remove the rule preventing you from remshing to the other host...

HTH,

FiX