"The network path was not found" error message when you start a LDAP-related application in Windows Server 2008 R2

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

On This Page

SYMPTOMS

Consider the following scenario:
  • You install the Remote Desktop Session Host role service on a computer that is running Windows Server 2008 R2.
  • You enable Remote Desktop IP Virtualization on the computer.
  • You try to start a Lightweight Directory Access Protocol (LDAP)-related application or LDAP-related service on the computer.
In this scenario, you cannot start the application or service, and you receive the following error message:

The network path was not found

Here are some sample LDAP-related applications that are affected by the issue:

Active Directory Users and Computers MMC snap-in
Active Directory Domain and Trusts MMC snap-in
Active Directory Sites and Services MMC snap-in
ADSI Edit MMC snap-in
Group Policy Management MMC snap-in
DHCP MMC snap-in
Ldp.exe
Microsoft System Center Configuration Manager 2007 Administration Console
Authorization Manager (AzMan)

CAUSE

The issue occurs because of a compatibility issue between LDAP and Remote Desktop IP Virtualization.

The LDAP module's hard-coded behavior is to use an internal socket that is bound to the IP address 127.0.0.1. However, Remote Desktop IP Virtualization rebinds the socket to a virtualized IP for the session or the program. This behavior causes a connection failure in the LDAP component.

RESOLUTION

Hotfix information

After you install the following hotfix and configure a registry subkey, the LDAP module will bind and connect an internal socket to any loopback address that is provided in the registry by a user. The address provided must be a loopback address (the address starts with 127) and should not be 127.0.0.1. 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 Windows Server 2008 R2 or Windows Server 2008 R2 Service Pack 1 (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

After apply this hotfix, you must create a registry key.

To have us create the registry key for you, go to the "Fix it for me" section. If you prefer to create the registry key yourself, go to the "Let me fix it myself" section.

Fix it for me



To fix this problem automatically, click the Fix it button or link. Then click Run in the File Download dialog box, and follow the steps in the Fix it wizard.


Fix this problem
Microsoft Fix it 50808


Notes
  • Please download and install the hotfix in above Knowledge Base (KB) article before you run the Fix it solution.
  • You must restart any applications that are using the LDAP module after you apply this hotfix.
  • This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
  • If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.

Then, go to the "Did this fix the problem?" section.



Let me fix it myself

To do this, follow these steps:
  1. Click Start
    Collapse this imageExpand this image
    start button
    , type regedit in the Search programs and files box, and then press ENTER.
    Collapse this imageExpand this image
    UAC
    If you are prompted for an administrator password, type the password. If you are prompted for confirmation, provide confirmation.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ldap\
  3. On the Edit menu, point to New, and then click String Value.
  4. Type IPv4LoopbackAlternative, and then press ENTER.
  5. Right-click IPv4LoopbackAlternative, and then click Modify.
  6. In the Value data box, type 127.0.0.2, and then click OK.
  7. Exit Registry Editor.

Note We recommend that you use 127.0.0.2 in the Value data field, but anything in the range of 127.0.0.2 through 127.255.255.254 (inclusive) is acceptable.

Restart requirement

You must restart any applications that are using the LDAP module after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

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.
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 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:
    Collapse this tableExpand this table
    VersionProductMilestoneService branch
    6.1.760 0.21xxxWindows Server 2008 R2RTMLDR
    6.1.760 1.21xxxWindows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. 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
Wldap32.dll6.1.7600.21057312,83218-Sep-201101:45x64
Wldap32.dll6.1.7601.21822312,83218-Sep-201103:05x64
Wldap32.dll6.1.7600.21057269,31218-Sep-201101:07x86
Wldap32.dll6.1.7601.21822270,33618-Sep-201102:41

Did this fix the problem?

  • Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support.
  • We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me" blog or send us an email.

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 how to configure Remote Desktop IP Virtualization settings, visit the following Microsoft website:
How to configure Remote Desktop IP Virtualization
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 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_5305f7a1f95355c3ec741daec9cd5a2b_31bf3856ad364e35_6.1.7601.21822_none_8cb2d34be02cf135.manifest
File versionNot applicable
File size703
Date (UTC)18-Sep-2011
Time (UTC)06:02
PlatformNot applicable
File nameAmd64_b60b5cbf24fec97a49d44e4683828ccd_31bf3856ad364e35_6.1.7601.21822_none_39b0d1b5e246b7e7.manifest
File versionNot applicable
File size1,046
Date (UTC)18-Sep-2011
Time (UTC)06:02
PlatformNot applicable
File nameAmd64_c3d06b01daf73185259bfc94cdb45eef_31bf3856ad364e35_6.1.7600.21057_none_cd3d7ea01052b4cc.manifest
File versionNot applicable
File size703
Date (UTC)18-Sep-2011
Time (UTC)06:02
PlatformNot applicable
File nameAmd64_c767e639018f581b698cd2c5693fbc0f_31bf3856ad364e35_6.1.7600.21057_none_2ad3a4985c7e1c4e.manifest
File versionNot applicable
File size1,046
Date (UTC)18-Sep-2011
Time (UTC)06:02
PlatformNot applicable
File nameAmd64_microsoft-windows-ldap-client_31bf3856ad364e35_6.1.7600.21057_none_4fdd280189205e2c.manifest
File versionNot applicable
File size13,962
Date (UTC)18-Sep-2011
Time (UTC)02:16
PlatformNot applicable
File nameAmd64_microsoft-windows-ldap-client_31bf3856ad364e35_6.1.7601.21822_none_51df1d1d8632c177.manifest
File versionNot applicable
File size13,962
Date (UTC)18-Sep-2011
Time (UTC)04:22
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size3,215
Date (UTC)18-Sep-2011
Time (UTC)06:02
PlatformNot applicable
File nameX86_microsoft-windows-ldap-client_31bf3856ad364e35_6.1.7600.21057_none_f3be8c7dd0c2ecf6.manifest
File versionNot applicable
File size13,956
Date (UTC)18-Sep-2011
Time (UTC)01:42
PlatformNot applicable
File nameX86_microsoft-windows-ldap-client_31bf3856ad364e35_6.1.7601.21822_none_f5c08199cdd55041.manifest
File versionNot applicable
File size13,956
Date (UTC)18-Sep-2011
Time (UTC)03:12
PlatformNot applicable

Properties

Article ID: 2619880 - Last Review: December 21, 2011 - Revision: 2.0
APPLIES TO
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Foundation
  • Windows Server 2008 R2 Standard
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbexpertiseadvanced kbsurveynew kbfixme kbmsifixme KB2619880

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