topic Re: w2k -> HPUX rsh fails if username in hosts.equiv in Operating System - HP-UX

w2k -> HPUX rsh fails if username in hosts.equiv

Michael_356 — Mon, 17 Nov 2003 06:08:11 GMT

After all rsh-messages, i'd found in this forum, i'm ashamed to ask again.
My Situation as following:

PC with W2K
Server with HPUX 11.00

1.) I set my /etc/hosts.equiv to + +.
Then i run rsh host -l user1 date.
That works fine

2.) I set my /etc/hosts.equiv to PC21 +.
Then i run rsh host -l user1 date.
It works fine too.

But:

3.) I set my /etc/hosts.equiv to PC21 user1
If i ran rsh host -l user1 date
i get the message:
remshd: Login incorrect.

What's wrong now?
Anybody out there who can explain what's going wrong there?

It's not allowed for this servers, to run with the '+'-sign.

Re: w2k -> HPUX rsh fails if username in hosts.equiv

Laurent Menase — Mon, 17 Nov 2003 06:50:13 GMT

The hosts.equiv supposes that both of your the same user.

Apparently your user on W2K is not user1.

To check that you can use ethereal to trace the communication between the 2 systems, and check that the servers user and the client user are the same

If they are both different, you will have to
put PC21 yourw2kuser in this user1 .rhosts

Re: w2k -> HPUX rsh fails if username in hosts.equiv

Michael_356 — Mon, 17 Nov 2003 08:44:04 GMT

Thanks alot for this answer, all works fine.
But a small downer remains now.
The target for our security-guideline is a system without any .rhosts.
If i get the point, there's no way to avoid this file, while we are connecting via Windows, right?

Thanks again and 10 points for your answer

Michael

Re: w2k -> HPUX rsh fails if username in hosts.equiv

George McDuffie — Mon, 12 Jan 2004 16:41:39 GMT

I had the same problem. In tracing the remshd, I found that the WIN client was returning the username in all CAPS. Try making your user on the HP machine all caps and try again....