PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : zwei Sambaserver im Windowsnetzwerk



bueckner
26.08.05, 13:46
Hallo,
ich habe in einem Netzwerk zwei Sambaserver (einer unter SuSE9.2 der andere unter SuSE9.3) mit einer Reihe von Windowsrechnern (von 98 bis xp-pro).
Der eine Server hat die 4, der andere die 12 als IP.

Problem: Die Verbindung von dem einen Server zu den Win-Rechnern wird sporadisch abgebrochen, ein erneuter Zugriff ist dann nur nach Neustert von Samba möglich.

Anbei die beiden smb.conf Files un ein Ausschnitt aus /var/log/messages:

####### smb.conf von dem Samba ohne Probleme:
# Global parameters
[global]
workgroup = xxxx
netbios name = FILESERVER01
server string = FileServer01
encrypt passwords = Yes
domain logons = yes

hosts allow = 192.168.1.

username map = /etc/samba/smbusers

security = user

local master = yes
os level = 64
domain master = yes
preferred master = yes
domain logons = yes

####### smb.conf von dem Samba mit dem Problem:
die Zeilen mit den #. waren meine letzten Versuche ...
[global]
workgroup = xxxx
netbios name = fileserver02
server string = fileserver02

username map = /etc/samba/smbusers
map to guest = Bad User
#. include = /etc/samba/dhcp.conf
#. logon path = \\%L\profiles\.msprofile
#. logon home = \\%L\%U\.9xprofile
#. logon drive = P:
security = user
encrypt passwords = yes
domain logons = yes
domain master = no
#. ldap idmap suffix = ou=Idmap
#. ldap machine suffix = ou=Computers
local master = no
os level = 40
preferred master = no
#. ldap suffix = dc=example,dc=com
hosts allow = 192.168.1.

