Stuart McLachlan
stuart at lexacorp.com.pg
Mon Feb 14 21:27:08 CST 2011
Could it be something to do SMB2. I've just come across this in another context and was pointed to http://www.alaska-software.com/fixes/smb2/overview.shtm "With the advent of Windows Vista and Windows 7, Microsoft introduced a new network protocol (SMB2) to optimize file sharing for WAN and low bandwidth and high latency scenarios. To optimize these types of file access scenarios, Microsoft performed design decisions which lead to the inability of the new SMB2 protocol to handle cache coherency of file meta information such as the file size, the last update time and whether the file actually exists on the server ("file not found" status). As a result of this design decision made by Microsoft, the SMB2 protocol with its default configuration breaks any application relying on shared, concurrent data access. It is therefore absolutely required to reconfigure the SMB2 cache of the local workstation to not cache file meta information. Alaska Software provides to its customers and their end-users an MSI installation package which reconfigures the SMB2 cache accordingly. This MSI package needs to be executed on any Vista and Windows 7 workstation in a network to ensure that no data loss or data corruption occurs when accessing files concurrently." -- Stuart On 15 Feb 2011 at 6:18, Dros, David J. wrote: > Urgent help!! > Has anyone encountered this? Acc 2003 FE/BE on brand new network. > Clients running xp. Top of the line hardware etc. Cat 6 gig drops > /nics etc. File transfer speed lightning fast. BE sitting on a brand > new $25k nas running windows storage server 2008 64bit. Queries that > write to the database take minutes vs seconds on old 10/100mb network > of xp clients against single 10yr old sever 2003 fileserver. We are > handcuffed in the middle of an overseas deployment. Any help or > referals would be greatly appreciated. Thank you. >