Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have an application that uses DBF files - users run the application on their own machines and access the data on the server via a share. This application is installed on thousands of sites, with all combinations of Windows 2000/XP and Windows Server from 2000 up to 2008.

Some users (on multiple different sites) with Windows Server 2008 are now starting to get Windows 7 workstations and are reporting that some operations now take many times longer to complete with this configuration.

There's a known issue with SMB2 whereby it will corrupt the index files associated with DBFs, as well as MS Access tables and other things that utilise what could be described as legacy approaches to locking. So we generally force things back to SMB1.

Aside from that is there anything else at an OS / network transport level that would hammer performance in this scenario ?

share|improve this question
Silly question, but are they the same workstations they were using with windows 2000/XP or new workstations? – pablo Feb 10 '11 at 16:36
No they'd be new, running Win . Nothing else has changed. – Alan B Feb 10 '11 at 17:10

In windows 7 there is an option to run application in compatibility mode. Right click on the executable and navigate to COMPATIBILITY tab.

share|improve this answer
Thanks - the application runs fine, it's something at the network layer level in the OS is causing this. – Alan B Feb 10 '11 at 17:11
up vote 0 down vote accepted

To answer my own question:

Set Interrupt Moderation to Disabled on the network card advanced settings. Result – Major speed improvement, now up to what I would expect from a 100mbps LAN.

Interrupt Moderation is a feature intended to improve CPU performance by limiting the frequency at which the network stack interrupts the CPU to send network packets. In this case it’s obviously having the opposite effect - we want them sent and received right away.

This setting is present on a lot of current network cards apparently, including Realtek, Intel, Broadcom etc. although it might be driver dependent, ie. The stock HP or Dell driver might not have it but replacing that with the vendor supplied driver might make it available.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.