This week, I provide a summary of five recently released Windows 2000 Service Pack 3 (SP3) bug fixes, including a fix for a DHCP reservation problem, a workaround you can use to force a domain controller (DC) to immediately replicate an account you disable, an update that corrects a blue screen that occurs when you close a file on a network share, a solution for a Win2K Server Terminal Services client printing problem I discussed a few weeks ago, and a code fix that eliminates Perflib error messages in the Application Event Log.
Several readers reported that after upgrading to SP3, they experienced problems displaying DHCP reservations using the Microsoft Management Console (MMC) DHCP snap-in. Although a SP3 DHCP server manages client reservations correctly, a bug in the snap-in code prevents the server from displaying reservations when a scope has more than 100 active reservations. You can correct the problem by installing the latest version of dhcpsnap.dll, which has a file release date of September 11. You need to install this update on all systems on which you run the MMC DHCP snap-in to display client reservation information. The update is available only from Microsoft Product Support Services (PSS). To learn more about this problem, see the Microsoft article "The Windows 2000 SP3 DHCP Tool May Show an Empty Reservations List" at http://support.microsoft.com/default.aspx?scid=kb;en-us;q328636.
Disabled Account Does Not Replicate Immediately
SP3 contains several code changes that cause DCs to replicate immediately (urgent replication) when you modify selected fields in Active Directory (AD). Urgent replication causes a DC to immediately request replication with other DCs in the same site. In SP3, changing a user’s password generates an urgent replication event. Unfortunately, disabling an account doesn't trigger an urgent replication, which can have potentially serious consequences. If DCs within a site don't propagate the disabled account status immediately, a user can potentially log on to another DC and access the network until the authenticating DC receives the updated information during a regular replication cycle.
A workaround exists that you can use to force DCs to replicate the change in the account status immediately. Because a password reset triggers an urgent replication, first disable the account and then reset the account’s password. This sequence causes the authenticating DC to replicate both the disabled account status and the password change. No bug fix is available for this problem, so make this extra step part of the standard routine when you disable an account. Read the Microsoft article "Urgent Replication Is Not Triggered When You Turn Off an Account" at http://support.microsoft.com/default.aspx?scid=kb;en-us;q325217.
Blue Screen Closing a Remote File
An error in SP3 can cause a system to blue screen with a stop code of 0x000000C2 when you close a file located in a network share. The reference article doesn't provide a reason for the problem but does indicate Microsoft has a fix, a new version of mrxsmb.sys, with a file release date of September 4, and a new version of rdbss.sys with a file release date of August 23. This update is available from PSS. For details, see the Microsoft article "A 'Stop 0x000000C2' Error Occurs When You Try to Close a File on a Network Share" at http://support.microsoft.com/default.aspx?scid=kb;en-us;q328776.
Terminal Services Printing Problem
A printing problem occurs when a Terminal Services client prints a file located on a network share. If the client submits the print request using the Universal Naming Convention (UNC) share name (e.g., print \\server\share\file.doc), the spooler correctly processes and prints the document. However, if the client references the file using the driver letter of the mapped share (e.g., print m:\file.doc where m is mapped to \\server\share), the print job fails because the Terminal Services server incorrectly uses the Terminal Services port number as the filename. The bug fix that corrects this problem contains three revised components: printui.dll, winspool.drv, and winotify.dll; all the files have a release date of August 15. The Microsoft article "Redirected Printing Through a Terminal Services Session May Not Work with Windows 2000 SP3" at http://support.microsoft.com/default.aspx?scid=kb;en-us;q328020 contains a sample event log message you can use to confirm this problem on your Terminal Services server and a workaround you can use until you apply the fix.
Perflib Errors in the Application Event Log
Have you noticed Perflib error messages in the Application Event Log on DCs that you've upgraded to SP3? Microsoft published a fix for this problem just last week. Although information about the source of the problem is scanty, you can get rid of the error messages by updating four kernel files: ntkrnlmp.exe, ntkrnlpa.exe, ntkrpamp.exe, and ntoskrnl.exe. All four files have a release date of September 24, and the fix is only available from PSS.
For more information, see the Microsoft article "Event ID 3006 in Application Log After You Upgrade Your Domain Controller to Service Pack 3" at http://support.microsoft.com/default.aspx?scid=kb;en-us;q328556.