Windows Sockets 2.0 Does Not Use DnsNbtLookupOrder Value

ID: Q216470

The information in this article applies to:

Microsoft Windows 98
Microsoft Windows 95

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.

SYMPTOMS

With Windows Sockets 2.0 (Winsock 2) installed, the registry entries for controlling name resolution order have no effect. Name resolution is carried out first using DNS and then using NetBIOS, even if the DNS resolution is successful.

Note that Winsock 2 is optional in Windows 95, which is initially configured with Windows Sockets 1.1, but is the default in Windows 98.

CAUSE

The Winsock 2 technology does not incorporate the name resolution provider ordering control that is a part of Winsock 1.1. Additionally, Winsock 2 as implemented for both Windows 95 and Windows 98 does not incorporate the registry control specified and provided for in the Microsoft Windows NT implementation.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft Windows 98 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

All localized versions of this fix should have the following file attributes or later:


   Date     Time    Version      Size    File name   Platform
   ------------------------------------------------------------
   03/03/99 2:59pm  4.10.2002    44,032  Rnr20.dll   Windows 98
   05/23/99 5:02pm  4.10.1662    43,520  Rnr20.dll   Windows 95

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

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. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

The registry control specified and provided for in the Windows NT implementation is:

Key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP
Value: DnsNbtLookupOrder
Type: DWORD
Notes: 0 = DNS first, 1 = NBT first

NOTE: If the value is not in the registry, DNS is queried first.

For additional information about Winsock 2 and Windows 95, please see the following article in the Microsoft Knowledge Base:

Q182108 Availability of Windows Sockets 2.0 for Windows 95

For additional information about registry entries and Windows Sockets, please see the following articles in the Microsoft Knowledge Base:

Q158474 Windows TCP/IP Registry Entries

Q170619 Windows 95 ServiceProvider Priority Values Not Applied

Additional query words: DNS lookup order WINS winsock 2.0 name resolution netbios tcp/ip

Keywords : kbenv kbnetwork win95 win98
Version : WINDOWS:95
Platform : WINDOWS
Issue type : kbprb