Hi, we have updated our samba version from 3.0.20-something (SuSE packages) to 3.0.25b-33 (SerNet " " ) a few weeks ago.
Since we have done this update, some people are reporting
the following behavior. They open an M$-Access file and
after a few hours a messages is coming up, network connection error.
A reopen works without any fault. No data are lost.
What's the reason for this behavior ?
Can we change it ?
Any idea ?
Thanks!
Bye, Peer
Hardware: SUN X4100 (AMD64), SuSE SLES9 SP3
smb.conf:
------------
[global]
socket options = TCP_NODELAY SO_RCVBUF=65536 SO_SNDBUF=65536
netbios name = SNFS_1
interfaces = eth0
security = domain
password server = *
printing = cups
printcap name = cups
printcap cache time = 0
cups options = raw
printer admin = @ntadmin, root, administrator
map to guest = Bad User
log file = /var/log/samba/%m.log
read only = no
unix charset = UTF-8
display charset = UTF-8
----------
--
Mit freundlichem Gruss
Peer-Joachim Koch
_________________________________________________________
Max-Planck-Institut fuer Biogeochemie
Dr. Peer-Joachim Koch
Hans-Knöll Str.10 Telefon: ++49 3641 57-6705
D-07745 Jena Telefax: ++49 3641 57-7705
smime.p7s
Description: S/MIME Cryptographic Signature
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
