2008 R2 SMB2 problem with files getting locked
Since migrating our file server to 2008 R2 we are having a problem with asp files getting locked. The file servers host a shared configuration used by the web servers. What we are seeing is that if someone edits a page (such as index.asp) and tries to save it, they are getting sharing violations or access denied if anyone hits that page with a browser at the same time. 5 or 10 seconds later it will allow them to save. This seems to happen with just about any text editor including notepad but it only seems to happen for .asp files and it only seems to happen on WXP, not W7. The old file servers had oportunitistic locking disabled which apparently doesnt work in 2008 R2. We tried to disable SMB2 on the web servers (clients) which seemed to fix the problem but then the web servers started going up and down continously trying to access the file server. We do have oportunitistic locking disabled on the file server but since that settings doesnt seem to work for SMB2, Im not sure what we can do to fix the problem. Another syptom of this problem is that our W7 users using Dreameaver and connecting to the websites via CPS are seeing a slightly different problem. If they have an asp file checked out and try to check it back in, it will fail if anyone has that page open in a browser. They can retry all day long but as long as someone has the page open in a browser, it will never let them check it back in. On a high traffic website, this is not going to work. Any ideas?
August 17th, 2011 7:23pm

Take closer look with Process Monitor from Sysinternals. (Set time format into more readable one and you can filter logging by taking only relevat processes.)
Free Windows Admin Tool Kit Click here and download it now
August 19th, 2011 11:26am

Dave, Did you ever find a solution to this? /Per
March 30th, 2012 2:25am

This is a compatability issue between SMB and SMB2. Unfortunately Microsoft Support gave no indication that this would ever be fixed. We eventually came up with our own workaround. WXP machines that saw the problem were upgraded to W7 so it was using SMB2 on both ends. The W7 machines that were seeing the issue were only because the contribute publishing server they were using to get to the 2008 file server was actually a Windows 2003 server which again uses SMB. We moved CPS to 2008 to eliminate that problem as well.
Free Windows Admin Tool Kit Click here and download it now
March 30th, 2012 8:19am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics