[Samba] NSLCD works, do I need RFC2307 extensions enabled in AD as well?
rowlandpenny at googlemail.com
Mon Apr 20 14:17:30 MDT 2015
On 20/04/15 20:50, john wrote:
> Hi Rowland,
> On Mon, Apr 20, 2015 at 10:29 AM, Rowland Penny <rowlandpenny at googlemail.com
>> OK, I understand a bit better where your problems lie. I would still use
>> backports, supported code is (hopefully) better code :-)
> I am certainly willing to do that.
>>> I'd be willing to do that if it got me support for UPN names (see below)
>>> I installed NSLCD to allow users in AD to authenticate against
>>> my linux
>>> server per
>>> Why use nlscd ? why not use winbind, see:
>>> My impression from this thread
>>> is that Winbind doesn't support UPN names. This was my lame-brain
>>> attempt to "work around" that issue.
>> I use winbind and using the UPN seems to work for smbclient:
>> smbclient \\\\xp.example.com\\shared -Urowland at example.com
>> Enter rowland at example.com's password:
>> Domain=[EXAMPLE] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
>> smb: \>
>> Is this the way you mean ?
> Well that appears to be what I want, but that doesn't work in my case. Can
> I see the smb.conf file? As I mentioned my PDC is a Windows box and this
> Samba server is a member server. I am trying to keep this as simple as
> Since I am able to see UID/GID information via the method outlined on the
> Samba wiki
> it seems like the missing part is getting winbind to use that information.
> Can you guide me on the proper approach?
OK, have a look here:
That is basically my smb.conf (and when I say 'my' I really mean that is
More information about the samba