Search
Newsletter
r1215: File-locking on Windows 2000 Server
File-locking on Windows 2000 Server
Problem
You have Windows XP clients connected to a Windows 2000 Server. Users are experiencing problems with locked files. Files are locked for editing, but not unlocked, preventing the user from reopening the file for further editing.
Applies To
Microsoft Windows 2000 Server
Solution
This is a known issue with Windows XP clients on a Windows 2000 network. For more information go to:
http://www.win2000mag.net/Articles/Index.cfm?ArticleID=27148
This article also refers you to the following Microsoft Knowledge Base article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;q331519
(at the time of writing, this page is not available)
The change needed on the Windows 2000 Server is the following, taken from the Windows & .Net magazine site (www.win2000mag.net).
To temporarily work around the problem, you can disable SMB signing on servers that host resources for XP SP1 clients. To do so, you need to modify the Default Domain Controllers policy, a built-in policy that applies to all DCs. Open the Microsoft Management Console (MMC) Active Directory Users and Computers snap-in. Right-click the Domain Controllers organizational unit (OU), and click Properties. Click the Group Policies tab, select the Default Domain Controllers Policy, then click Edit. Expand the keys and navigate to Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options. Here, you will find four of Win2K’s SMB signing options, including
· Digitally sign client communication (always)
· Digitally sign client communication (when possible)
· Digitally sign server communication (always)
· Digitally sign server communication (when possible)
A default DC installation enables the last option, "Digitally sign server communication (when possible)." You turn off SMB signing on a DC by disabling this feature. If the last option isn't enabled, check the settings for the other three options and disable every enabled SMB option. At this point, you can wait 5 minutes for the automatic Group Policy refresh cycle, or you can manually refresh the policy on each DC with the command secedit/refreshpolicy machine_policy/enforce. The Microsoft article "Network File Errors Occur After You Install Windows XP SP1" at http://support.microsoft.com/default.aspx?scid=kb;en-us;q331519 documents this workaround.