samba - Jul 2003 - My W2k client generates internal errors / panic in samba ?

I have a small site running Samba 2.2.8a from SuSE and I started wonder about
the "stability"
of Samba running with W2K clients, when I installed W2k on a machine that
previous ran Win.98
without any problems.

After the W2K installation's had been finished (with all security fixes, new
drivers etc.) I noticed
that when accessing shares on the samba server, Samba began generating log
entries like these:

  bopc2 (192.168.7.43) connect to service diverse as user bo (uid=1001, gid=100)
(pid 5965)
[2003/07/21 20:43:53, 0] lib/fault.c:fault_report(38)
  ==============================================================[2003/07/21
20:43:53, 0] lib/fault.c:fault_report(39)
  INTERNAL ERROR: Signal 11 in pid 5965 (2.2.8a-SuSE)
  Please read the file BUGS.txt in the distribution
[2003/07/21 20:43:53, 0] lib/fault.c:fault_report(41)
  ==============================================================[2003/07/21
20:43:53, 0] lib/util.c:smb_panic(1094)
  PANIC: internal error
[2003/07/21 20:43:53, 0] smbd/password.c:authorise_login(863) 


I started to look at how the W2K machine behaved during a normal working day,
and noticed that
it was as if the connection to the network-drives is lost for short periods of
time, when performing
certain operations on the client.
When trying to download a file from Opera on the client, another internal error
is generated, and
the saving of the file is aborted:

[2003/07/21 22:04:49, 2] smbd/service.c:make_connection(331)
  Invalid username/password for diverse [nobody]
[2003/07/21 22:04:49, 2] smbd/service.c:make_connection(331)
  Invalid username/password for bo [nobody]
[2003/07/21 22:04:49, 2] smbd/open.c:open_file(247)
  Bo opened file Download/linux-2.4.21.SuSE-1.tar.bz2 read=Yes write=No
(numopen=1)
[2003/07/21 22:04:49, 2] smbd/close.c:close_normal_file(229)
  bo closed file Download/linux-2.4.21.SuSE-1.tar.bz2 (numopen=0)
[2003/07/21 22:04:49, 2] smbd/open.c:open_file(247)
  Bo opened file Download/linux-2.4.21.SuSE-1.tar.bz2 read=Yes write=Yes
(numopen=1)
[2003/07/21 22:04:49, 0] lib/fault.c:fault_report(38)
  ==============================================================[2003/07/21
22:04:49, 0] lib/fault.c:fault_report(39)
  INTERNAL ERROR: Signal 11 in pid 7050 (2.2.8a-SuSE)
  Please read the file BUGS.txt in the distribution
[2003/07/21 22:04:49, 0] lib/fault.c:fault_report(41)
  ==============================================================[2003/07/21
22:04:49, 0] lib/util.c:smb_panic(1094)
  PANIC: internal error
[2003/07/21 22:04:50, 2] smbd/reply.c:reply_special(92)
  netbios connect: name1=LSERV1           name2=BOPC2
[2003/07/21 22:04:50, 2] smbd/reply.c:reply_special(111)
  netbios connect: local=lserv1 remote=bopc2
[2003/07/21 22:04:50, 1] smbd/service.c:make_connection(636)
  bopc2 (192.168.7.43) connect to service diverse as user bo (uid=1001, gid=100)
(pid 7051)
[2003/07/21 22:04:50, 2] smbd/open.c:open_file(247)
  Bo opened file Download/linux-2.4.21.SuSE-1.tar.bz2 read=Yes write=No
(numopen=1)
[2003/07/21 22:04:50, 2] smbd/close.c:close_normal_file(229)
  bo closed file Download/linux-2.4.21.SuSE-1.tar.bz2 (numopen=0)


When downloading the same file in Internet Explorer, Explorer displays an error
of this nature (translated
from danish), but completes the saving of the file:
    An error occurred when L: was connected to \\lserv1\diverse again.
    Microsoft Windows-network: The local unit name is already used.
    The connection has not been reestablished.

L: is my local drive letter connected to the samba share
"\\lserv1\diverse"

When opening the window "this computer" on the W2K client, the
connected drives is sometimes
marked with a red cross, and sometimes they are not. Not matter what, I'm
almost always able to "open"
the "drive".
Drive letters that is connected to shares on the W2K-server, never behaves like
this ?.

I have tried other kernels then the std. SuSE 8.2, like the Official vanilla
2.4.21, with and without
the 2.4.22-pre7 patch, but nothing changes.

First I thought that it maybe was some kind of hardware error that coursed the
problem, but as it's not the
first time I see this type of error (I have also seen it in other networks,
where Samba 2.2.3 and 2.2.7a was
in use, and almost always with W2K or XP clients), so I'm starting to wonder
about what's going on ?

My setup is:
    SuSE 8.2
    Samba 2.2.8a
    W2K Client
    
Samba conf:
# smb.conf is the main Samba configuration file. You find a full commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SuSE
# Date: 2003-07-01
[global]
    workgroup = NET
    netbios name = lserv1
    security = user
    valid users = @users
    domain logons = yes
    domain master = yes
    os level = 2
    time server = Yes
    unix extensions = Yes
    encrypt passwords = Yes
    map to guest = Bad User
    log level = 2
    syslog = 0
    printing = CUPS
    printcap name = CUPS
    socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
    veto files = /*.eml/*.nws/riched20.dll/*.{*}/

    character set = ISO8859-15
    client code page = 850
#   strict locking = yes
    oplocks = false
    logon script = brugere.bat
    wins support = yes
----------------------------------------------------
Any idears


Thanks in advance
Bo Jacobsen