I'm confused, ... domain vs. local account mappings (why diffs, how to control mappings?)
Fri Jul 22 04:39:00 GMT 2011
For various reasons (config changes, upgrading to newer
version of samba, phase of the moon, dumb-luck/random
chance, after a latest round of samba-setup config
auditing (amongst other things),
I'm no longer getting "device attached to sys not functioning"
(originally reported http://cygwin.com/ml/cygwin/2010-07/msg00289.html)
Now I get output that I'm not exactly sure how to interpret.
--- first local, which by itself seems almost normal):
(I split long lines and indented the continuations, also sub'ed
the long sys-uniq# with 11111-22222-11111 for my local sys.
I use a different ## for my domain further on, down, below.
(I also sorted them by UID)
# mkpasswd -l:
law:unused:1001:513:L A Walsh,U-athenae\law,\
# mkgroup -l
Remote Desktop Users:S-1-5-32-555:555:
Network Configuration Operators:S-1-5-32-556:556:
Performance Monitor Users:S-1-5-32-558:558:
Performance Log Users:S-1-5-32-559:559:
Distributed COM Users:S-1-5-32-562:562:
Event Log Readers:S-1-5-32-573:573:
so above looks ok, -- several builtin entries, and some
added local entries.
Now the Domain entries:
# mkpasswd -D:
BLISS\law:unused:90026:71008:L A Walsh,U-BLISS\law,\
BLISS\Trusted Local Net Users:S-1-5-21-33333-77777-33333-50002:60002:
1) local user 'law', 'root' and 'guest' are all in '513'
Sid "S-1-5-21----513" is a "well known sid" for 'Domain Users'
(why it shows up as a group labeled 'non' with my local
computers id in the computer part, is confusing.
2) 'law' is in 'lawgroup' (one good thing!)
But Domain user 'root' is in group 10513, which is sorta 'broken'
like the local users mapping to 513. It probably should have
mapped to '10512'?
3) Why 2 Backup Operators? -- Backup Operators mapping
correctly from Sid S---551->551.
but 'builtin\backup operators, (also 512, mapping to a different
domain-mapped UID on the local machine).
I do have Domain Admins, -512, but they aren't being mapped
to the correct local GID of '512'...
Same goes for 'Domain Controllers' (516->10516)
Or design (I hope?, but how to fix the broken parts?)
Note there is a larger overlap of unprefixed groups from
the local and domain listing. None conflict if they were
merged with dups removed, but some are in the Domain
listing, while others are only in the local listing.
So -- I take it the low-numbered groups are not prefixed because
the somehow have a "WELL KNOWN SID" property attached to them?
Hoping/presuming that's the case, how can I map the
3 domain groups:
'Domains Admins' (i.e. 10512 -> 512)
'Domain Controllers' (10516 -> 516)
builtin/backup operators -> backup operators
(i.e. did I miss setting some 'built-in' flag somewhere?)
or, how do I prevent cygwin from adding anything to the
UID's, that way, I can have the same mapping from the DC?
(as the DC, running samba, has already done a block-jump
mapping of UID's into a higher level)....
Guess that's the main Q how to have cygwin not add to the
UID's -- that way Domain Administrator would map to Administrator,
which is also 'correct' for Admins on Domain joined machines
(IF memory serves me correctly, I could see that making sense
as well -- as in a domain, as domain policy can lockdown/control
member machines, it could also disable local admin accounts if that
In my situation would there be any great risk in removing that offset,
since it seems to be preventing some logins/groups from
properly mapping, within cygwin they way they should....
Certainly, would like to get my 'Bliss\law acct to have the same
UID as what is seen on my network shares...would make life
so much more integrous**....
** -- a word in need or more usage!
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin