Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
"The network path was not found" error message when you start a LDAP-related application in Windows Server 2008 R2
Article ID: 2619880 - View products that this article applies to.
Consider the following scenario:
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
Microsoft System Center Configuration Manager 2007 Administration Console
Authorization Manager (AzMan)
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.
Hotfix informationAfter 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=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.
PrerequisitesTo 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:
(http://support.microsoft.com/kb/976932/ )Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry informationAfter 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
Then, go to the "Did this fix the problem?" section.
Let me fix it myselfTo do this, follow these steps:
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 requirementYou must restart any applications that are using the LDAP module after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
File informationThe 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 notesImportant 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.
For all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
Did this fix the problem?
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how to configure Remote Desktop IP Virtualization settings, visit the following Microsoft website:
How to configure Remote Desktop IP VirtualizationFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/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
Article ID: 2619880 - Last Review: December 21, 2011 - Revision: 2.0