rlogin: no directory! connection closed

Cause

When user tries to remotely login to a machine, he gets the error.

The machine that the customer was trying to rlogin(1) to had permissions of 700 on its root directory. The permissions on root should be 755.

Once the user changed the rootpermissions to 755, he was able to get farther when attempting a rlogin, but it still failed:

Last login: Fri Aug 29 10:24:43 from machinename
no shell
connection closed

Action

The machine that the user was trying to rlogin into had the permissions set to 700 on both the root and /usr/bin directories. For both directories, the permissions should be 775. Once the user changed the permissions to 775, rlogin(1) was successful.

Another possibility is to check the user's >passwd(1) entry in the NIS/NIS+ map. A login shell such as /usr/dist/exe/tcsh or /net/lab/.../csh could cause the failure because of NFS mount permission.