X-Spam-Check-By: sourceware.org
Message-ID: <599515fa0607251506t38ecf38aga64d95f8db8c3ea6@mail.gmail.com>
Date: Tue, 25 Jul 2006 17:06:37 -0500
From: MyStiC <mystic DOT master AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: MS Windows 2k3 domain users issue
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

>From: "Larry Hall (Cygwin)"
>It's not clear whether your '/etc/groups' file is up-to-date on your XP
>machine.  Try running 'mkgroup -l -d >/etc/group'.  If you have trouble

XP machine is at my office and the w2k3 server is at my residence.
The 'etc/group' file on the XP box was build local to the machine and
the domain it is connected to as well as the password file.  According
to the documentation I've seen on this, the client side (connecting
from) 'group & passwd' files do not 'participate' in the
authentication to the server.  That the 'server side' is unable to
properly validate the incoming client credentials against the 'server
side' '/etc/group & /etc/passwd' files.

>doing this, check if you need to specify your domain as well.

Example of SSH connection process:
SSH ssh_server_domain_name -l username

adding the @ and domain behind the username also does not work.
Administrators have no problem connecting, but no other users can.
-MyStiC

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/