Win2K File Rename Bug Fix
Have you ever seen a Windows 2000 machine hang after you remotely attempt to change a file's name? According to the Microsoft article "File Server Stops Responding (Hangs) When You Rename a File" (, a coding error in the rename procedure can create a deadlock between two threads on the server, both of which wait forever for access to the file control block. When the server becomes unresponsive, a reboot will clear the deadlock. The reference doesn't state how frequently this problem occurs but indicates Microsoft Product Support Services (PSS) has a bug fix for the rename problem, a new version of ntfs.sys with a file release date of January 16, 2003. This subtle timing problem affects all Win2K versions.

Win2K DNS Update Corrects 2 Failures
The DNS service on all Win2K platforms through Win2K Service Pack 3 (SP3) might misbehave in unusual circumstances. When the DNS service encounters a parenthesis in a host record in the zone file, the service terminates and writes a System event-log message with event ID 7031 and the text “The DNS Server service terminated unexpectedly. It has done this x time(s). The following corrective action will be taken in 0 milliseconds: No Action.“ The DNS service might also lose its configuration settings when you delete and add several zones in a short time period. If either of these concerns applies to your operation, call PSS and ask for the latest version of dns.exe, with a file release date of January 30, 2003. The January 30 version supersedes two recent DNS post-Win2K SP3 updates released on January 16, 2003, and December 28, 2002. Cite the Microsoft articles "DNS Service Ends Unexpectedly and Event 7031 Error Message Appears" ( and "DNS Server Settings Are Lost When You Rapidly Delete and Re-Create a Directory Service Zone from a File" ( as references.

Win2K Refuses Incoming TCP Connections
Here’s another patch for unusual behavior. The Microsoft article "Windows 2000 Stops Accepting Incoming TCP Connections" ( states that a Win2K system might unexpectedly stop accepting incoming TCP connections but gives no reason for this behavior. This behavior might occur on file, print, or VPN servers. To diagnose this problem, display the state of the system’s TCP connections with the netstat –an command. If many of the connections are in a Closing state, you need to install the TCP bug fix. The fix updates five components: afd.sys, msafd.dll, tcpip.sys, tdi.sys and wshtcpip.dll. Most of the files have a December 2002 release date; the update is available only from PSS.

HP SecurePath Fills Up System Event Log
If you use Hewlett-Packard (HP) StorageWorks Secure Path storage subsystems, you need to be aware of an incompatibility problem between the Windows Workgroup Edition and Win2K SP3 systems. SP3 introduces a new SCSI command called Synchronize Cache. Because HP didn't update Secure Path to recognize the new command, Secure Path incorrectly assumes that a SCSI Synchronize Cache command indicates that a path to the disk array has failed (even though reads and writes to the disk function correctly). When Secure Path receives this command, it posts a message with event ID 7772 in the System event log. If the SCSI controller issues many of these commands, Secure Path can fill a 32MB event log with these messages in less than a minute. This problem occurs in RA4000 or RA4100 systems running Secure Path versions 3.1A and 3.1X, and in MSA1000 subsystems running Secure Path versions 3.1B and 4.0. If you use the MSA1000 storage system and Secure Path versions 3.1B or 4.0, you need to install the MSA1000 firmware upgrade plus the Secure Path software update. If you use RA4000 or RA4100 subsystems, you need to get a new host bus adapter (HBA) driver from HP. To avoid filling up the System event log, you need to update Windows Workgroups Secure Path subsystems before you upgrade to SP3. For more information, see the Microsoft article "Many Event ID 772 Entries Are Recorded with HP SecurePath Software ( You can read the HP customer advisory regarding this problem at|sanworks+securepath&source=oi021115_cw01.xml&dt=3&docid=13489.

Spooler Service Bug Fix
If you use a multiprocessor system as a print server, be aware that a bug in the spooler service might cause the system to crash when the server is extremely busy. Under stress, a function in the local spooler code incorrectly deletes the memory structure that defines the local printer port while the port is still in use. The patch contains new versions of four files: localspl.dll, spoolss.dll, win32spl.dll, and sp3res.dll; most of the files have a release date of January 15, 2003. You need to obtain this fix directly from PSS; cite as a reference the Microsoft article "The Spooler Service May Crash Under Stress" (