Univention Bugzilla – Bug 30843
UCS memberservers in a Samba3 domain currently cannot find a server for password changes
Last modified: 2017-08-08 07:10:00 CEST
The same behaviour as in Bug 30839 can be found on a UCS memberserver in a Samba3 domain, where /etc/krb5.conf has "dns_lookup_kdc = true" and no kerberos/kdc is set. =============================================================================arequate@lagra:~$ ssh 10.200.8.23 -l user7 Password: You are required to change your password immediately (password aged) Current Kerberos password: Your password will expire at Thu Mar 14 01:00:00 2013 Password: Retype new password: Unable to reach any changepw server in realm ARUCS311I2.S3 ============================================================================= Adding the missing _kpasswd._tcp and _kpasswd._udp srv records fixes the problem: root@master20:~# /usr/share/univention-directory-manager-tools/univention-dnsedit arucs311i2.s3 add srv kpasswd tcp 0 100 464 master20.arucs311i2.s3.Adding SRV record "kpasswd tcp 0 100 464 master20.arucs311i2.s3." to zone arucs311i2.s3... done root@master20:~# /usr/share/univention-directory-manager-tools/univention-dnsedit arucs311i2.s3 add srv kpasswd udp 0 100 464 master20.arucs311i2.s3. Adding SRV record "kpasswd udp 0 100 464 master20.arucs311i2.s3." to zone arucs311i2.s3... done +++ This bug was initially created as a clone of Bug #30839 +++
We will not ship a UCS 3.1-2 release; the next UCS release will be UCS 3.2. As such, this bug is moved to the new target milestone.
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4. If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
This issue has been filed against UCS 3.1. UCS 3.1 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.