This article was previously published under Q171567
This article has been archived. It is offered "as is" and will no longer be updated.
You may notice that changing the ServiceProvider priority values, asspecified in Knowledge Base article 139270, "How to Change NameResolution Order on Windows 95 and Windows NT," does not change thehostname resolution order as expected.
Unlike Windows NT 3.x, Windows NT 4.0 does not implement theServiceProvider priority values.
To resolve this problem, install the latest service pack for Windows NT.
For additional information about obtaining the latest Windows NT 4.0 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Windows NT 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 4.
Microsoft has confirmed that this is a problem in Windows NT 4.0.
In Windows NT 4.0 Service Pack 4, Microsoft added a new registry value tothe TCP/IP service that allows an administrator the option of changing thehostname resolution order. By default, hostname resolution is performed byDomain Name Service (DNS) first, followed by NetBIOS over TCP/IP (NetBT),if DNS fails. With the use of this registry value, the order of hostnameresolution can be reversed.
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To change the hostname resolution order (between DNS and NetBT nameresolution mechanisms), perform the following steps: