Hallo,
ich habe heute einen 10.0 Printserver mit Cups und Samba von 10.0 auf 10.2 ubgedatet. Neben diverssen anderen Nickeligkeiten ahbe ich im Moment folgendes Problem:
Samba startet nicht mehr wenn die Zeile
ldap admin dn = cn=system,dc=firma,dc=com
eingetragen ist.
Die Konfiguration hat unter 10.0 gestern noch einwandfrei funktioniert.
Hat jemand dazu einen Tip?
Durch systematische Tests habe ich genau diese Zeile als Ursache ausfindig machen können.
Danke für Tips
[global]
unix charset = LOCALE
workgroup = Tfirma
server string = %h server (Samba %v)
map to guest = Bad User
passdb backend = ldapsam:ldap://kenobi.top-lamp.com
enable privileges = Yes
username map = /etc/samba/smbusers
log level = 1
syslog = 0
log file = /var/log/samba/%m
max log size = 50
smb ports = 139
name resolve order = wins bcast hosts
time server = Yes
printcap name = CUPS
os level = 2
show add printer wizard = No
add user script = /usr/sbin/smbldap-useradd -m "%u"
delete user script = /usr/sbin/smbldap-userdel "%u"
add group script = /usr/sbin/smbldap-groupadd -p "%g"
delete group script = /usr/sbin/smbldap-groupdel "%g"
add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g"
delete user from group script = /usr/sbin/smbldap-groupmod -x "%u" "%g"
set primary group script = /usr/sbin/smbldap-usermod -g "%g" "%u"
add machine script = /usr/sbin/smbldap-useradd -w "%u"
logon script = scripts\logon.bat
logon path = \\%L\profiles\%U
logon drive = Z:
logon home = \\%L\%U\.9xprofile
domain logons = Yes
preferred master = Yes
wins support = Yes
ldap admin dn = cn=system,dc=firma,dc=com
ldap group suffix = ou=groups
ldap idmap suffix = ou=idmap
ldap machine suffix = ou=machines
ldap suffix = dc=top-lamp,dc=com
ldap user suffix = ou=people
idmap backend = ldap:ldap://system.firma.com
idmap uid = 10000-20000
idmap gid = 10000-20000
printer admin = ich
hosts allow = 192.168.3.
map acl inherit = Yes
include = /etc/samba/dhcp.conf
ich habe heute einen 10.0 Printserver mit Cups und Samba von 10.0 auf 10.2 ubgedatet. Neben diverssen anderen Nickeligkeiten ahbe ich im Moment folgendes Problem:
Samba startet nicht mehr wenn die Zeile
ldap admin dn = cn=system,dc=firma,dc=com
eingetragen ist.
Die Konfiguration hat unter 10.0 gestern noch einwandfrei funktioniert.
Hat jemand dazu einen Tip?
Durch systematische Tests habe ich genau diese Zeile als Ursache ausfindig machen können.
Danke für Tips
[global]
unix charset = LOCALE
workgroup = Tfirma
server string = %h server (Samba %v)
map to guest = Bad User
passdb backend = ldapsam:ldap://kenobi.top-lamp.com
enable privileges = Yes
username map = /etc/samba/smbusers
log level = 1
syslog = 0
log file = /var/log/samba/%m
max log size = 50
smb ports = 139
name resolve order = wins bcast hosts
time server = Yes
printcap name = CUPS
os level = 2
show add printer wizard = No
add user script = /usr/sbin/smbldap-useradd -m "%u"
delete user script = /usr/sbin/smbldap-userdel "%u"
add group script = /usr/sbin/smbldap-groupadd -p "%g"
delete group script = /usr/sbin/smbldap-groupdel "%g"
add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g"
delete user from group script = /usr/sbin/smbldap-groupmod -x "%u" "%g"
set primary group script = /usr/sbin/smbldap-usermod -g "%g" "%u"
add machine script = /usr/sbin/smbldap-useradd -w "%u"
logon script = scripts\logon.bat
logon path = \\%L\profiles\%U
logon drive = Z:
logon home = \\%L\%U\.9xprofile
domain logons = Yes
preferred master = Yes
wins support = Yes
ldap admin dn = cn=system,dc=firma,dc=com
ldap group suffix = ou=groups
ldap idmap suffix = ou=idmap
ldap machine suffix = ou=machines
ldap suffix = dc=top-lamp,dc=com
ldap user suffix = ou=people
idmap backend = ldap:ldap://system.firma.com
idmap uid = 10000-20000
idmap gid = 10000-20000
printer admin = ich
hosts allow = 192.168.3.
map acl inherit = Yes
include = /etc/samba/dhcp.conf