Hide Forgot
Marko saw this on an AD domain: otherwise looking very good but please see the attachment - I noticed three "issues", can't remember any more are these something we found out already: - ! Couldn't lookup domain short name: 0000208D: NameErr: DSID-0310020A, problem 2001 (NO_OBJECT), data 0, best match of: 'DC=YYYYY,DC=zzzzz,DC=com' ... domain-short = (null) Perhaps an option to allow specifying that might help - OTOH not sure why YYYYY is not used if lookup fails? Version-Release number of selected component (if applicable): adcli 0.4
(In reply to comment #0) > Marko saw this on an AD domain: > > otherwise looking very good but please see the attachment - I noticed > three "issues", can't remember any more are these something we found out > already: > > - ! Couldn't lookup domain short name: 0000208D: NameErr: > DSID-0310020A, problem 2001 (NO_OBJECT), data 0, best match of: > 'DC=YYYYY,DC=zzzzz,DC=com' > ... > domain-short = (null) > > Perhaps an option to allow specifying that might help - OTOH not sure > why YYYYY is not used if lookup fails? Marko could you look for nETBIOSName attributes in your domain and note the domain AD windows version and domain controller version (either here or in an email?). Both in the CN=Configuration DSE and the root DSE. You might do something like this: $ ldapsearch -H ldap://dc.zzzz.com -Y GSSAPI -b 'CN=Configuration,DC=YYYYY,DC=zzzzz,DC=com' '(nETBIOSName=*)' nETBIOSName $ ldapsearch -H ldap://dc.zzzz.com -Y GSSAPI -b 'DC=YYYYY,DC=zzzzz,DC=com' '(nETBIOSName=*)' nETBIOSName Thanks.
This is in 2008 R2 domain. It turns out that nETBIOSName can be retrieved by using configurationNamingContext from rootDSE: ldapsearch -H ldap://dc.example.com -Y GSSAPI -b '' -s base 'objectclass=*' configurationNamingContext ldapsearch -H ldap://dc.example.com -Y GSSAPI -b 'CN=Partitions,<configurationNamingContext>' '(&(objectClass=crossRef)(dnsRoot=example.com)(nETBIOSName=*))' nETBIOSName Thanks.
adcli-0.5-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/adcli-0.5-1.fc19
Package adcli-0.5-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing adcli-0.5-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5301/adcli-0.5-1.fc19 then log in and leave karma (feedback).
adcli-0.5-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/adcli-0.5-2.fc19
adcli-0.5-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.