Hoping to find some nudging in the right direction with this issue. We cannot say exactly when this started, neither can the end users, but slowly certain functions of this custom FoxPro application have started to take 10-15 seconds to respond, when the response used to be instantaneous. The program will also hang periodically for each user, once a day or more.
All clients are Windows 7 Pro, Server is SBS2008, all machines connect at gigabit speed.
We have been working for a few weeks on the issue and tried a variety of fixes that resolved these types of issues for others. Some of the changes we have made are:
1. Disabling SMB2, enabling SMB1, disabling OpLocks on server/client
2. Installed various hotfixes = see attached
3. Reindexed the foxpro tables
4. Changed various settings on the NIC, interrupt moderation disabled, Jumbo Packet changed value from 1514 to 9014, Large Send Offload/TCP Connection Offload/TCP-UDP Checksum offload all disabled
5. Moved shared Foxpro data to a workstation and tested accessing - issue went away so we contacted Microsoft Suppor but haven't tested with multiple users accessing the data at once this way (currently in progress of testing this scenario)
6. Contacted Microsoft Critical Business Support - they did similar work to the above notes but also updated all TCP/IP dll's to most current version, took network logs on both server and client during the Application hang ups which their senior analysts looked at (weren't able to come up with anything specific, only that there was much more network traffic showing when FoxPro data was shared on the server vs when we did test it shared from a workstation) Microsoft is at the end of helping us due to FoxPro not being supported any longer. They stated this would be a "Best Effort" type situation.
7. A local cabling company did thorough test on network cabling - a few small issues were discovered and resolved but nothing major
I'm hoping others that have run into this with aging FoxPro applications can shed some light on what may be going on here.