[Samba] Reliable Build (Was Re: Samba and Excel corruption)

[Dan Horth]

Hi - I've been running a samba 2.2.1a server for some time now, with no evident problems regarding file corruption or other information loss. I'm in the process of moving samba to a different server - both running on Intel based hardware, Redhat 7.2 with all errata applied.

I have been having some odd problems with profiles, printing, and printer driver setup / downloading and was considering upgrading to 2.2.3a in an attempt to remedy these and improve overall reliability.

I was wondering if anyone could share any horror or success stories with either of these builds - or even suggest whichmight be the best build to use to service a small number of mixed clients - Win98 and NT4 with one 2000 and oneXP laptop. I'd rather server stability and reliability to "sysadmin conveniences", while maintaining best interoperability with the variety of clients.

I'm planning on building and testing the SAMBA_2_2 branch from samba CVS tomorrow - but cannot afford to invest thetimeright now if there are known reliability / data integrity problems.

Any advice would be appreciated. Even short references to specific problems (ie word 2000 file corruption with 2.2.3) if they're known issues will help enormously in my research and decision. I'd be glad to summarise replies to individuals or the list if desired.

Thanks in advance, Dan.


Re:
>I read with great interest your post to the Samba mailing list about Excel
>files corrupting on a Samba share.
<snip>
>Any attempt to open the recently saved file causes Excel to complain that
>the data is not in a recognized format.

and

>I am running Samba 2.2.3 on Red Hat 7.2 with Win XP work stations.
>
>Everything is working fine except for when I try to save a file from Word 2000
>to a share on Samba.  The file saves OK but will not re-open, I get the error