samba - Jul 2006 - kicked users and login troubles (write failure in writing to client and Connection reset by peer)

Hi List,

One particular user is kicked quite often (espescially during the usage 
of Outlook). When she tries to login she isn't very succesfull. The 
serverlog show this:

Jul 13 10:41:14 server smbd[12277]: [2006/07/13 10:41:14, 0] 
lib/util_sock.c:write_data(554)
Jul 13 10:41:14 server smbd[12277]:   write_data: write failure in 
writing to client 192.168.1.101. Error Connection reset by peer
Jul 13 10:41:14 server smbd[12277]: [2006/07/13 10:41:14, 0] 
lib/util_sock.c:send_smb(762)
Jul 13 10:41:14 server smbd[12277]:   Error writing 61503 bytes to 
client. -1. (Connection reset by peer)

I've tried disabling the oplocks; because I suspect the problem lies 
herein. However; reloading the config file gives me these errors:

Jul 13 10:48:36 server smbd[9426]: [2006/07/13 10:48:36, 0] 
param/loadparm.c:map_parameter(2650)
Jul 13 10:48:36 server smbd[9426]:   Unknown parameter encountered: "z 
browseable"
Jul 13 10:48:36 server smbd[9426]: [2006/07/13 10:48:36, 0] 
param/loadparm.c:lp_do_parameter(3399)
Jul 13 10:48:36 server smbd[9426]:   Ignoring unknown parameter "z 
browseable"
Jul 13 10:48:36 server smbd[9426]: [2006/07/13 10:48:36, 0] 
param/loadparm.c:map_parameter(2650)
Jul 13 10:48:36 server smbd[9426]:   Unknown parameter encountered: "3 
oplocks"
Jul 13 10:48:36 server smbd[9426]: [2006/07/13 10:48:36, 0] 
param/loadparm.c:lp_do_parameter(3399)
Jul 13 10:48:36 server smbd[9426]:   Ignoring unknown parameter "3
oplocks"

my global section of smb.conf:

[global]
   workgroup = sophia
   printing = cups
   printcap name = cups
   printcap cache time = 750
   cups options = raw
   map to guest = Bad User
   include = /etc/samba/dhcp.conf
   logon path = \\%N\profiles\.msprofile
   logon home = \\%N\%U
   logon drive = W:
   logon script = logon.bat
   security = user
   encrypt passwords = yes
   passdb backend = ldapsam:ldap://localhost smbpasswd
   ldap admin dn = cn=Administrator,dc=sophia
   ldap suffix = dc=sophia
   ldap group suffix = ou=group
   ldap user suffix = ou=people
   add machine script = /sbin/yast /usr/share/YaST2/data/add_machine.ycp %m$
   domain logons = yes
   idmap backend = ldap:ldap://localhost
   ldap idmap suffix = ou=Idmap
   ldap machine suffix = ou=Computers
   local master = yes
   wins support = yes
   netbios name = server
   domain master = yes
   preferred master = yes
   os level = 65
        oplocks = No
        level2 oplocks = no
        kernel oplocks = no


Anyone any ideas? It has been suggested that the hardware could be 
defect, but it's strange because only one user suffers from these problems.
ifconfig offers this information:

eth0      Link encap:Ethernet  HWaddr 00:0C:6E:10:DE:84
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:269696 errors:0 dropped:0 overruns:0 frame:0
          TX packets:478580 errors:0 dropped:0 overruns:0 carrier:7
          collisions:0 txqueuelen:1000
          RX bytes:54893197 (52.3 Mb)  TX bytes:420965181 (401.4 Mb)
          Interrupt:10

So there are a few carrier's. Could this be related?

-- 
Thijs Hakkenberg,  

Voorzitter Stichting Ebriositas
www.ebriositas.nl

Student Natuurkunde UvA
www.uva.nl

Systeembeheerder Stichting Varkens in Nood
www.varkensinnood.nl

Contact:
tel: 06-48761131
www.hakkenberg.com
thijs@hakkenberg.com

On Thu, Jul 13, 2006 at 12:53:19PM +0200, Thijs Hakkenberg
wrote:
> Hi List,
> 
> One particular user is kicked quite often (espescially during the usage 
> of Outlook). When she tries to login she isn't very succesfull. The 
> serverlog show this:
> 
> Jul 13 10:41:14 server smbd[12277]: [2006/07/13 10:41:14, 0] 
> lib/util_sock.c:write_data(554)
> Jul 13 10:41:14 server smbd[12277]:   write_data: write failure in 
> writing to client 192.168.1.101. Error Connection reset by peer
> Jul 13 10:41:14 server smbd[12277]: [2006/07/13 10:41:14, 0] 
> lib/util_sock.c:send_smb(762)
> Jul 13 10:41:14 server smbd[12277]:   Error writing 61503 bytes to 
> client. -1. (Connection reset by peer)
"Connection reset by peer" means the client sent a TCP RST 
packet as it thinks the connection is closed. Check your
networking hw.
> I've tried disabling the oplocks; because I suspect the problem lies 
> herein. However; reloading the config file gives me these errors:
> 
> Jul 13 10:48:36 server smbd[9426]: [2006/07/13 10:48:36, 0] 
> param/loadparm.c:map_parameter(2650)
> Jul 13 10:48:36 server smbd[9426]:   Unknown parameter encountered: "z
> browseable"
> Jul 13 10:48:36 server smbd[9426]: [2006/07/13 10:48:36, 0] 
> param/loadparm.c:lp_do_parameter(3399)
> Jul 13 10:48:36 server smbd[9426]:   Ignoring unknown parameter "z 
> browseable"
> Jul 13 10:48:36 server smbd[9426]: [2006/07/13 10:48:36, 0] 
> param/loadparm.c:map_parameter(2650)
> Jul 13 10:48:36 server smbd[9426]:   Unknown parameter encountered: "3
> oplocks"
> Jul 13 10:48:36 server smbd[9426]: [2006/07/13 10:48:36, 0] 
> param/loadparm.c:lp_do_parameter(3399)
> Jul 13 10:48:36 server smbd[9426]:   Ignoring unknown parameter "3
oplocks"
Looks like memory corruption ? Run memtest ?

Jeremy.