A Windows Server 2008 domain controller or a Windows Server 2008 R2 domain controller cannot allocate new ports when Server for NIS is running

Article translations Article translations
Article ID: 980027 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

You run the Server for Network Information Service (NIS) service on an Active Directory Domain Services (AD DS) domain controller that is running Windows Server 2008 or Windows Server 2008 R2. When multiple clients connect to the Server for NIS server, the domain controller cannot allocate new ports. Therefore, the domain controller cannot open new network connections. For example, you experience one or more of the following issues:
  • When you run the Ypcat utility on the domain controller, you receive the following error message:
    Cannot set socket option SO_BROADCAST: 10055
  • The snap-in for the domain controller cannot start. For example, the Active Directory Users and Computers snap-in or the Domain Name System (DNS) management snap-in cannot start.

CAUSE

When the Server for NIS service closes a client connection, the socket that is associated with the connection is not closed. Therefore, the port that is associated with the socket remains open. When multiple connections are initiated, the Server for NIS service exhausts all available ports. In this situation, the issue that is described the "Symptoms" section occurs.

RESOLUTION

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 the problem described in this article. 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
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.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows Server 2008 R2
Additionally, you must have the Server for NIS service installed. For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849 How to obtain the latest service pack for Windows Server 2008

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) 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.
Windows Server 2008 file information notes
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.0.600 1 . 22xxxWindows Server 2008SP1LDR
    6.0.600 2 . 22xxxWindows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxx version number.
  • 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 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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 x86-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Nis2ad.exe6.0.6001.22623126,97602-Feb- 201013:00
Nisad.dll6.0.6001.22623208,89602-Feb- 201015:33
Nisadmin.exe6.0.6001.22623153,60002-Feb- 201013:00
Nisadres.dll6.0.6001.22623118,27202-Feb- 201011:17
Niscnfg.exe6.0.6001.22623157,69602-Feb- 201013:00
Nismap.exe6.0.6001.22623128,00002-Feb- 201013:00
Nissvc.dll6.0.6001.22623237,05602-Feb-201015:32
Snis-ppdlic.xrm- msNot Applicable3,14802-Feb-201015:11
Ypcat.exe6.0.6001.22623151,55202-Feb- 201013:00
Ypmatch.exe6.0.6001.22623151,04002-Feb- 201013:00
Yppush.exe6.0.6001.22623157,69602-Feb- 201013:00
Nis2ad.exe6.0.6002.22327126,97602-Feb- 201012:43
Nisad.dll6.0.6002.22327208,89602-Feb- 201015:12
Nisadmin.exe6.0.6002.22327153,60002-Feb- 201012:43
Nisadres.dll6.0.6002.22327118,27202-Feb- 201011:10
Niscnfg.exe6.0.6002.22327157,69602-Feb- 201012:43
Nismap.exe6.0.6002.22327128,00002-Feb- 201012:43
Nissvc.dll6.0.6002.22327236,03202-Feb-201015:12
Snis-ppdlic.xrm- msNot Applicable3,14802-Feb-201014:47
Ypcat.exe6.0.6002.22327151,55202-Feb- 201012:43
Ypmatch.exe6.0.6002.22327151,04002-Feb- 201012:43
Yppush.exe6.0.6002.22327157,69602-Feb-201012:43
For all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Nis2ad.exe6.0.6001.22623128,00002-Feb- 201013:20
Nisad.dll6.0.6001.22623232,44802-Feb- 201015:58
Nisadmin.exe6.0.6001.22623157,69602-Feb- 201013:20
Nisadres.dll6.0.6001.22623118,27202-Feb- 201011:17
Niscnfg.exe6.0.6001.22623166,91202-Feb- 201013:20
Nismap.exe6.0.6001.22623129,02402-Feb- 201013:20
Nissvc.dll6.0.6001.22623260,09602-Feb-201015:58
Snis-ppdlic.xrm- msNot Applicable3,14802-Feb-201015:35
Ypcat.exe6.0.6001.22623157,69602-Feb- 201013:20
Ypmatch.exe6.0.6001.22623156,67202-Feb- 201013:20
Yppush.exe6.0.6001.22623164,86402-Feb- 201013:20
Nis2ad.exe6.0.6002.22327128,00002-Feb- 201012:55
Nisad.dll6.0.6002.22327232,44802-Feb- 201015:11
Nisadmin.exe6.0.6002.22327157,69602-Feb- 201012:55
Nisadres.dll6.0.6002.22327118,27202-Feb- 201011:11
Niscnfg.exe6.0.6002.22327166,91202-Feb- 201012:55
Nismap.exe6.0.6002.22327129,02402-Feb- 201012:55
Nissvc.dll6.0.6002.22327249,85602-Feb-201015:11
Snis-ppdlic.xrm- msNot Applicable3,14802-Feb-201014:53
Ypcat.exe6.0.6002.22327157,69602-Feb- 201012:55
Ypmatch.exe6.0.6002.22327156,67202-Feb- 201012:55
Yppush.exe6.0.6002.22327164,86402-Feb-201012:55
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • 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 and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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 of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Nisnotfy.mofNot Applicable55210-Jun-200921:08Not Applicable
Nispush.mofNot Applicable67510-Jun-200921:08Not Applicable
Nisremot.mofNot Applicable65910-Jun-200921:08Not Applicable
Nissvc.dll6.1.7600.20735251,90416-Jun-201006:11x64
Snis-ppdlic.xrm-msNot Applicable2,98116-Jun-201006:35Not Applicable
Snis_namespace.mofNot Applicable12110-Jun-200921:08Not Applicable
Snis_provreg.mofNot Applicable49810-Jun-200921:08Not Applicable
Ypcat.exe6.1.7600.20735159,23216-Jun-201006:06x64
Ypmatch.exe6.1.7600.20735158,20816-Jun-201006:06x64
Yppush.exe6.1.7600.20735165,88816-Jun-201006:06x64

