X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=NYw4
	lQ8cSgdWGG8FJpTLfV947SpLAUUPUtd6LDEok5H5XkxbQCutBOY1666yfJW/Js5t
	d4TAUzluRdvow865/Akj4mPi3Ml9Puf5D44wWxTmcpioi1cXsqudkq7SwhoVA9fw
	nd8lawE9W+o1yUFJHa5wYvE8ZaZVO2YP0GfYMmQ=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; s=default; bh=U5jxX6JMCd
	CkTTsegxQCvDlR0UU=; b=hB7/MGzicsJEa7Tn5wrL1+/7rIBy5ocQdx3Hy2l3nC
	Rlm6Te3TQNsdpj0wQyrEAnRrK4cKwFI7/aXCPVRr0uCesOnQGFC7KNLgJoWSEoGj
	13ZI4+rXd5UGRwL5xHhm+Qmep2SXax0IBI8VK7aJx06ZUb0wje85YfzRRTW85Akm
	4=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.6 required=5.0 tests=BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=H*f:sk:57ECA90, H*i:sk:57ECA90, H*MI:sk:57ECA90, joining
X-HELO:	mail-pa0-f51.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=AI4izzFITV5/4raVEIBvSTPykZl5lYzHOWMOil4DQYc=; b=VrRsyjqfSDpyqoCN2smvkLkgzSoy0d0rP69Dr/3I26jS1dMG8DffUOHHJXJyWEbGEf Uu0pJYmPTCF3y4LDRFqvwIwXG5RyY4HYlyfEOFIVY5lG8Y3aEK6PnGJExwUY1qpmzypY qbssS2w4kawClJjvrpJDHwYBPhmpZXB/I0IHtaUOmIymJmTG01yE8a1PxUrGDRP30/iO YxxjLSS0yTQNMrXH6SlYu+Z4X3lHD22/BHc3m9+Q9M78mII/527MAXrBHc++dKzEH4MQ Y+nbFgZE/6ZUaTjjRAm7nueEEwYpGH9wPRUW3j3m6qe8rOLGnIAHHBxNhjuyZp6QxQFT 0IkA==
X-Gm-Message-State:	AA6/9RkDWz2HNuCmI+8EHQoCeAt7yHflQzQEIBs7eHr3krEol3aB/GGVevnuqoD37wsNmw==
X-Received:	by 10.66.230.228 with SMTP id tb4mr4725362pac.99.1475174449454; Thu, 29 Sep 2016 11:40:49 -0700 (PDT)
Date:	Thu, 29 Sep 2016 11:40:40 -0700
From:	Wayne Porter <wporter82 AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Unknown+User Unix_Group+505 on smb shares in a domian
Message-ID:	<20160929184039.GD12532@hdmetxxxx33004g.AD.UCSD.EDU>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<57EB4449 DOT 7010206 AT tlinx DOT org> <20160928180456 DOT GA1128 AT hdmetxxxx33004g DOT AD DOT UCSD DOT EDU> <57ECA908 DOT 9010402 AT tlinx DOT org>
MIME-Version:	1.0
In-Reply-To:	<57ECA908.9010402@tlinx.org>
User-Agent:	Mutt/1.7.0 (2016-08-17)
X-IsSubscribed:	yes

--NklN7DEeGtkPCoo3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 28, 2016 at 10:39:20PM -0700, Linda Walsh wrote:
> Wayne Porter wrote:
> > The server that the W: drive is mapped on is not using domain accounts.=
 As far as I know,
> > all Linux servers we have are running local accounts. Is there somethin=
g I can set in
> > my local /etc/passwd to convince Cygwin to map it to my user account?
> ---
> 	If the linux servers are not exporting files under the domain account,
> then they files are not part of the 'domain' but owned only by the userna=
me
> on that specific linux-machine.  It sorta sounds like the linux server may
> not even be in the domain -- in which case mentioning domains only confus=
es
> the issue.

The reason I bring up domains is that I thought the solution might be close=
 to
what was being discussed in the following thread:
https://cygwin.com/ml/cygwin/2015-04/msg00506.html

It seems that setting the comment in the user account to the uid that the l=
inux
machine has would possibly help, but I can't do that since it's not a local
account.

>=20
> 	Essentially you have a bunch of users on different machines that aren't
> sharing their files under any common (or shared) security authority
> (like a single domain).  Until you persuade the owners of those linux mac=
hines
> to move the linux machines under a common security authority (like a wind=
ows
> domain) and moving the user accounts into the domain.  Each local account
> would have to be moved to a domain account with the files under each
> machine-local account being moved (or "chown'ed") to the new, correspondi=
ng
> domain account).

The shares are mapped and working just fine in Windows. To IT, there isn't
anything that needs to be done. It just happens that Cygwin, which I'm the =
only
one using, maps the Windows mapped drives to an unknown user account and ma=
kes
using it difficult.

>=20
> 	This is an organizational problem that has nothing to do with
> cygwin, but whether windows and linux machines are using domain or machin=
e-local
> security.  Until your linux machines and their local user become part of =
the
> domain, you can't expect any "write" privileges granted to you under the
> domain to work on the linux machines.
>=20

I have write permissions on those machines from Windows. Cygwin thinks I do=
n't so
files are opened in read-only mode but when I force them to be written, it =
works.
I'm not sure if maybe I left this out of my initial information, but these =
are
shares that are mapped in Windows on login and there are no issues there, b=
ut once
I open Cygwin, I don't appear to have write access even though I do.

When mapping the drives in Windows, a username and password are given. Is t=
here no
way to let Cygwin know about that username without joining the servers to t=
he domain?
I know that this setup isn't ideal, which is why I'm trying to find a work-=
around.


Wayne

--NklN7DEeGtkPCoo3
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBAgAGBQJX7WAnAAoJEMcDZgYHTWDO4OAH+wVO84VgoIjeo6/7rUd4baHC
npTmIv8v31dZpuBccvF7yBS/j4QwWS1baaHTfWcUvv127J+ybLI5y37BESyDURXl
QPDPt4jG6mbJMTnNV+3AS1Ht8LTj/5VX2xdNxdvSDeyNXx8eYRCogelAzV4ASgRf
IRLza9ZZ7Qvd+RUUdSAKD9UUA/FtqSFcHcUFc8r0nDeX3kh9xmvD07FQRWHtgay0
8RNLWUlu6467c5CGjMLG9u9PhddPu8a5Bw4dwFMipx/xmmaoJQxZeaoUVfugiwrN
XdC2FHlRbFINzb58RvURgfUjkU+SHb0TOZWfhqQQ+N4P2/jeU+nuSW+4Te+7m8Q=
=DlXM
-----END PGP SIGNATURE-----

--NklN7DEeGtkPCoo3--

- Raw text -