Windows 95 ServiceProvider Priority Values Not Applied

Last reviewed: June 25, 1997
Article ID: Q170619
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.

SYMPTOMS

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.

CAUSE

A ServiceProvider registry key exists (with associated registry values) at the following registry location:

   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\
   ServiceProvider

However, the Winsock code incorrectly references the ServiceProvider registry key at the following location:

   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSTCP\
   ServiceProvider

RESOLUTION

To resolve this issue, use either of the following methods:

Method 1

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:

  1. Use Regedit.exe to open the following location:

          HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
    

  2. On the Edit menu, point to New, and then click Key. Name the new key MSTCP.

  3. 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:

          HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSTCP\
          ServiceProvider
    

  4. 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.
    

  5. Set the priority values as appropriate.

Method 2

Obtain the update mentioned in the "Status" section of this article. This update causes Winsock to reference the correct location for the ServiceProvider key in the registry.

STATUS

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 mplementing this update at this time. Contact Microsoft Technical Support for additional information about the availability of this update.

MORE INFORMATION

For additional information, see the following articles in the Microsoft Knowledge Base:

    ARTICLE-ID: Q158474
    TITLE     : Windows 95 TCP/IP Registry Entries

    ARTICLE-ID: Q139270
    TITLE     : How to Change Name Resolution Order on Windows 95 and
                Windows NT


Additional query words: 95
Keywords : kbnetwork osr1 osr2 win95 kbfixlist
Version : 95
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.