The number of WINS transaction log files on the WINS server greatly increases after you install Microsoft Security Bulletin MS04-031 on a Windows XP-based or Windows 2000-based WINS client
On This PageSYMPTOMSYou install Microsoft Security Bulletin MS04-031 on a Microsoft Windows XP Professional-based or Microsoft Windows 2000 Professional-based client that is running Windows Internet Name Service (WINS). If the client uses the Clipboard Viewer program (Clipbrd.exe) or any other Network Dynamic Data Exchange (NetDDE)-based program, the number of WINS transaction log files on the WINS server greatly increases. Additionally, these log files occupy lots of disk space. Note The WINS transaction, or J<n>, log files are located in the %systemroot%\System32\Wins folder. %systemroot% is the folder where you installed Microsoft Windows. If you use the Network Monitor utility to capture a network trace, the network trace shows excessive registration and de-registration traffic for the NetDDE service on WINS clients. The WINS clients register and unregister the NetDDE service with the WINS server several hundred times per second. This activity loads down the WINS server. CAUSEThis problem occurs because of a code defect in the NetDDE service on WINS clients. This defect is introduced with Security Bulletin MS04-031. RESOLUTIONHotfix information for Windows XPA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support) Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesWindows XP Professional Service Pack 1 (SP1) or Windows XP Professional SP2Restart requirementYou do not have to restart your computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Windows XP Professional SP1, 32-bit versions
Date Time Version Size File name
--------------------------------------------------------------
10-Feb-2005 17:10 5.1.2600.1621 16,384 Nddenb32.dll
Windows XP Professional SP2, 32-bit versionsDate Time Version Size File name -------------------------------------------------------------- 10-Feb-2005 17:26 5.1.2600.2608 18,944 Nddenb32.dll Windows XP Professional SP1, 64-bit versions
Date Time Version Size File name Platform
----------------------------------------------------------------------------
10-Feb-2005 08:07 5.1.2600.1621 39,936 Nddenb32.dll IA-64
10-Feb-2005 08:10 5.1.2600.1621 16,384 Wnddenb32.dll x86
Hotfix information for Windows 2000A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support) Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesWindows 2000 Professional SP3 or Windows 2000 Professional SP4Restart requirementYou do not have to restart your computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Date Time Version Size File name -------------------------------------------------------------- 01-Mar-2005 21:55 5.0.2195.7035 17,168 Nddenb32.dll 25-Feb-2005 17:43 6.1.22.4 371,936 Updspapi.dll STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONThe following is an example of the name registration and of the name release that are displayed when you use the Network Monitor utility: NBT: NS: Registration req. for NETBIOSNAME <1F> NBT: NS: Registration (Node Status) resp. for NETBIOSNAME <1F>, Success, Owner Addr. 10.10.10.10 NBT: NS: Release req. for NETBIOSNAME <1F> NBT: NS: Release (Node Status) resp. for NETBIOSNAME <1F>, SuccessAll NetBIOS names are 16 characters in length. A NetBIOS suffix is the 16th character in the 16-character NetBIOS name. The NetBIOS suffix is used by Microsoft networking software to identify functionality that is installed on the registered device. 1F is the unique NetBIOS suffix that is used by the NetDDE service. For additional information about NetBIOS suffixes, click the following article number to view the article in the Microsoft Knowledge Base: 163409 (http://support.microsoft.com/kb/163409/)
NetBIOS suffixes (16th character of the NetBIOS name)
For additional information about the Jet database for Microsoft Windows NT 4.0, click the following article number to view the article in the Microsoft Knowledge Base:
165915 (http://support.microsoft.com/kb/165915/)
Explanation of Jet Database for Windows NT 4.0
For additional information about Microsoft Security Bulletin MS04-031, click the following article number to view the article in the Microsoft Knowledge Base:
841533 (http://support.microsoft.com/kb/841533/)
MS04-031: Vulnerability in NetDDE could allow remote code execution
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:816915 (http://support.microsoft.com/kb/816915/) New file naming schema for Microsoft Windows software update packages 824684 (http://support.microsoft.com/kb/824684/) Description of the standard terminology that is used to describe Microsoft software updates
| Article Translations
|
Back to the top
