remshd: Login incorrect.

[Ralph Grothe]

Hello,

new box, so far SSH not installed yet,
until I've got a running sshd I need to transfer files from another box,
try to do it by tar and remsh,
but always get

remshd: Login incorrect.

I've forgotten what to switch to enable remsh commands (don't mean trusted hosts like .rhost, password is ok, as as soon as SSH is installed I won't use remsh anymore.
I looked at /etc/inetd.conf but looks ok.
I also produced a /etc/shells that contained /bin/remsh
but doesn't change anything.

There is however a inetd.sec file, so I added an allow line for the host from where I want to do the tar and rexec but doesn't help (maybe wrong syntax?)

# grep -v ^# /var/adm/inetd.sec
dtspc allow 127.0.0.1 loopback rubiconx
rexecd allow 10.45.11.123

[Sridhar Bhaskarla · Accepted solution]

Hi,

If it is a problem with inetd.sec, then the connection would be refused. So, your inetd.sec is ok. I dont' think syntax of your command is the culprit here as it is trying to connect to the system.

1. Look at your .rhosts file (in the home directory)on the remote host and make sure the syntax of the file is correct. "system_name login".

2. Enable connection logging of inetd on the remote server by doing an inetd -l. Then look at /var/adm/syslog/syslog.log while doing a remsh/rlogin onto the box. You may find errors there.

If it is not the .rhosts, then it could be that remote host is resolving the IP of your source host differently.

-Sri

[Stefan Farrelly]

There should be 2 lines in /etc/inetd.conf

login stream tcp nowait root /usr/lbin/rlogind rlogind
shell stream tcp nowait root /usr/lbin/remshd remshd

You dont need /etc/shells - we dont use them, remove it. /var/adm/inetd.sec should only have one line active;
/vdtspc allow 127.0.0.1 loopback flowers

Sometimes it can take some time before inetd rereads its conf file and same for inetd.sec
Cant think of much else apart from password stuff which would give you login denied - maybe reverse lookup ? dns ?

[Sajid_1]

A quick try - check and see if your inetd.conf file contains '-l' option for 'remshd'. If it is there then remove it and try:
# inetd -c

And check again

[Uday_S_Ankolekar]

Hello,

You should check /var/adm/inetd.sec file
check for login,shell,exec etc.. should be allow to your new box

-Goodluck
-USA..

[Pete Randall]

Ralph,

I think you're going to need to create .rhosts and/or /etc/hosts.equiv - at least temporarily. I would do both and list both hosts in each of the files (on both hosts). When you've SSH running, you can go back and get rid of the .rhosts and hosts.equiv.

Pete

[S.K. Chan]

Example .. cannot remsh from box A to B. Login/telnet to B from A and run "who -Rm", that will (the last field in the output) show how host B resolve host A. That's the exact hostname you'll have to use in your .rhosts. It may/may not be a full domain name. If you only see IP address, it means B is having problem resolving hostname for A.