Microsoft KB Archive/170336
Article ID: 170336
Article Last Modified on 10/31/2006
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q170336
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.
You are able to access network resources from a command prompt; however, when you try to access network resources from Windows Explorer, you may experience one or more of the following problems:
- Double-clicking Network Neighborhood gives the following error:
- Clicking Start, clicking Run, typing <computer name>, and clicking OK results in the following error:
- From File Manager (Winfile.exe), none of the connect drive commands are present.
The Multiple Provider Router (Mpr.dll) cannot load any network providers from the registry.
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.
To resolve this issue, follow this procedure:
Start Registry Editor (Regedt32.exe) and go to the following key:
- On the Edit menu, click Add Value.
Enter the following value:
Value Name: ProviderOrder Data Type: REG_SZ Value: LanmanWorkstation
- This change should take effect without restarting Windows NT.
When Mpr.dll initializes, it reads the above registry key value. If Mpr.dll fails to get this information, it will return WN_NO_NETWORK, which produces the symptoms described above.
Keywords: kbnetwork KB170336