1820603 Members
1790 Online
109626 Solutions
New Discussion юеВ

Re: problem with rlogin

 
andrea_53
Advisor

problem with rlogin

Hi people,
I have a problem.
rlogin ask me the password to connect to the server!!!
I checked everything in the .rhosts, /etc/hosts, resolv.conf, nsswitch.conf and everything is fine.
/etc/host.equiv doesn't exist.
DNS is working fine!!
Please help me!!!
Thank you
12 REPLIES 12
Domenico_5
Respected Contributor

Re: problem with rlogin

hi andrea

have you write correctly .rhost?

hostname user
Domenico_5
Respected Contributor

Re: problem with rlogin

sorry

I have cliked so quikly.

check if you dns work correctly, connect to the server with telnet, use who -R for read you user so you can check if .rhost have the correct user

by
harry d brown jr
Honored Contributor

Re: problem with rlogin


ROOT user or some other user? IF it is "root", then take a look at /etc/securetty


live free or die
harry
Live Free or Die
Pete Randall
Outstanding Contributor

Re: problem with rlogin

Hi Andrea,

Typically, when I run into this, it's because the .rhosts on one server does not contain an entry for the other server. In other words, the .rhosts file on HOSTA must contain an entry for HOSTB and vice-versa. The .rhosts file must be in the proper location as well. If /etc/passwd on HOSTA says the home directory is /root and /etc/passwd on HOSTB says the home directory is /, you can have problems.

I use hosts.equiv for regular users and .rhosts for root and keep these two files and the passwd file the same on all machines - that way, there's no problems.

Pete

Pete
Deepak Extross
Honored Contributor

Re: problem with rlogin

Hi,

From the man page of rlogin:
"For security purposes, the /etc/hosts.equiv and .rhosts files should exist, even if they are empty."

-hth.
Bonny Jose_1
Advisor

Re: problem with rlogin

Hi,
The hostname in .rhosts entry should be in such a way that how the second one knows Ist.

For this you do a ping from the server where you want to put .rhosts and see the reply. This reply will show you how the 1st is known to 2nd. Enter this name in .rhosts and this solve your problem.
Or you can put all the probable names like
IP
hostname
hostname.domainname

Cheers
Bonny Jose
let us make the world
Mark Ellzey
Valued Contributor

Re: problem with rlogin

Hi,

You may also want to check the file /var/adm/inetd.sec. This can also limit which hosts are allowd to log into your server.

Regards,
Mark
MANOJ SRIVASTAVA
Honored Contributor

Re: problem with rlogin

Hi Andrea


here is what you can try

server A IP ADD 10.2.10.30
server B IP ADD 10.2.10.32

in the /etc/hosts there should be an entry in both the servers .

then in $home/.rhosts of the user you shoould have

serverA username
serverB username

in both the servers .

if this doenst work then the server name is not being resolved properly , you migh like to change the .rhosts to

10.2.10.30 username
10.2.10.32 username

Also you can try to do rlogin locally to check whter there is a problem like taht or not.



Manoj Srivastava
Charles Akonnor
Advisor

Re: problem with rlogin

Normally name resolution in a big problem in this issue.
-Make sure the hostnames of both servers resolves to the right IP Addresses and that reverse lookup also works fine.
-Make sure the .rhosts entries are correct
-Before you type rlogin make sure the effective user id is the id of the user set to have rlogin access( type #id , to check this).
-If the above does not solve your problem then make sure the user id of the rlogin user is the same on both servers.


Never give up.
Robin Wakefield
Honored Contributor

Re: problem with rlogin

Hi Andrea,

Make sure the .rhosts (or whatever) entry is the *primary* FQDN entry as returned by nslookup, not an alias.

Rgds, Robin
Uday_S_Ankolekar
Honored Contributor

Re: problem with rlogin

Well,

Couple of things..

1.Try with ipaddress instead of hostname in .rhosts file.

2. check /var/adm/inetd.sec file if you have restrictions for telnet shell exec etc..

3. If you are tring rlogin for a user try with for different user or for the root and see if it works.

-Goodluck

-USA..

Good Luck..
Sanjay_6
Honored Contributor

Re: problem with rlogin

Hi Andrea,

I had this problem when i was using servers in different domain and doing an rlogin.

on server1
# nslookup
> server2

on server2
# nslookup
> server1

Say server1 is server1.domain1.com
server2 is server2.domain2.com

on server1 the .rhosts file should be

server2.domain2.com root any_other_user

on server2 the .rhosts file should be

server1.domain1.com root any_other_user

I think you can achieve this by adding domain1.com in the serach list in /etc/resolv.conf on server2 and vice versa too. I cannot try this before i post this answer because my test workstation which is another domain is down at the moment, clash of ip's that i'm trying to resolve.

Hope this helps.

Regds