Displaying 20 results from an estimated 30000 matches similar to: "RFC2307, AD, and Samba 3.6"
2012 Jul 14
2
Failing to get uids from AD
Hi,
I'm still having trouble getting Samba 3.6.3 / Winbind to fetch UIDs from AD 2008 R2 with the Services for Unix feature installed. My users have uidNumber fields which contain the UIDs I want. I'm on Ubuntu 12.04
The global part of my smb.conf. I've tried changing 'winbind nss info' and 'schema_mode' to sfu as well.
security = ADS
realm = CORP.mycompany.COM
2012 Jul 10
2
Can't get idmap connected to AD unix attribs
Hi,
I'm trying to get an Ubuntu 12.04 system's Samba (3.6.3) and Winbind to map userids and groups to the unix attributes in an AD 2008 server. I can see that when I perform an ldapsearch, I'm able to read the attributes, and for one of my accounts, the id should be 1001. However, when I run 'wbinfo -i <username>', I get back something like 920.
At one point, I was
2009 Mar 07
1
idmap_ad not returning correct UID under 3.3.1
I'm testing winbind 3.3.1-1ubuntu1 (jaunty) and my user stored in AD
is consistently being returned with a UID of 1000, rather than 10031,
which is whats stored in LDAP/AD under uidNumber. If I install the
3.2.3-1ubuntu3.4 packages from intrepid, 'id bryanm' correctly returns
10031, but when upgrading back to 3.3.1-1ubuntu1, I get the wrong UID
again. I did an install from source as
2016 Dec 08
2
winbind rfc2307 - wbinfo -i fails
I'm trying to get Samba 4 AD to work with rfc2307 extensions.
wbinfo -i fails
root at m1:~# wbinfo -i SAMDOM\\demo01
failed to call wbcGetpwnam: WBC_ERR_DOMAIN_NOT_FOUND
winbindd.log it here: http://pastebin.com/X0rEaLt2
Pretty much everything else seems to work:
root at m1:~# wbinfo --ping-dc
checking the NETLOGON for domain[SAMDOM] dc connection to "dc1.samdom.example.com"
2016 Dec 08
4
winbind rfc2307 - wbinfo -i fails
Am 08.12.2016 um 13:55 schrieb Rowland Penny via samba:
> On Thu, 8 Dec 2016 12:52:53 +0100
> Oliver Heinz via samba <samba at lists.samba.org> wrote:
>
>> I'm trying to get Samba 4 AD to work with rfc2307 extensions.
>>
>> wbinfo -i fails
>>
>> root at m1:~# wbinfo -i SAMDOM\\demo01
>>
>> failed to call wbcGetpwnam:
2019 Apr 15
2
winbind offline login - NT_STATUS_NO_SUCH_USER (0xc0000064)
Hello All,
I am at the switch from sssd to winbind based samba domain members (Debian
9 stretch).
I am using Samba 4.10.2 packages from Louis ( http://apt.van-belle.nl/ )
and rid backend for idmap.
*My problem:*
I am able to logon to my domain members using winbind_pam as long as my
client is connected to a network where a domain controller is reachable.
As soon as I shutdown and connect a
2015 Jun 11
4
idmap & migration to rfc2307
Yup, strange - right!
Samba 4.2.2
RFC2307 attributes were added as follows:
# sed -e 's/${DOMAINDN}/dc=MYDOMAIN,dc=MY,dc=TLD/g' \
-e 's/${NETBIOSNAME}/MYDOMAIN/g' \
-e 's/${NISDOMAIN}/MYDOMAIN/g' \
/usr/local/samba/share/setup/ypServ30.ldif > ypServ30-JMH.ldif
# service samba4 stop
# ldbmodify -H
2014 Dec 01
5
uidNumber. ( Was: What is --rfc2307-from-nss ??)
On Mon, Dec 1, 2014 at 1:33 AM, Rowland Penny <rowlandpenny at googlemail.com>
wrote:
>
>> I do what windows does, it ignores the RID (what you call 'the last set
> of digits from SID') and uses a builtin mechanism to store the next uid &
> gidNumber.
The builtin users/groups use the RID for the GID/UID.
If you create a user and then goto to the
2016 Dec 08
2
winbind rfc2307 - wbinfo -i fails
On Thu, 8 Dec 2016 14:44:16 +0100
Oliver Heinz via samba <samba at lists.samba.org> wrote:
>
>
> Am 08.12.2016 um 14:31 schrieb Oliver Heinz:
> >
> >
> > Am 08.12.2016 um 13:55 schrieb Rowland Penny via samba:
> >> On Thu, 8 Dec 2016 12:52:53 +0100
> >> Oliver Heinz via samba <samba at lists.samba.org> wrote:
> >>
>
2016 Mar 24
2
Winbind doesn't honor rfc2307 data set in AD (Samba 4.3.6 on Debian jessie)
Hi all, I've just installed Samba 4.3.6 on Debian jessie amd64 (as
described in the wiki [1]) and everything seems to work properly
except for rfc2307 data that winbind doesn't retrieve from AD backend,
shell is always "/bin/false", homedir is always
"/home/DOMAIN/username" and "getent passwd" also lists user without
unix attributes.
I have configured idmap_ad
2015 Apr 23
3
RFC2307 attributes not being read by DC2 in 4.2.1
Hi all
On latest samba 4.2.1 I have provisioned a new domain on DC1 that
successfully reads RFC2307 attributes set on a user account through
ADUC.
wbinfo (correct uid gets resolved from sid)
wbinfo -n fsmith
S-1-5-21-1273750850-484487853-1026460749-1120 SID_USER (1)
wbinfo -S S-1-5-21-1273750850-484487853-1026460749-1120
1000006
ldbsearch
sudo ldbsearch -H
2015 Dec 03
3
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
192.168.127.129 is the core DNS server. It forwards anything in the
windows subdomain straight to the DCs, so it doesn't matter if this client
is pointed at the DC or the main DNS server. Either way, it still does the
wrong behavior, which is use the short .WINDOWS instead of .
WINDOWS.CORP.XXX.COM
I removed all .tdb files, purged /var/cache/samba, removed /etc/krb5.tdb,
and deleted the
2014 Dec 01
3
uidNumber. ( Was: What is --rfc2307-from-nss ??)
Rowland,
How are you selecting you UID to store in the AD uidNumber attribute? I
initially thought UID could be pulled from the last set of digits from
SID, ut this does not appear to be what others are doing :(
What are you using determine the UID number???
Thanks
2015 Dec 03
4
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
jonathan.fisher at freeradius:~$ sudo net ads join -Uadministrator
Enter administrator's password:
Using short domain name -- WINDOWS
Joined 'FREERADIUS' to dns domain 'windows.corp.XXX.com'
jonathan.fisher at freeradius:~$ hostname
freeradius
jonathan.fisher at freeradius:~$ hostname -d
windows.corp.XXX.com
jonathan.fisher at freeradius:~$ hostname -f
2015 Jun 22
2
Samba 3 AD Member Server Strangeness
On , June 20, 2015 5:10 AM, Rowland Penny wrote:
>
> On 19/06/15 21:39, Brian.Huffman at dupont.com wrote:
> > All,
> >
> > I'm trying to configure a Samba 3 AD member server including winbind. I'm
> on RHEL 6.6, so I'm using Samba version 3.6.23.
> >
> > Here's my configuration:
> > [global]
> > log level = 3 winbind:10
2015 Apr 23
0
RFC2307 attributes not being read by DC2 in 4.2.1
On 23/04/15 02:48, Fred Smith wrote:
> Hi all
>
> On latest samba 4.2.1 I have provisioned a new domain on DC1 that
> successfully reads RFC2307 attributes set on a user account through
> ADUC.
>
> wbinfo (correct uid gets resolved from sid)
>
> wbinfo -n fsmith
> S-1-5-21-1273750850-484487853-1026460749-1120 SID_USER (1)
> wbinfo -S
2019 Apr 12
1
Joining Ubuntu Server to Domain - "kinit succeeded but ads_sasl_spnego_gensec_bind failed"
I'm currently attempting to join an Ubuntu server to an AD domain,
eventually with the intention of allowing Windows-based domain members to
access a Samba share using their AD credentials. (As specified in the Wiki
article "Setting Up Samba as a Domain Member." The DC is running on Windows
(not Samba) and has DHCP/DNS running on a separate Linux server (using
BIND). The DC
2015 Jun 19
2
Samba 3 AD Member Server Strangeness
All,
I'm trying to configure a Samba 3 AD member server including winbind. I'm on RHEL 6.6, so I'm using Samba version 3.6.23.
Here's my configuration:
[global]
log level = 3 winbind:10
workgroup = ABC
server string = LV37
netbios name = LV37
idmap config *:backend = tdb
idmap config *:range = 2000-9999
idmap config
2015 Jun 22
2
Samba 3 AD Member Server Strangeness
On Monday, June 22, 2015 9:15 AM ,Rowland Penny wrote:
> On 22/06/15 13:55, Brian.Huffman at dupont.com wrote:
> > On , June 20, 2015 5:10 AM, Rowland Penny wrote:
> >> On 19/06/15 21:39, Brian.Huffman at dupont.com wrote:
> >>> All,
> >>>
> >>> I'm trying to configure a Samba 3 AD member server including
> >>> winbind. I'm
2015 Jan 14
2
Domain Computer not showing up in domain utilities
> > I am running Samba Version 4.1.6.
> >
> > I have a PDC and two BDC setup.
> >
> > I have a specific computer named eds, it is a Windows 7 Pro box, When
> > I add it to the domain everything works normally and it works well.
> > Domain users can login, and they have the proper permissions, but am
> > seeing two problems.
> >
> > 1)