Symptoms

Consider the following scenario:

  • You have a Windows Internet Name Service (WINS) server installed on a computer that is running Windows Server 2012 R2 or Windows Server 2008 R2 Service Pack 1 (SP1).

  • You try to add a multi-homed record (one host name and multiple IP addresses) on the WINS server by using the Netsh command.

  • The multi-homed record specifies a custom Endchar parameter together with a Group parameter. For example, you run the following command to create the record:

    netsh wins_server add name Name=TEST EndChar=35 IP={192.168.0.2,192.168.0.3} Group=3

In this scenario, the record has a name without an IP address, and the WINS server shows the record as released.

Cause

This issue occurs because of a missing check in the winsmon.dll file.

Resolution

To resolve this issue for Windows Server 2012 R2, install update rollup 2955164.

To resolve this issue for Windows Server 2008 R2 SP1, install the hotfix that is described in this article.

Update information

For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base:

2955164 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: May 2014

Hotfix information

A 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 website:

http://support.microsoft.com/contactus/?ws=supportNote 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.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.1.760 1.22xxx

    Windows Server 2008 R2

    SP1

    LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Winsmon.dll

6.1.7601.22619

142,336

07-Mar-2014

02:38

x64




Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates.

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2

File property

Value

File name

Amd64_c344509f2146f617fe1781813b03021a_31bf3856ad364e35_6.1.7601.22619_none_14eae746f1ab01cc.manifest

File version

Not applicable

File size

721

Date (UTC)

07-Mar-2014

Time (UTC)

08:14

Platform

Not applicable

File name

Amd64_microsoft-windows-i..aming-service-netsh_31bf3856ad364e35_6.1.7601.22619_none_75a2b33d154e6334.manifest

File version

Not applicable

File size

2,787

Date (UTC)

07-Mar-2014

Time (UTC)

05:40

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

1,680

Date (UTC)

07-Mar-2014

Time (UTC)

08:14

Platform

Not applicable


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×