Microsoft KB Archive/170619
Windows 95 ServiceProvider Priority Values Not Applied
The information in this article applies to:
- Microsoft Windows 95
- Microsoft Windows 95 OEM Service Release, versions 1, 2, 2.1
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, you should first make a backup copy of the registry files (System.dat and User.dat). Both are hidden files in the Windows folder.
When you configure the ServiceProvider Priority values in the registry to modify the DNS search order, the search order may not seem to be changed.
A ServiceProvider registry key exists (with associated registry values) at the following registry location:
However, the Winsock code incorrectly references the ServiceProvider registry key at the following location:
To resolve this issue, use either of the following methods:
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows 95. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
NOTE: For information about how to edit the registry, view the Changing Keys And Values online Help topic in Registry Editor (Regedit.exe). Note that you should make a backup copy of the registry files (System.dat and User.dat) before you edit the registry.
Create the registry key being referenced by Winsock. To do so, use the following steps:
Use Regedit.exe to open the following location:
- On the Edit menu, point to New, and then click Key. Name the new key MSTCP.
Click the new MSTCP key, point to New on the Edit menu, and then click Key. Name the new key ServiceProvider. The registry path should look like this:
Click the new ServiceProvider key, point to New on the Edit menu, and then click Binary Value. Create the following new binary values:
- DnsPriority - LocalPriority - HostsPriority - NetbtPriority.
- Set the priority values as appropriate.
This issue is resolved by the following updated file for Windows 95 and OSR2, and later versions of this file:
WSOCK32.DLL version 4.00.1112 dated 05/13/1997 66,560 bytes
A version of this file that resolves this problem is included in the Windows Sockets 2.0 update for Windows 95. For information about obtaining this update, see the following article in the Microsoft Knowledge Base:
Q182108 Availability of Windows Sockets 2.0 for Windows 95
Microsoft has confirmed this to be a problem in Microsoft Windows 95 and OEM Service Release 2 (OSR2). An update to address this problem is now available, but is not fully regression tested and should be applied only to computers experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft does not recommend implementing this update at this time. Contact Microsoft Technical Support for additional information about the availability of this update.
This issue is resolved in Microsoft Windows 98.
For additional information, see the following articles in the Microsoft Knowledge Base:
Q158474 Windows TCP/IP Registry Entries
Q139270 How to Change Name Resolution Order on Windows 95 and Windows NT
For additional information about issues resolved by updates to this component, please see the following articles in the Microsoft Knowledge Base:
Q169035 Windows 95 WinSock Update to Improve Multihoming Support
Q141211 Memory Leak with Multithreaded Winsock Programs
For additional information about Windows 95 updates, please see the following article in the Microsoft Knowledge Base:
Q161020 Implementing Windows 95 Updates
Additional query words:
Keywords : kbnetwork osr1 osr2 win95
Issue type : kbprb
Technology : kbWin95search kbOPKSearch kbWin95 kbWin95OPKOSR2 kbWin95OPKOSR1 kbWin95OPKOSR210
Last Reviewed: January 31, 2001