WORKAROUND

To work around this issue, restart either the Server for NIS service or the domain controller.

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

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameX86_microsoft-windows-server-for- nis_31bf3856ad364e35_6.0.6001.22623_none_497256207d63991e.manifest
File versionNot Applicable
File size275,197
Date (UTC) 02-Feb-2010
Time (UTC)20:22
File nameX86_microsoft-windows-server-for- nis_31bf3856ad364e35_6.0.6002.22327_none_4b5cc9307a86539e.manifest
File versionNot Applicable
File size275,178
Date (UTC) 02-Feb-2010
Time (UTC)18:10
Additional files for all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameAmd64_microsoft-windows-server-for- nis_31bf3856ad364e35_6.0.6001.22623_none_a590f1a435c10a54.manifest
File versionNot Applicable
File size275,237
Date (UTC) 02-Feb-2010
Time (UTC)17:43
File nameAmd64_microsoft-windows-server-for- nis_31bf3856ad364e35_6.0.6002.22327_none_a77b64b432e3c4d4.manifest
File versionNot Applicable
File size275,218
Date (UTC) 02-Feb-2010
Time (UTC)16:44

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_db27440e4a5f8bee33ed9f0a91d58825_31bf3856ad364e35_6.1.7600.20735_none_00459b2d6ba59ae3.manifest
File versionNot Applicable
File size706
Date (UTC)16-Jun-2010
Time (UTC)10:31
PlatformNot Applicable
File nameAmd64_microsoft-windows-server-for-nis_31bf3856ad364e35_6.1.7600.20735_none_a5aff29196de95db.manifest
File versionNot Applicable
File size280,918
Date (UTC)16-Jun-2010
Time (UTC)10:31
PlatformNot Applicable
File namePackage_1_for_kb980027~31bf3856ad364e35~amd64~~6.1.1.0.mum
File versionNot Applicable
File size1,806
Date (UTC)16-Jun-2010
Time (UTC)10:31
PlatformNot Applicable
File namePackage_for_kb980027_rtm~31bf3856ad364e35~amd64~~6.1.1.0.mum
File versionNot Applicable
File size1,437
Date (UTC)16-Jun-2010
Time (UTC)10:31
PlatformNot Applicable

Properties

Article ID: 980027 - Last Review: October 10, 2011 - Revision: 3.0
APPLIES TO
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 Standard without Hyper-V
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Standard
Keywords: 
kbqfe kbHotfixServer kbsurveynew kbautohotfix kbexpertiseinter kbbug kbfix KB980027

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com