Like every other website on the planet, SmallNetBuilder uses cookies. Our cookies track login status, but we only allow admins to log in anyway, so those don't apply to you. Any other cookies you pick up during your visit come from advertisers, which we don't control.
If you continue to use the site, you agree to tolerate our use of cookies. Thank you!

Router Charts

Click for Router Charts

Router Ranker

Click for Router Ranker

NAS Charts

Click for NAS Charts

NAS Ranker

Click for NAS Ranker

More Tools

Click for More Tools

NAS Features

Options

Unfortunately, most NASes take the all-on or all-off approach to oplocks, for various reasons. One vendor that I checked with pointed to problems with certain versions of Samba and also certain applications, so has defaulted its product to opplocks-off, but offers an add-on for users who want them enabled. This same vendor plans to change the default to enabling oplocks in an upcoming firmware update, but will provide an option in its management GUI to disable them.

Another NAS vendor defaults its products to oplocks-on for all shares, but offers a "database optimization" mode to disable oplocks on all shares. Yet another vendor started with having its NAS default to enabling oplocks, but changed the default to disable after experiencing problems oplocks getting stuck on when clients disconnected before closing an opened file. This vendor is currently evaluating alternative approaches.

Since it is Windows clients (or to be specific, clients running the SMB protocol) that set the oplocks, one would hope that this feature could be disabled there. This Microsoft KB article describes the Registry edits to do just that, except for Vista. (If you need the regedits for Win NT, use this KB article.) To further complicate the issue, Microsoft introduced a new version of the SMB protocol—SMB2—in Vista, which does not allow oplocks to be disabled.

So, what's the bottom line? Don Capps' advice above seems to provide a good set set of recommendations. Unfortunately, most consumer NASes don't provide share-by-share control of oplocks. So the next best thing seems to be the path that many NAS vendors are taking; disabling oplocks. This seems to minimize application-specific NAS problems and has the benefit of improved throughput.

Since vendors don't provide information on their oplock approach, however, you may have to experiment for yourself by using the Windows Registry hacks referenced above and doing your own testing. I'm interested in what you find, so post a comment and share your results.

More NAS

Wi-Fi System Tools
Check out our Wi-Fi System Charts, Ranker and Finder!

Support Us!

If you like what we do and want to thank us, just buy something on Amazon. We'll get a small commission on anything you buy. Thanks!

Over In The Forums

Hello all,A couple of problems have developed with my AC86U, running 384.14_2.Firstly, I have a USB pen drive plugged into the USB 2.0 port, which hos...
Hello,I am using an old Merlin firmware on my RT-N66U Assus router: 3.0.0.4.374.34_2 (Merlin build).Since this is a very old version and updated firmw...
Hello,I have been away from this forum for a few years since I had decided togo back to Asus stock firmware for various ASUS routers namely these whic...
Hi I upgraded to firmware version 3.0.0.4.384_81981 today and I am experiencing lots of disconnections/reboots. Output from the log attached. If any...
I'm running an AiMesh setup with one RT-AX88U as main and one AC86U and AC68U as nodes. Backhaul is wireless. All three running 384.14 beta 3 firmware...

Don't Miss These

  • 1
  • 2
  • 3