search for: supportedcapabilities

Hello，I'm using samba ad dc about a year. I have 2 DCs, One is DC1 with FSMO role. And another is DC2. there's a error in DC1 when i use dbcheck tool. And samba-tool dbcheck --cross-ncs--fix can't fix that. And I made a big mistake ! In DC2 I use "tdbbackup -s .bak /var/lib/samba/private/sam.ldb" create a bak file. and using that bak file replace the sam.ldb

...faultNamingContext: DC=addom,DC=samba,DC=example,DC=com rootDomainNamingContext: DC=addom,DC=samba,DC=example,DC=com schemaNamingContext: CN=Schema,CN=Configuration,DC=addom,DC=samba,DC=example,D  C=com subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=addom,DC=samba,D  C=example,DC=com supportedCapabilities: 1.2.840.113556.1.4.800 supportedCapabilities: 1.2.840.113556.1.4.1670 supportedCapabilities: 1.2.840.113556.1.4.1791 supportedCapabilities: 1.2.840.113556.1.4.1935 supportedCapabilities: 1.2.840.113556.1.4.2080 supportedLDAPVersion: 2 supportedLDAPVersion: 3 vendorName: Samba Team (https://www.sam...

...faultNamingContext: DC=addom,DC=samba,DC=example,DC=com rootDomainNamingContext: DC=addom,DC=samba,DC=example,DC=com schemaNamingContext: CN=Schema,CN=Configuration,DC=addom,DC=samba,DC=example,D C=com subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=addom,DC=samba,D C=example,DC=com supportedCapabilities: 1.2.840.113556.1.4.800 supportedCapabilities: 1.2.840.113556.1.4.1670 supportedCapabilities: 1.2.840.113556.1.4.1791 supportedCapabilities: 1.2.840.113556.1.4.1935 supportedCapabilities: 1.2.840.113556.1.4.2080 supportedLDAPVersion: 2 supportedLDAPVersion: 3 vendorName: Samba Team (https://www.sam...

Hey Folks, I will teach a mini course on LDAP next week and I'm with the following question: Is There any documentation that give some details about what LDAP Controls and Extensions are provided by the Samba 4 Implementation? Thanks in advance.

Hi All, I am having a problem with SMB4 ADDC. I cannot join the AD from Fedora. I have done a wireshark capture and found that it does 2 LDAP search requests when doing a discovery. The 1st query was a search for the defaultNamingContext and supportedCapabilities attributes. This got a successful search response packet and a result of 1. the 2nd query was a search for the NetLogon attribute. This also got a successful search response packet but it had a result of 0 so no attribute details. I am currently using RealmD to join and get: ! Received invalid o...

...x ? objectclass0? + subschemaSubentry dsServiceName namingContexts defaultNamingContext schemaNamingContext configurationNamingContext rootDomainNamingContext supportedControl supportedLDAPVersion supportedLDAPPolicies supportedSASLMechanisms dnsHostName ldapServiceName serverName supportedCapabilities //server ->client 0? t d? m 0? g0' namingContexts1 dc=arc-aachen,dc=de0?? supportedControl1?? 2.16.840.1.113730.3.4.18 2.16.840.1.113730.3.4.2 1.3.6.1.4.1.4203.1.10.1 1.2.840.113556.1.4.319 1.2.826.0.1.3344810.2.3 1.3.6.1.1.13.2 1.3.6.1.1.13.1 1.3.6.1.1.120 supportedLDAPVer...

...attrs: [supportedControl] SearchRequest: attrs: [supportedLDAPVersion] SearchRequest: attrs: [supportedLDAPPolicies] SearchRequest: attrs: [supportedSASLMechanisms] SearchRequest: attrs: [dnsHostName] SearchRequest: attrs: [ldapServiceName] SearchRequest: attrs: [serverName] SearchRequest: attrs: [supportedCapabilities] ldb_request BASE dn= filter=(objectclass=*) SearchRequest: results: [1] Received cldap packet of length 156 from 10.0.0.2:55999 cldap netlogon query domain=NVIZN.COM host=FRODO user=(null) version=536870934 guid=0020fc69-5a37-46af-8279-7462bed3d8e9 added interface ip=10.0.0.1 nmask=255.255.255.0...