Die Kommunikation zwischen UCS und meinem Samba Server scheint nicht zufunktionieren, eingerichtet habe ich ihn nach der Dokumentation. Ich bin mir auch nicht ganz sicher was hier in diese Zeile muss: ldap idmap suffix = cn=idmap,cn=univention
Ich finde auch kein Eintrag wo man die SID für die SambaServer sehen könnte
Versuche ich mich von den Samba Server zum USC zuverbinden kommt folgende Meldung: Connecting to LDAP server …
… connection failed : Failed to bind to LDAP server 192.168.0.2 as cn=Administrator,dc=Shiva,dc=de : Invalid credentials
Muss bei cn Memberserver stehen oder ein eigener Angeleter Rechner im USC?
[global]
workgroup = Shiva
server string = %h server
netbios name = smb
wins server = 192.168.0.2
dns proxy = no
interfaces = 127.0.0.0/8 eth0
bind interfaces only = true
log file = /var/log/samba/log.%m
debug level = 9
max log size = 1000
syslog = 4
panic action = /usr/share/samba/panic-action %d
security = domain
#password server = ucs
encrypt passwords = true
#passdb backend = ldapsam:ldap://ucs.xyz.local
#auth methods = guest sam winbind
ldap suffix = dc=Shiva
ldap admin dn = cn=Administrator,dc=Shiva
ldap ssl = on
idmap backend = ldap:ldap://192.168.0.2
ldap idmap suffix = cn=idmap,cn=univention
idmap uid = 55000-64000
idmap gid = 55000-64000
winbind trusted domains only = yes
winbind nested groups = no
winbind enum users = yes
winbind enum groups = yes
winbind separator = +
#winbind use default domain = yes
#winbind enable local accounts = yes
template shell = /bin/bash
template homedir = /home/%D-%U
obey pam restrictions = yes
map to guest = Bad User
admin users = administrator
guest account = nobody
invalid users = root daemon bin sys sync games man lp mail news uucp
proxy majordom postgres www-data backup msql operator list irc gnats
alias qmaild qmails qmailr qmailq qmaill qmailp telnetd identd ftp rwhod
gdm fetchmail faxmaster
pam password change = no
domain logons = no
preferred master = no
local master = no
domain master = no
load printers = yes
printing = cups
printcap name = cups
printer admin = @ntadmin, @"Printer-Admins", root, Administrator
socket options = TCP_NODELAY
os level = 65
oplocks = yes
kernel oplocks = yes
large readwrite = yes
deadtime = 15
read raw = yes
write raw = yes
max xmit = 65535
getwd cache = yes
store dos attributes = yes
preserve case = yes
short preserve case = yes
time server = yes
host msdfs = no
msdfs root = no
use spnego = yes
client use spnego = yes
[share]
comment = TestShare
path = /home/Test
read only = No
force create mode = 0770
force directory mode = 0770Die .conf von Kerberos funtkioniert auch nicht wie im .pdf beschrieben: verify_krb5_conf: krb5_init_context failed to parse configuration file
[code][libdefaults]
default_realm = Shiva
clockskew = 300
v4_instance_resolve = false
v4_name_convert = {
host = {
rcmd = host
ftp = ftp
}
plain = {
something = something - else
}
}
Set this to false to disable MIT krb5 compatibility
in GSSAPI get_mic / verify_mic , and become compatible
with older Heimdal releases instead .
gss_mit_compat = true
[realms]
Shiva = {
kdc = Shiva
}
OTHER . REALM = {
v4_instance_convert = {
kerberos = kerberos
computer = computer . some . other . domain
}
}
[domain_realm]
.my. domain = Shiva
#auth sufficient pam_krb5.so forwardable ccache=/tmp/krb5_%u
[/code]
root@ubuntu:~# apt-get install pam-krb5 Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut Reading state information… Fertig E: Konnte Paket pam-krb5 nicht finden
root@ubuntu:~# kpasswd kpasswd: krb5_init_context failed: -1765328248