remsh problem

[dictum9]

Trying to remsh to an Itanium 11.23 box and the remsh asks for a password. I set up the ~/.rhosts file but the problem persists.

Once I enter the password, it logs me in, but cannot do passwordless logins.

Looking at /etc/inetd.conf and /etc/services, everthing looks reasonable.

Any idea what is going on?

[John Dvorchak · Accepted solution]

Are you trying to remsh to the 11.23 box as root? What is the perms of ~root/.rhosts? It should be 400.

[A. Clay Stephenson]

Is this a non-root user and is the -l remshd option in effect? (Check /etc/inetd.conf for this).

[James R. Ferguson]

Hi:

I'd review the contents of your '.rhosts' file. Make sure, too that your file is readable and writeable only by the owner.

Regards!

...JRF...

[dictum9]

I forgot to mention that I am doing it as a regular user.

When I try to remsh to execute a command on there, it says login incorrect.

when I try to login in via remsh, it asks for the password, and when I enter the password, it logs me in.

But it doesn't do password-less authentication.

[John Dvorchak]

Are you logged on to the originating box as the same userid as on the target box? If not you have to use the -l userid switch. From the man remsh page:

remsh -l user_on_host hostname command

Also does the host use password authentication or some sort of SecurID card where the password changes every minute or so?

[dictum9]

#:grep remsh /etc/inetd.conf
shell stream tcp6 nowait root /usr/lbin/remshd remshd
# The standard remshd and rlogind do not include the Kerberized
kshell stream tcp nowait root /usr/lbin/remshd remshd -K





$ ll .rhosts
-r-------- 1 test1 sap 76 Jan 30 15:58 .rhosts

[Denver Osborn]

Are you using the shortname or fqdn in .rhosts file?

After you rlogin using password, what host does "who -mR" display? This string doesn't match the .rhosts entry. You could also change the hostname to the ip for testing in .rhosts

Hope this helps,
-denver

[Denver Osborn]

ew. I need to reword that or stop playing on the ITRC and take a nap. :)

Anyhow, should've been... run "who -mR" and if the host string doesn't match what's in your ~/.rhosts entry, fix it.

-denver

[dictum9]

Bingo - that fixed it. It was resolving to hostname.backups.com, not the primary name. Don't know why, but I included it in the .rhosts - and it works, without the password now.

quote-----------------------

who -mR" and if the host string doesn't match what's in your ~/.rhosts entry, fix it.