rlogin problem

[Joanne Keegan]

Hi Everyone,

For some strange reason I'm having problems with rlogin (via root) to one of our servers. Another server can rlogin (via root), yet not another one. I've checked /.rhosts and /etc/hosts.equiv. They are configured correctly. I've checked permissions of these files, deleted and recreated them, etc - but things still don't work. I have compared them against a system that can successfully rlogin, and everything seems okay.

What am I overlooking?

Regards,

Jo

[harry d brown jr]

Check to make sure both hosts can resolve each other. What does your /etc/resolv.conf file look like?

live free or die
harry

[John Bolene]

DNS or the hosts file may know the machine by a different name.

In the .rhosts file be sure and have the DNS name that shows up when doing a "who -a" command.

[Sanjay_6]

Hi Joanne,

what is the error message you get when you try to "rlogin".

Do remeber that if you are logginf in from server1 to server2 as root using rlogin server2 should have an entry in /.rhosts file as

server1 root

Hope this helps.

Regds

[Craig Rants]

"For some strange reason I'm having problems with rlogin (via root) to one of our servers. Another server can rlogin (via root), yet not another one. I've checked /.rhosts and /etc/hosts.equiv. They are configured correctly. I've checked permissions of these files, deleted and recreated them, etc - but things still don't work. I have compared them against a system that can successfully rlogin, and everything seems okay."

Have you looked at syslog.log. If you are logging inetd connections some valuable information will be in there. If not edit /etc/rc.config.d/netdaemons and enter "-l" after the INETD_ARGS= option. Then restart inetd through /sbin/init.d. No inetd -c will not work for this since there was no change to the config file.

Hope this helps,
C

Personally I would look into secure shell for this type of stuff.

[Joanne Keegan]

I want to be able to login without having to enter a password and to be able to do remsh statements (error: remshd: Login incorrect).

Regards,

Jo

[Darrell Allen]

Hi Joanne,

Is /var/adm/inetd.sec denying access from the server that is failing?

Are you being prompted for a password or is the connection refused?

Darrell

[Sanjay_6 · Accepted solution]

Hi Joanne,

Do a "nslookup" on both the servers and check that the hostname and ip's are correctly resolved.

Try, on server2

nslookup
> server1_name
> server1_ip
> exit

on server1

nslookup
> server2_name
> server2_ip
> exit


Hope this helps.

regds

[Sanjay_6]

Hi Joanne,

Here is a thread on .rhosts,

http://us-support2.external.hp.com/cki/bin/doc.pl/sid=7867a22601145be36a/screen=ckiDisplayDocument?docId=200000006377362

Hope this helps.

Regds

[Darrell Allen]

Either I type real slow or my Internet connection is slow.

Name resolution is key. I'd ensure /etc/nsswitch.conf has files before dns and make sure the hosts files are accurate.

Darrell

[Steve Labar]

Try rlogin by IP address vice host id. If you are able to rlogin by IP, then verify your addresses resolve properly using nslookup. If you still cannot rlogin by IP, check your /var/adm/inetd.sec if it has an entry to permit rlogin, only the entries listed will be permitted. If the 2 servers are on 2 subnets you can verify you have network connectivity via ping command.

Steve

[Sridhar Bhaskarla]

Hi Joanne,

I am pretty sure you have checked your .rhosts, hosts.equiv, /etc/hosts, /etc/resolv.conf etc., etc.,

The best way to troubleshoot is to enable inetd logging.

#inetd -l

This is going to start logging the commands.

Now try to do an rlogin to this system and observe the syslog.log. You should get something like this

Dec 3 12:18:48 hostA inetd[24273]: shell/tcp: Connection from hostB(
xx.xx.xx.xx) at Mon Dec 3 12:18:48 2001

Now check hostB to make sure it is there in .rhosts of hostA.

Most of the times we configure aliases in /etc/hosts but mess up the order. For ex., if your /etc/hosts on hostA is like this
...
...
xx.xx.xx.xx alias1 hostB alias2 alias3

You will not see any problem anywhere but if you try to rlogin from hostB, hostA will understand that it is coming from alias1 and refuse the connection as we mentioned hostA in .rhosts.

-Sri

[Joanne Keegan]

Thank-you to all that replied. I now have things working. Using nslookup basically was the key. The hosts file had two entries against the ip address, each with a different host name.

Once again, thank-you. I thought the answer would be something simple, something I overlooked.

Regards,

Jo

[Ian Dennison_1]

Have you changed the password since the last guy left?

Share and Enjoy! Ian (aka Fred)