Hi,
since some Months, our Windows 2000 and Windows-XP Clients have the Problem,
that in Explorer the Connection to the Share on the Samba-Server seems to be
lost. But on clicking on the drive letter in can be reactivated. The Clients
habe Windows 2000 SP3 or Windows XP SP1.
The Samba-Server is in a Domain controlled by a Windows 2000 Server.
In the log-file of the clients with these Problems the folowing ist printed:
[2002/12/12 09:06:44, 0] lib/util_sock.c:write_socket_data(499)
write_socket_data: write failure. Error = Connection reset by peer
[2002/12/13 08:37:40, 0] lib/util_sock.c:write_socket_data(499)
write_socket_data: write failure. Error = Connection reset by peer
[2002/12/16 09:07:11, 0] lib/util_sock.c:write_socket_data(499)
write_socket_data: write failure. Error = Connection reset by peer
[2002/12/17 09:17:03, 0] lib/util_sock.c:write_socket_data(499)
write_socket_data: write failure. Error = Connection reset by peer
[2002/12/18 14:36:36, 0] lib/util_sock.c:write_socket_data(499)
write_socket_data: write failure. Error = Connection reset by peer
[2002/12/19 15:57:31, 0] lib/util_sock.c:write_socket_data(499)
write_socket_data: write failure. Error = Connection reset by peer
[2003/01/07 08:57:44, 0] lib/util_sock.c:write_socket_data(499)
write_socket_data: write failure. Error = Connection reset by peer
[2003/01/08 08:45:51, 0] lib/util_sock.c:write_socket_data(499)
write_socket_data: write failure. Error = Connection reset by peer
[2003/01/09 14:58:14, 0] lib/util_sock.c:write_socket_data(499)
write_socket_data: write failure. Error = Connection reset by peer
[2003/01/10 08:42:59, 0] lib/util_sock.c:write_socket_data(499)
write_socket_data: write failure. Error = Connection reset by peer
[2003/01/13 12:12:31, 0] lib/util_sock.c:write_socket_data(499)
write_socket_data: write failure. Error = Connection reset by peer
The Server is Running SuSE 7.2 with all security updates. Samba is
self-compiled with these options:
./configure \
--prefix=/usr/local/samba \
--exec-prefix=/usr/local/samba \
--sysconfdir=/etc/samba \
--with-privatedir=/etc/samba \
--with-configdir=/etc/samba \
--with-smbmount \
--without-acl-support
Here ist the smb.conf
[global]
workgroup = FTK
netbios name = WOOKIE2
server string = Samba Server
security = SERVER
encrypt passwords = Yes
password server = EXCHANGE
log file = /var/log/samba/log.%m
max log size = 50
add user script = /usr/sbin/useradd %u
delete user script = /usr/sbin/userdel %u
[FTKADMIN]
path = /root/smb_ftkadmin
valid users = @ftkadmin
force user = root
force group = root
writeable = Yes
[REDAKTION]
comment = stuff: redaktion
path = /mnt/harddisks/hdb1/redaktion
valid users = @ftk_reda
force group = ftk_reda
writeable = Yes
create mask = 0770
directory mask = 0770
[devel_ecin]
path = /www/devel_ecin
valid users = tschuermann, msmieja, abruns, oehlert, mrobben,
rkoyro, abarre, oczypull, cheiders, mgatzke, jvollmert
force user = imperia
force group = imperia
writeable = Yes
create mask = 0755
force create mode = 0755
force directory mode = 0755
[devel_media]
path = /www/devel_media
valid users = @ftk_develmedia
force user = imperia
force group = imperia
writeable = Yes
create mask = 0755
force create mode = 0755
force directory mode = 0755
Is there something I configured wrong?
On another File-server with the same compile-Options and the same
smb.conf, these problems are less often.
Greetings
Alexander Bruns
Alexander Bruns
System- und Netzwerkadministration
FTK - Forschungsinstitut fuer Telekommunikation
Martin-Schmeisser-Weg 4
D - 44227 Dortmund
tel + 49 (0) 231 97 50 56 16
fax + 49 (0) 231 97 50 56 10
mail abruns@ftk.de