remshd: Login incorrect.

[Leslie Chaim]

We have several servers this problem is only with one server.

If you say:

remsh $(hostname) date

it works fine. But,

remsh alias_name date

returns: remshd: Login incorrect.

Thanks

[Sridhar Bhaskarla]

Hi Leslie,

To better troubleshoot this problem, on the server where you are trying to remsh into, enable connection logging by "inetd -l". Keep a tail -f /var/adm/syslog/syslog.log session open and then try both 'remsh HOSTNAME date' and 'remsh ALIAS date'. See what syslog.log reports about the incoming hostname.

-Sri

[Jose Mosquera]

Hi,

Try to put always the resolution name retrieved by the nslookup command:
#nslookup alias_name

Rgds.

[John Poff]

Hi,

Can you successfully resolve the 'alias_name' hostname on that machine? Is 'nslookup' happy when you look up 'alias_name'?

JP

[harry d brown jr]

And your user name is what?

.rhosts is set up correctly?

live free or die
harry

[Paul Sperry]

double check the $HOME/.rhosts file and /etc/hosts.equiv files on the problem server.

[Ross Zubritski]

Sounds like the "alias" entry isn't in .rhosts.

Regards.

RZ

[Leslie Chaim]

Can I run "inted -l" without killing any current sessions?

[Sridhar Bhaskarla]

Yes. Just run "inetd -l". You do not need to kill the existing inetd.

-Sri

[Leslie Chaim]

Well, I am a bit frantic:(

This is a production box.

What will effect will it have on the current inted process?

How about any services which inted is currently running?

And, can I then restore to the default mode of inted (without logging)?

Thanks for your help so far!

[Sridhar Bhaskarla]

Hi,

inetd -l will not distrupt anything. You can safely run it anytime.

In order to revert it back, use inetd -c following by inetd -l again. It will disable connection logging. You should see both enabled|disabled messages in syslog.log

#inetd -c
#inet -l

-Sri

[Leslie Chaim]

Hi Sri,

I found the problem...

There was a typo in the /etc/hosts file when naming the aliases.