Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3DB9C013.CF6CF751@acm.org>
Date: Fri, 25 Oct 2002 15:05:07 -0700
From: David Rothenberger <daveroth AT acm DOT org>
X-Accept-Language: en
MIME-Version: 1.0
To: Andrew DeFaria <ADeFaria AT Salira DOT com>
CC: cygwin AT cygwin DOT com
Subject: Re: Problem with rsh
References: <3DB9AD4E DOT 10407 AT Salira DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Check your /etc/passwd file and make sure there is no entry in the
password field (the second field).  You want something like this:

someuser::11150:...

and not something like this:

someuser:unused_by_nt/2000/xp:11150:...

An easy way to check if this is the culprit is to try doing an
rlogin.  For me, this will ask me for a password and then succeed if
I have an entry in the password field.  If the password field is
empty, it succeeds without asking for a password.

Andrew DeFaria wrote:
> 
> I've run into a major problem using rsh. Note that I've been using rsh
> successfully for a while and many people here depend on being able to
> rsh into the server. However now I get:
> 
> $ rsh server id
> server.mydomain.com: Permission denied.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/