####### die messages:
Aug 26 08:24:53 fileserver02 nmbd[3428]: [2005/08/26 08:24:53, 0] nmbd/asyncdns.c:start_async_dns(149)
Aug 26 08:24:53 fileserver02 nmbd[3428]: started asyncdns process 3429
Aug 26 08:24:53 fileserver02 nmbd[3428]: [2005/08/26 08:24:53, 0] nmbd/nmbd_logonnames.c:add_logon_names(163)
Aug 26 08:24:53 fileserver02 nmbd[3428]: add_domain_logon_names:
Aug 26 08:24:53 fileserver02 nmbd[3428]: Attempting to become logon server for workgroup xxxx on subnet 192.168.
1.12
Aug 26 08:24:53 fileserver02 nmbd[3428]: [2005/08/26 08:24:53, 0] nmbd/nmbd_logonnames.c:add_logon_names(163)
Aug 26 08:24:53 fileserver02 nmbd[3428]: add_domain_logon_names:
Aug 26 08:24:53 fileserver02 nmbd[3428]: Attempting to become logon server for workgroup xxxx on subnet UNICAST_
SUBNET
Aug 26 08:24:53 fileserver02 nmbd[3428]: [2005/08/26 08:24:53, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(124
)
Aug 26 08:24:53 fileserver02 nmbd[3428]: become_logon_server_success: Samba is now a logon server for workgroup xxxx on subnet UNICAST_SUBNET
Aug 26 08:24:57 fileserver02 kernel: klogd 1.4.1, log source = /proc/kmsg started.
Aug 26 08:24:57 fileserver02 kernel: eth0: Media Link On 100mbps full-duplex
Aug 26 08:24:57 fileserver02 nmbd[3428]: [2005/08/26 08:24:57, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(124
)
Aug 26 08:24:57 fileserver02 nmbd[3428]: become_logon_server_success: Samba is now a logon server for workgroup xxxx on subnet 192.168.1.12


Aug 26 09:04:40 fileserver02 smbd[4214]: [2005/08/26 09:04:40, 0] lib/util_sock.c:read_socket_data(384)
Aug 26 09:04:40 fileserver02 smbd[4214]: read_socket_data: recv failure for 4. Error = Connection reset by peer
Aug 26 09:06:41 fileserver02 smbd[4217]: [2005/08/26 09:06:41, 0] lib/util_sock.c:get_peer_addr(1136)
Aug 26 09:06:41 fileserver02 smbd[4217]: getpeername failed. Error was Transport endpoint is not connected
Aug 26 09:06:41 fileserver02 smbd[4217]: [2005/08/26 09:06:41, 0] lib/access.c:check_access(328)
Aug 26 09:06:41 fileserver02 smbd[4217]: [2005/08/26 09:06:41, 0] lib/util_sock.c:get_peer_addr(1136)
Aug 26 09:06:41 fileserver02 smbd[4217]: getpeername failed. Error was Transport endpoint is not connected
Aug 26 09:06:41 fileserver02 smbd[4217]: Denied connection from (0.0.0.0)
Aug 26 09:06:41 fileserver02 smbd[4217]: [2005/08/26 09:06:41, 0] lib/util_sock.c:get_peer_addr(1136)
Aug 26 09:06:41 fileserver02 smbd[4217]: getpeername failed. Error was Transport endpoint is not connected
Aug 26 09:06:41 fileserver02 smbd[4217]: Connection denied from 0.0.0.0
Aug 26 09:06:41 fileserver02 smbd[4217]: [2005/08/26 09:06:41, 0] lib/util_sock.c:write_socket_data(430)
Aug 26 09:06:41 fileserver02 smbd[4217]: write_socket_data: write failure. Error = Connection reset by peer
Aug 26 09:06:41 fileserver02 smbd[4217]: [2005/08/26 09:06:41, 0] lib/util_sock.c:write_socket(455)
Aug 26 09:06:41 fileserver02 smbd[4217]: write_socket: Error writing 5 bytes to socket 24: ERRNO = Connection reset by
peer
Aug 26 09:06:41 fileserver02 smbd[4217]: [2005/08/26 09:06:41, 0] lib/util_sock.c:send_smb(647)
Aug 26 09:06:41 fileserver02 smbd[4217]: Error writing 5 bytes to client. -1. (Connection reset by peer)
Aug 26 09:38:41 fileserver02 smbd[4270]: [2005/08/26 09:38:41, 0] lib/util_sock.c:read_socket_data(384)
Aug 26 09:38:41 fileserver02 smbd[4270]: read_socket_data: recv failure for 4. Error = Connection reset by peer
Aug 26 09:59:01 fileserver02 /usr/sbin/cron[4296]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Aug 26 10:10:41 fileserver02 smbd[4318]: [2005/08/26 10:10:41, 0] lib/util_sock.c:get_peer_addr(1136)
Aug 26 10:10:41 fileserver02 smbd[4318]: getpeername failed. Error was Transport endpoint is not connected
Aug 26 10:10:41 fileserver02 smbd[4318]: [2005/08/26 10:10:41, 0] lib/util_sock.c:get_peer_addr(1136)
Aug 26 10:10:41 fileserver02 smbd[4318]: getpeername failed. Error was Transport endpoint is not connected
Aug 26 10:10:41 fileserver02 smbd[4318]: [2005/08/26 10:10:41, 0] lib/access.c:check_access(328)
Aug 26 10:10:41 fileserver02 smbd[4318]: [2005/08/26 10:10:41, 0] lib/util_sock.c:get_peer_addr(1136)
Aug 26 10:10:41 fileserver02 smbd[4318]: getpeername failed. Error was Transport endpoint is not connected
Aug 26 10:10:41 fileserver02 smbd[4318]: Denied connection from (0.0.0.0)
Aug 26 10:10:41 fileserver02 smbd[4318]: [2005/08/26 10:10:41, 0] lib/util_sock.c:get_peer_addr(1136)
Aug 26 10:10:41 fileserver02 smbd[4318]: getpeername failed. Error was Transport endpoint is not connected
Aug 26 10:10:41 fileserver02 smbd[4318]: Connection denied from 0.0.0.0
Aug 26 10:10:41 fileserver02 smbd[4318]: [2005/08/26 10:10:41, 0] lib/util_sock.c:write_socket_data(430)
Aug 26 10:10:41 fileserver02 smbd[4318]: write_socket_data: write failure. Error = Connection reset by peer
Aug 26 10:10:41 fileserver02 smbd[4318]: [2005/08/26 10:10:41, 0] lib/util_sock.c:write_socket(455)
Aug 26 10:10:41 fileserver02 smbd[4318]: write_socket: Error writing 5 bytes to socket 24: ERRNO = Connection reset by peer
Aug 26 10:10:41 fileserver02 smbd[4318]: [2005/08/26 10:10:41, 0] lib/util_sock.c:send_smb(647)
Aug 26 10:10:41 fileserver02 smbd[4318]: Error writing 5 bytes to client. -1. (Connection reset by peer)

Aug 26 12:21:54 fileserver02 nmbd[4379]: add_domain_logon_names:
Aug 26 12:21:54 fileserver02 nmbd[4379]: Attempting to become logon server for workgroup xxxx on subnet 192.168.1.12
Aug 26 12:21:58 fileserver02 nmbd[4379]: [2005/08/26 12:21:58, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(124)
Aug 26 12:21:58 fileserver02 nmbd[4379]: become_logon_server_success: Samba is now a logon server for workgroup xxxx on subnet 192.168.1.12

michaxyz
26.08.05, 14:08
Hallo bueckner,

ist es denn wirklich notwendig, dass beide Server Domänen-Logins entgegen nehmen?
Meiner Ansicht nach ist das "domain logons = yes" bei dem Domänen-Nicht-Master das Problem. Wäre es da nicht einfacher, securitiy auf server einzustellen und die Anfragen zu den Logons nur vom ersten Server beantworten zu lassen?

Mfg Michael

bueckner
26.08.05, 14:31
Hi Michael,

es ist so, dass der eine Server für die Benutzer in einem Gebäude, der andere für die Benutzer in einem anderen Gebäude ist. Beide Gebäude sind durch eine WLAN Verbindung (die kann schon mal ausfallen) verbunden. Als Domaincontroller fungieren die Server nicht, sondern sind reine Fileserver für die Arbeitsgruppe.

emba
30.08.05, 12:39
dann habt ihr was falsch konfiguriert

domain master = no
preferred master = yes
domain logons = no

greez