danielmader
08-28-2007, 01:31 PM
Hallo,
wir betreiben einen Arbeitsgruppenserver auf Basis des SLES 10 SP1.
Folgende Pakete sind installiert:
samba-doc-3.0.24-2.23
kdebase3-samba-3.5.1-69.52
yast2-samba-server-2.13.22-0.8
samba-client-3.0.24-2.28
samba-winbind-3.0.24-2.28
yast2-samba-client-2.13.36-0.8
samba-pdb-3.0.24-2.28
samba-3.0.24-2.28
Der Server funktioniert soweit, leider haben wir aber noch ein
Konfigurationsproblem, was uns volle Logfiles und Messages beschert:
************************************************** *******************
Auszug aus log.nmbd:
[2007/08/28 13:03:34, 0]
nmbd/nmbd_browsesync.c:get_domain_master_name_node_stat us_fail(486)
get_domain_master_name_node_status_fail:
Doing a node status request to the domain master browser at IP
192.168.173.252 failed.
Cannot get workgroup name.
[2007/08/28 13:18:28, 0]
nmbd/nmbd_browsesync.c:get_domain_master_name_node_stat us_fail(486)
get_domain_master_name_node_status_fail:
Doing a node status request to the domain master browser at IP
192.168.173.253 failed.
Cannot get workgroup name.
[2007/08/28 13:18:28, 0]
nmbd/nmbd_browsesync.c:get_domain_master_name_node_stat us_fail(486)
get_domain_master_name_node_status_fail:
Doing a node status request to the domain master browser at IP
192.168.173.252 failed.
Cannot get workgroup name.
[2007/08/28 13:33:40, 0]
nmbd/nmbd_browsesync.c:get_domain_master_name_node_stat us_fail(486)
get_domain_master_name_node_status_fail:
Doing a node status request to the domain master browser at IP
192.168.173.253 failed.
Cannot get workgroup name.
[2007/08/28 13:33:40, 0]
nmbd/nmbd_browsesync.c:get_domain_master_name_node_stat us_fail(486)
get_domain_master_name_node_status_fail:
Doing a node status request to the domain master browser at IP
192.168.173.252 failed.
Cannot get workgroup name.
[2007/08/28 13:48:30, 0]
nmbd/nmbd_browsesync.c:get_domain_master_name_node_stat us_fail(486)
get_domain_master_name_node_status_fail:
Doing a node status request to the domain master browser at IP
192.168.173.253 failed.
Cannot get workgroup name.
[2007/08/28 13:48:30, 0]
nmbd/nmbd_browsesync.c:get_domain_master_name_node_stat us_fail(486)
get_domain_master_name_node_status_fail:
Doing a node status request to the domain master browser at IP
192.168.173.252 failed.
Cannot get workgroup name.
************************************************** *******************
************************************************** *******************
Auszug aus log.smbd:
[2007/08/28 12:40:57, 0] lib/fault.c:fault_report(41)
================================================== =============
[2007/08/28 12:40:57, 0] lib/fault.c:fault_report(42)
INTERNAL ERROR: Signal 6 in pid 8871 (3.0.24-2.28-1354-SUSE-CODE10)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2007/08/28 12:40:57, 0] lib/fault.c:fault_report(44)
From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2007/08/28 12:40:57, 0] lib/fault.c:fault_report(45)
================================================== =============
[2007/08/28 12:40:57, 0] lib/util.c:smb_panic(1599)
PANIC (pid 8871): internal error
[2007/08/28 12:40:57, 0] lib/util.c:log_stack_trace(1706)
BACKTRACE: 24 stack frames:
#0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x8021861d]
#1 /usr/sbin/smbd(smb_panic+0x5d) [0x8021874d]
#2 /usr/sbin/smbd [0x8020418a]
#3 [0xffffe420]
#4 /lib/libc.so.6(abort+0x103) [0xb7bd9ff3]
#5 /usr/sbin/smbd [0x8021e986]
#6 /usr/sbin/smbd(talloc_steal+0x3a) [0x8021eb5a]
#7 /usr/sbin/smbd(lookup_sids+0x39a) [0x801d56ca]
#8 /usr/sbin/smbd [0x80107611]
#9 /usr/sbin/smbd(_lsa_lookup_sids+0x131) [0x80107df1]
#10 /usr/sbin/smbd [0x801011d1]
#11 /usr/sbin/smbd(api_rpcTNP+0x198) [0x80162478]
#12 /usr/sbin/smbd(api_pipe_request+0x19e) [0x80162ace]
#13 /usr/sbin/smbd [0x8015d63f]
#14 /usr/sbin/smbd [0x8015db7c]
#15 /usr/sbin/smbd(write_to_pipe+0x6e) [0x8015c3ae]
#16 /usr/sbin/smbd [0x8005f381]
#17 /usr/sbin/smbd [0x8005f8b6]
#18 /usr/sbin/smbd(reply_trans+0x5e0) [0x800601c0]
#19 /usr/sbin/smbd [0x800b4410]
#20 /usr/sbin/smbd(smbd_process+0x78b) [0x800b550b]
#21 /usr/sbin/smbd(main+0xbd0) [0x802c2200]
#22 /lib/libc.so.6(__libc_start_main+0xdc) [0xb7bc587c]
#23 /usr/sbin/smbd [0x80042f21]
[2007/08/28 12:40:59, 0] lib/fault.c:dump_core(180)
dumping core in /var/log/samba/cores/smbd
[2007/08/28 12:40:59, 0] lib/fault.c:fault_report(41)
================================================== =============
[2007/08/28 12:40:59, 0] lib/fault.c:fault_report(42)
INTERNAL ERROR: Signal 6 in pid 8872 (3.0.24-2.28-1354-SUSE-CODE10)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2007/08/28 12:41:00, 0] lib/fault.c:fault_report(44)
From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2007/08/28 12:41:00, 0] lib/fault.c:fault_report(45)
================================================== =============
[2007/08/28 12:41:00, 0] lib/util.c:smb_panic(1599)
PANIC (pid 8872): internal error
[2007/08/28 12:41:00, 0] lib/util.c:log_stack_trace(1706)
BACKTRACE: 24 stack frames:
#0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x8021861d]
#1 /usr/sbin/smbd(smb_panic+0x5d) [0x8021874d]
#2 /usr/sbin/smbd [0x8020418a]
#3 [0xffffe420]
#4 /lib/libc.so.6(abort+0x103) [0xb7bd9ff3]
#5 /usr/sbin/smbd [0x8021e986]
#6 /usr/sbin/smbd(talloc_steal+0x3a) [0x8021eb5a]
#7 /usr/sbin/smbd(lookup_sids+0x39a) [0x801d56ca]
#8 /usr/sbin/smbd [0x80107611]
#9 /usr/sbin/smbd(_lsa_lookup_sids+0x131) [0x80107df1]
#10 /usr/sbin/smbd [0x801011d1]
#11 /usr/sbin/smbd(api_rpcTNP+0x198) [0x80162478]
#12 /usr/sbin/smbd(api_pipe_request+0x19e) [0x80162ace]
#13 /usr/sbin/smbd [0x8015d63f]
#14 /usr/sbin/smbd [0x8015db7c]
#15 /usr/sbin/smbd(write_to_pipe+0x6e) [0x8015c3ae]
#16 /usr/sbin/smbd [0x8005f381]
#17 /usr/sbin/smbd [0x8005f8b6]
#18 /usr/sbin/smbd(reply_trans+0x5e0) [0x800601c0]
#19 /usr/sbin/smbd [0x800b4410]
#20 /usr/sbin/smbd(smbd_process+0x78b) [0x800b550b]
#21 /usr/sbin/smbd(main+0xbd0) [0x802c2200]
#22 /lib/libc.so.6(__libc_start_main+0xdc) [0xb7bc587c]
#23 /usr/sbin/smbd [0x80042f21]
[2007/08/28 12:41:03, 0] lib/fault.c:dump_core(180)
dumping core in /var/log/samba/cores/smbd
[2007/08/28 12:41:03, 0] lib/fault.c:fault_report(41)
================================================== =============
[2007/08/28 12:41:03, 0] lib/fault.c:fault_report(42)
INTERNAL ERROR: Signal 6 in pid 8874 (3.0.24-2.28-1354-SUSE-CODE10)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2007/08/28 12:41:03, 0] lib/fault.c:fault_report(44)
From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2007/08/28 12:41:03, 0] lib/fault.c:fault_report(45)
================================================== =============
[2007/08/28 12:41:03, 0] lib/util.c:smb_panic(1599)
PANIC (pid 8874): internal error
[2007/08/28 12:41:04, 0] lib/util.c:log_stack_trace(1706)
BACKTRACE: 24 stack frames:
#0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x8021861d]
#1 /usr/sbin/smbd(smb_panic+0x5d) [0x8021874d]
#2 /usr/sbin/smbd [0x8020418a]
#3 [0xffffe420]
#4 /lib/libc.so.6(abort+0x103) [0xb7bd9ff3]
#5 /usr/sbin/smbd [0x8021e986]
#6 /usr/sbin/smbd(talloc_steal+0x3a) [0x8021eb5a]
#7 /usr/sbin/smbd(lookup_sids+0x39a) [0x801d56ca]
#8 /usr/sbin/smbd [0x80107611]
#9 /usr/sbin/smbd(_lsa_lookup_sids+0x131) [0x80107df1]
#10 /usr/sbin/smbd [0x801011d1]
#11 /usr/sbin/smbd(api_rpcTNP+0x198) [0x80162478]
#12 /usr/sbin/smbd(api_pipe_request+0x19e) [0x80162ace]
#13 /usr/sbin/smbd [0x8015d63f]
#14 /usr/sbin/smbd [0x8015db7c]
#15 /usr/sbin/smbd(write_to_pipe+0x6e) [0x8015c3ae]
#16 /usr/sbin/smbd [0x8005f381]
#17 /usr/sbin/smbd [0x8005f8b6]
#18 /usr/sbin/smbd(reply_trans+0x5e0) [0x800601c0]
#19 /usr/sbin/smbd [0x800b4410]
#20 /usr/sbin/smbd(smbd_process+0x78b) [0x800b550b]
#21 /usr/sbin/smbd(main+0xbd0) [0x802c2200]
#22 /lib/libc.so.6(__libc_start_main+0xdc) [0xb7bc587c]
#23 /usr/sbin/smbd [0x80042f21]
[2007/08/28 12:41:06, 0] lib/fault.c:dump_core(180)
dumping core in /var/log/samba/cores/smbd
[2007/08/28 12:41:06, 0] lib/util_sock.c:get_peer_addr(1229)
getpeername failed. Error was Transport endpoint is not connected
[2007/08/28 12:41:06, 0] lib/util_sock.c:get_peer_addr(1229)
getpeername failed. Error was Transport endpoint is not connected
[2007/08/28 12:41:06, 0] lib/util_sock.c:read_data(534)
read_data: read failure for 4 bytes to client 0.0.0.0. Error = Connection
reset by peer
************************************************** *******************
Letzteres Logfile scheint auf etwas Böseres hinzudeuten!
Weiterhin ergibt der Aufruf von testparm, dass die verwendete Version keine
Mehrfacheinträge für das Authentifizierungsbackend mehr unterstützt:
passdb backend = ldapsam:ldap://127.0.0.1 smbpasswd
Hier wird smbpasswd ignoriert. Die Frage ist, ob uns das stören muss? Der
Benutzer root ist nur in der smbpasswd eingetragen, nicht aber im
LDAP-Verzeichnis. Um neue Windows-Maschinen in die NT-Domäne aufzunehmen
brauchen wir aber die Authentifizierung als root, oder nicht? Wie geht man
hier am sinnvollsten vor?
Der Vollständigkeit halber folgt hier noch die Global-Section der smb.conf:
************************************************** *******************
[global]
workgroup = micro-optics
server string = micro-optics PDC (SLES 10)
hosts allow = 127.0.0.1 192.168.173.0/24 132.230.0.0/16
hosts deny = 0.0.0.0/0
printing = cups
printcap name = cups
printcap cache time = 750
#printer admin = *ntadmin
load printers = yes
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \\%L\profiles$\.msprofile
#logon path = \\%L\profiles
#logon home = \\%L\%U\.9xprofile
logon drive = L:
logon script = logon.bat
add machine
script= /sbin/yast /usr/share/YaST2/data/add_machine.ycp %m
$
domain logons = Yes
domain master = Yes
ldap passwd sync = Yes
local master = Yes
os level = 65
passdb backend = ldapsam:ldap://127.0.0.1 smbpasswd
preferred master = Yes
security = user
wins support = Yes
netbios name = rioja
idmap backend = ldap:ldap://127.0.0.1
ldap admin dn = cn=moadmin,dc=micro-optics,dc=local
ldap group suffix = ou=gruppen
ldap idmap suffix = ou=Idmap
ldap machine suffix = ou=rechner
ldap suffix = dc=micro-optics,dc=local
ldap user suffix = ou=nutzer
idmap gid = 10000-20000
idmap uid = 10000-20000
************************************************** *******************
Vielen Dank schon mal im Voraus!
Viele Grüße,
Daniel Mader
wir betreiben einen Arbeitsgruppenserver auf Basis des SLES 10 SP1.
Folgende Pakete sind installiert:
samba-doc-3.0.24-2.23
kdebase3-samba-3.5.1-69.52
yast2-samba-server-2.13.22-0.8
samba-client-3.0.24-2.28
samba-winbind-3.0.24-2.28
yast2-samba-client-2.13.36-0.8
samba-pdb-3.0.24-2.28
samba-3.0.24-2.28
Der Server funktioniert soweit, leider haben wir aber noch ein
Konfigurationsproblem, was uns volle Logfiles und Messages beschert:
************************************************** *******************
Auszug aus log.nmbd:
[2007/08/28 13:03:34, 0]
nmbd/nmbd_browsesync.c:get_domain_master_name_node_stat us_fail(486)
get_domain_master_name_node_status_fail:
Doing a node status request to the domain master browser at IP
192.168.173.252 failed.
Cannot get workgroup name.
[2007/08/28 13:18:28, 0]
nmbd/nmbd_browsesync.c:get_domain_master_name_node_stat us_fail(486)
get_domain_master_name_node_status_fail:
Doing a node status request to the domain master browser at IP
192.168.173.253 failed.
Cannot get workgroup name.
[2007/08/28 13:18:28, 0]
nmbd/nmbd_browsesync.c:get_domain_master_name_node_stat us_fail(486)
get_domain_master_name_node_status_fail:
Doing a node status request to the domain master browser at IP
192.168.173.252 failed.
Cannot get workgroup name.
[2007/08/28 13:33:40, 0]
nmbd/nmbd_browsesync.c:get_domain_master_name_node_stat us_fail(486)
get_domain_master_name_node_status_fail:
Doing a node status request to the domain master browser at IP
192.168.173.253 failed.
Cannot get workgroup name.
[2007/08/28 13:33:40, 0]
nmbd/nmbd_browsesync.c:get_domain_master_name_node_stat us_fail(486)
get_domain_master_name_node_status_fail:
Doing a node status request to the domain master browser at IP
192.168.173.252 failed.
Cannot get workgroup name.
[2007/08/28 13:48:30, 0]
nmbd/nmbd_browsesync.c:get_domain_master_name_node_stat us_fail(486)
get_domain_master_name_node_status_fail:
Doing a node status request to the domain master browser at IP
192.168.173.253 failed.
Cannot get workgroup name.
[2007/08/28 13:48:30, 0]
nmbd/nmbd_browsesync.c:get_domain_master_name_node_stat us_fail(486)
get_domain_master_name_node_status_fail:
Doing a node status request to the domain master browser at IP
192.168.173.252 failed.
Cannot get workgroup name.
************************************************** *******************
************************************************** *******************
Auszug aus log.smbd:
[2007/08/28 12:40:57, 0] lib/fault.c:fault_report(41)
================================================== =============
[2007/08/28 12:40:57, 0] lib/fault.c:fault_report(42)
INTERNAL ERROR: Signal 6 in pid 8871 (3.0.24-2.28-1354-SUSE-CODE10)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2007/08/28 12:40:57, 0] lib/fault.c:fault_report(44)
From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2007/08/28 12:40:57, 0] lib/fault.c:fault_report(45)
================================================== =============
[2007/08/28 12:40:57, 0] lib/util.c:smb_panic(1599)
PANIC (pid 8871): internal error
[2007/08/28 12:40:57, 0] lib/util.c:log_stack_trace(1706)
BACKTRACE: 24 stack frames:
#0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x8021861d]
#1 /usr/sbin/smbd(smb_panic+0x5d) [0x8021874d]
#2 /usr/sbin/smbd [0x8020418a]
#3 [0xffffe420]
#4 /lib/libc.so.6(abort+0x103) [0xb7bd9ff3]
#5 /usr/sbin/smbd [0x8021e986]
#6 /usr/sbin/smbd(talloc_steal+0x3a) [0x8021eb5a]
#7 /usr/sbin/smbd(lookup_sids+0x39a) [0x801d56ca]
#8 /usr/sbin/smbd [0x80107611]
#9 /usr/sbin/smbd(_lsa_lookup_sids+0x131) [0x80107df1]
#10 /usr/sbin/smbd [0x801011d1]
#11 /usr/sbin/smbd(api_rpcTNP+0x198) [0x80162478]
#12 /usr/sbin/smbd(api_pipe_request+0x19e) [0x80162ace]
#13 /usr/sbin/smbd [0x8015d63f]
#14 /usr/sbin/smbd [0x8015db7c]
#15 /usr/sbin/smbd(write_to_pipe+0x6e) [0x8015c3ae]
#16 /usr/sbin/smbd [0x8005f381]
#17 /usr/sbin/smbd [0x8005f8b6]
#18 /usr/sbin/smbd(reply_trans+0x5e0) [0x800601c0]
#19 /usr/sbin/smbd [0x800b4410]
#20 /usr/sbin/smbd(smbd_process+0x78b) [0x800b550b]
#21 /usr/sbin/smbd(main+0xbd0) [0x802c2200]
#22 /lib/libc.so.6(__libc_start_main+0xdc) [0xb7bc587c]
#23 /usr/sbin/smbd [0x80042f21]
[2007/08/28 12:40:59, 0] lib/fault.c:dump_core(180)
dumping core in /var/log/samba/cores/smbd
[2007/08/28 12:40:59, 0] lib/fault.c:fault_report(41)
================================================== =============
[2007/08/28 12:40:59, 0] lib/fault.c:fault_report(42)
INTERNAL ERROR: Signal 6 in pid 8872 (3.0.24-2.28-1354-SUSE-CODE10)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2007/08/28 12:41:00, 0] lib/fault.c:fault_report(44)
From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2007/08/28 12:41:00, 0] lib/fault.c:fault_report(45)
================================================== =============
[2007/08/28 12:41:00, 0] lib/util.c:smb_panic(1599)
PANIC (pid 8872): internal error
[2007/08/28 12:41:00, 0] lib/util.c:log_stack_trace(1706)
BACKTRACE: 24 stack frames:
#0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x8021861d]
#1 /usr/sbin/smbd(smb_panic+0x5d) [0x8021874d]
#2 /usr/sbin/smbd [0x8020418a]
#3 [0xffffe420]
#4 /lib/libc.so.6(abort+0x103) [0xb7bd9ff3]
#5 /usr/sbin/smbd [0x8021e986]
#6 /usr/sbin/smbd(talloc_steal+0x3a) [0x8021eb5a]
#7 /usr/sbin/smbd(lookup_sids+0x39a) [0x801d56ca]
#8 /usr/sbin/smbd [0x80107611]
#9 /usr/sbin/smbd(_lsa_lookup_sids+0x131) [0x80107df1]
#10 /usr/sbin/smbd [0x801011d1]
#11 /usr/sbin/smbd(api_rpcTNP+0x198) [0x80162478]
#12 /usr/sbin/smbd(api_pipe_request+0x19e) [0x80162ace]
#13 /usr/sbin/smbd [0x8015d63f]
#14 /usr/sbin/smbd [0x8015db7c]
#15 /usr/sbin/smbd(write_to_pipe+0x6e) [0x8015c3ae]
#16 /usr/sbin/smbd [0x8005f381]
#17 /usr/sbin/smbd [0x8005f8b6]
#18 /usr/sbin/smbd(reply_trans+0x5e0) [0x800601c0]
#19 /usr/sbin/smbd [0x800b4410]
#20 /usr/sbin/smbd(smbd_process+0x78b) [0x800b550b]
#21 /usr/sbin/smbd(main+0xbd0) [0x802c2200]
#22 /lib/libc.so.6(__libc_start_main+0xdc) [0xb7bc587c]
#23 /usr/sbin/smbd [0x80042f21]
[2007/08/28 12:41:03, 0] lib/fault.c:dump_core(180)
dumping core in /var/log/samba/cores/smbd
[2007/08/28 12:41:03, 0] lib/fault.c:fault_report(41)
================================================== =============
[2007/08/28 12:41:03, 0] lib/fault.c:fault_report(42)
INTERNAL ERROR: Signal 6 in pid 8874 (3.0.24-2.28-1354-SUSE-CODE10)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2007/08/28 12:41:03, 0] lib/fault.c:fault_report(44)
From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2007/08/28 12:41:03, 0] lib/fault.c:fault_report(45)
================================================== =============
[2007/08/28 12:41:03, 0] lib/util.c:smb_panic(1599)
PANIC (pid 8874): internal error
[2007/08/28 12:41:04, 0] lib/util.c:log_stack_trace(1706)
BACKTRACE: 24 stack frames:
#0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x8021861d]
#1 /usr/sbin/smbd(smb_panic+0x5d) [0x8021874d]
#2 /usr/sbin/smbd [0x8020418a]
#3 [0xffffe420]
#4 /lib/libc.so.6(abort+0x103) [0xb7bd9ff3]
#5 /usr/sbin/smbd [0x8021e986]
#6 /usr/sbin/smbd(talloc_steal+0x3a) [0x8021eb5a]
#7 /usr/sbin/smbd(lookup_sids+0x39a) [0x801d56ca]
#8 /usr/sbin/smbd [0x80107611]
#9 /usr/sbin/smbd(_lsa_lookup_sids+0x131) [0x80107df1]
#10 /usr/sbin/smbd [0x801011d1]
#11 /usr/sbin/smbd(api_rpcTNP+0x198) [0x80162478]
#12 /usr/sbin/smbd(api_pipe_request+0x19e) [0x80162ace]
#13 /usr/sbin/smbd [0x8015d63f]
#14 /usr/sbin/smbd [0x8015db7c]
#15 /usr/sbin/smbd(write_to_pipe+0x6e) [0x8015c3ae]
#16 /usr/sbin/smbd [0x8005f381]
#17 /usr/sbin/smbd [0x8005f8b6]
#18 /usr/sbin/smbd(reply_trans+0x5e0) [0x800601c0]
#19 /usr/sbin/smbd [0x800b4410]
#20 /usr/sbin/smbd(smbd_process+0x78b) [0x800b550b]
#21 /usr/sbin/smbd(main+0xbd0) [0x802c2200]
#22 /lib/libc.so.6(__libc_start_main+0xdc) [0xb7bc587c]
#23 /usr/sbin/smbd [0x80042f21]
[2007/08/28 12:41:06, 0] lib/fault.c:dump_core(180)
dumping core in /var/log/samba/cores/smbd
[2007/08/28 12:41:06, 0] lib/util_sock.c:get_peer_addr(1229)
getpeername failed. Error was Transport endpoint is not connected
[2007/08/28 12:41:06, 0] lib/util_sock.c:get_peer_addr(1229)
getpeername failed. Error was Transport endpoint is not connected
[2007/08/28 12:41:06, 0] lib/util_sock.c:read_data(534)
read_data: read failure for 4 bytes to client 0.0.0.0. Error = Connection
reset by peer
************************************************** *******************
Letzteres Logfile scheint auf etwas Böseres hinzudeuten!
Weiterhin ergibt der Aufruf von testparm, dass die verwendete Version keine
Mehrfacheinträge für das Authentifizierungsbackend mehr unterstützt:
passdb backend = ldapsam:ldap://127.0.0.1 smbpasswd
Hier wird smbpasswd ignoriert. Die Frage ist, ob uns das stören muss? Der
Benutzer root ist nur in der smbpasswd eingetragen, nicht aber im
LDAP-Verzeichnis. Um neue Windows-Maschinen in die NT-Domäne aufzunehmen
brauchen wir aber die Authentifizierung als root, oder nicht? Wie geht man
hier am sinnvollsten vor?
Der Vollständigkeit halber folgt hier noch die Global-Section der smb.conf:
************************************************** *******************
[global]
workgroup = micro-optics
server string = micro-optics PDC (SLES 10)
hosts allow = 127.0.0.1 192.168.173.0/24 132.230.0.0/16
hosts deny = 0.0.0.0/0
printing = cups
printcap name = cups
printcap cache time = 750
#printer admin = *ntadmin
load printers = yes
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \\%L\profiles$\.msprofile
#logon path = \\%L\profiles
#logon home = \\%L\%U\.9xprofile
logon drive = L:
logon script = logon.bat
add machine
script= /sbin/yast /usr/share/YaST2/data/add_machine.ycp %m
$
domain logons = Yes
domain master = Yes
ldap passwd sync = Yes
local master = Yes
os level = 65
passdb backend = ldapsam:ldap://127.0.0.1 smbpasswd
preferred master = Yes
security = user
wins support = Yes
netbios name = rioja
idmap backend = ldap:ldap://127.0.0.1
ldap admin dn = cn=moadmin,dc=micro-optics,dc=local
ldap group suffix = ou=gruppen
ldap idmap suffix = ou=Idmap
ldap machine suffix = ou=rechner
ldap suffix = dc=micro-optics,dc=local
ldap user suffix = ou=nutzer
idmap gid = 10000-20000
idmap uid = 10000-20000
************************************************** *******************
Vielen Dank schon mal im Voraus!
Viele Grüße,
Daniel Mader