Install and run again
[code][root@sbs ~]# account-provider-test
extended LDIF
LDAPv3
base <dc=compu-max,dc=lan> with scope baseObject
filter: (objectClass=*)
requesting: ALL
compu-max.lan
dn: DC=compu-max,DC=lan
objectClass: top
objectClass: domain
objectClass: domainDNS
instanceType: 5
whenCreated: 20161021112432.0Z
uSNCreated: 8
name: compu-max
objectGUID:: 0Tg8os3xUkaL7V4KuMx8nQ==
objectSid:: AQQAAAAAAAUVAAAArgoFLfMkPOX9n/6b
objectCategory: CN=Domain-DNS,CN=Schema,CN=Configuration,DC=compu-max,DC=lan
dc: compu-max
auditingPolicy:: AAE=
creationTime: 131215226720000000
forceLogoff: -9223372036854775808
gPLink: [LDAP://CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=Syste
m,DC=compu-max,DC=lan;0]
isCriticalSystemObject: TRUE
lockoutDuration: -18000000000
lockOutObservationWindow: -18000000000
lockoutThreshold: 0
minPwdLength: 7
modifiedCount: 1
modifiedCountAtLastProm: 0
msDS-AllUsersTrustQuota: 1000
msDS-Behavior-Version: 4
ms-DS-MachineAccountQuota: 10
msDS-NcType: 0
msDS-PerUserTrustQuota: 1
msDS-PerUserTrustTombstonesQuota: 10
nextRid: 1000
nTMixedDomain: 0
oEMInformation: Provisioned by SAMBA 4.4.5
pwdProperties: 1
pwdHistoryLength: 24
serverState: 1
systemFlags: -1946157056
uASCompat: 1
rIDManagerReference: CN=RID Manager$,CN=System,DC=compu-max,DC=lan
wellKnownObjects: B:32:6227F0AF1FC2410D8E3BB10615BB5B0F:CN=NTDS Quotas,DC=comp
u-max,DC=lan
wellKnownObjects: B:32:F4BE92A4C777485E878E9421D53087DB:CN=Microsoft,CN=Progra
m Data,DC=compu-max,DC=lan
wellKnownObjects: B:32:09460C08AE1E4A4EA0F64AEE7DAA1E5A:CN=Program Data,DC=com
pu-max,DC=lan
wellKnownObjects: B:32:22B70C67D56E4EFB91E9300FCA3DC1AA:CN=ForeignSecurityPrin
cipals,DC=compu-max,DC=lan
wellKnownObjects: B:32:18E2EA80684F11D2B9AA00C04F79F805:CN=Deleted Objects,DC=
compu-max,DC=lan
wellKnownObjects: B:32:2FBAC1870ADE11D297C400C04FD8D5CD:CN=Infrastructure,DC=c
ompu-max,DC=lan
wellKnownObjects: B:32:AB8153B7768811D1ADED00C04FD8D5CD:CN=LostAndFound,DC=com
pu-max,DC=lan
wellKnownObjects: B:32:AB1D30F3768811D1ADED00C04FD8D5CD:CN=System,DC=compu-max
,DC=lan
wellKnownObjects: B:32:A361B2FFFFD211D1AA4B00C04FD7D83A:OU=Domain Controllers,
DC=compu-max,DC=lan
wellKnownObjects: B:32:AA312825768811D1ADED00C04FD8D5CD:CN=Computers,DC=compu-
max,DC=lan
wellKnownObjects: B:32:A9D1CA15768811D1ADED00C04FD8D5CD:CN=Users,DC=compu-max,
DC=lan
fSMORoleOwner: CN=NTDS Settings,CN=NSDC-SBS,CN=Servers,CN=Default-First-Site-N
ame,CN=Sites,CN=Configuration,DC=compu-max,DC=lan
msDs-masteredBy: CN=NTDS Settings,CN=NSDC-SBS,CN=Servers,CN=Default-First-Site
-Name,CN=Sites,CN=Configuration,DC=compu-max,DC=lan
msDS-IsDomainFor: CN=NTDS Settings,CN=NSDC-SBS,CN=Servers,CN=Default-First-Sit
e-Name,CN=Sites,CN=Configuration,DC=compu-max,DC=lan
masteredBy: CN=NTDS Settings,CN=NSDC-SBS,CN=Servers,CN=Default-First-Site-Name
,CN=Sites,CN=Configuration,DC=compu-max,DC=lan
minPwdAge: 0
maxPwdAge: -9223372036854775808
whenChanged: 20161021112639.0Z
uSNChanged: 3732
distinguishedName: DC=compu-max,DC=lan
search result
search: 2
result: 0 Success
numResponses: 2
numEntries: 1
[root@sbs ~]# account-provider-test dump
{
“startTls” : “”,
“bindUser” : “SBS$”,
“userDN” : “dc=compu-max,dc=lan”,
“port” : 636,
“isAD” : “1”,
“host” : “compu-max.lan”,
“groupDN” : “dc=compu-max,dc=lan”,
“isLdap” : “”,
“ldapURI” : “ldaps://compu-max.lan”,
“baseDN” : “dc=compu-max,dc=lan”,
“bindPassword” : “jBVl16OKR80OcZ”,
“bindDN” : “COMPU-MAX\SBS$”[/code]
nothing changed.
Some other commands, just trying to understand where is the problem:
id admin
id administrator
net ads info
net ads testjoin
/usr/libexec/nethserver/list-users
net ads search -P samaccountname=administrator
Then
kinit administrator@compu-max.lan
everything get ok´s without an error but the kinit respond:
KDC reply did not match expectations while getting initial credentials
this really makes me upset. it is the third time i only install the updates what comes with the softwarecenter and after it something is broken
Don’t be upset, we’ll find a solution. Let’s see
cat /etc/resolv.conf
It could be mangled… Then try fix
signal-event nethserver-dnsmasq-save
And kinit again
also everything ok with cat /etc/resolv.conf
after kinit same problem
KDC reply did not match expectations while getting initial credentials
Do you confirn nameserver is 127.0.0.1?
yes it is
# dnsmasq is enabled on this machine:
nameserver 127.0.0.1
is it possible to update everything again what comes today?
its really bad, not possible to get it back working. the only thing what i do is making the updates from softwarecenter and this now 3 times and 3 times system is crashed. this never happen with zentyal i must say.
What does it mean? I thought it was password authentication… What service fails? Please describe the problem from the user’s point of view.
I still don’t catch what’s wrong in your setup:
- nsdc is running
- users are listed in server manager
- sssd is running and resolves account names
- DNS seems OK
kinit fails, and could be a symptom of misconfiguration compatible with password auth failure, but sssd actually uses kerberos and seems to work… Something does not match!
Any error in /var/log/secure?
Could you attach the complete list of packages?
rpm -qa
And verification
rpm -Va
Also
sss_cache -U -G
id administrator
Please past the entire output.
Nobody still reported issues like this. That does not mean the issue is not present. Its condition is hard to reproduce. I hope you understand.
i really have no idea but also the setup from the new release dont work very well. i was not able to save the network configuration during the installation and so not possible to use the webui. now i setup the rc3 again and try to get my data back after installation.
no one? like this?
Hello Kai!
I know it’s stupid when something does not work, but you (we) must also be clear that it is a preliminary development version.
If you want to have a fully functional you have to use the 6.8er.
And the boys and girls here work with high pressure on a solution of the many problems, partly small parts partly really big.
Until now they have done everything!
Give them some time!
sure, i really appreciate what they do and don´t complain. i guess its because i have this situation now 3 times and every time after i do updates from the softwarecenter. but anyway, it is part of the deal, i know that an be thankful for this great project.
SOGo? We were completely out of track here! Sorry but I didn’t catch it… Thanks to @gerald_FS for starting that new topic.
Thanks for pointing out that, we have always bear in mind that!
@hucky I hear you and I understand your frustration but I have to highlight that @davidep have answered your issues during his day off, stealing some time to the family.
Please, shoutout this man!
A recap on this support request. There were multiple problems here with different solutions. I hope @hucky has found a workaround for each them.
I want to link here two of them that were recognized as bugs: