Microsoft KB Archive/171567: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
Line 45: | Line 45: | ||
== SYMPTOMS == | == SYMPTOMS == | ||
You may notice that changing the ServiceProvider priority values, as specified in Knowledge Base article '''[[../139270|139270]]''', | You may notice that changing the ServiceProvider priority values, as specified in Knowledge Base article '''[[../139270|139270]]''', "How to Change Name Resolution Order on Windows 95 and Windows NT," does not change the hostname resolution order as expected. | ||
</div> | </div> |
Latest revision as of 11:05, 21 July 2020
Article ID: 171567
Article Last Modified on 10/30/2006
APPLIES TO
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q171567
SYMPTOMS
You may notice that changing the ServiceProvider priority values, as specified in Knowledge Base article 139270, "How to Change Name Resolution Order on Windows 95 and Windows NT," does not change the hostname resolution order as expected.
CAUSE
Unlike Windows NT 3.x, Windows NT 4.0 does not implement the ServiceProvider priority values.
RESOLUTION
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
STATUS
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.
STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0.
MORE INFORMATION
In Windows NT 4.0 Service Pack 4, Microsoft added a new registry value to the TCP/IP service that allows an administrator the option of changing the hostname resolution order. By default, hostname resolution is performed by Domain Name Service (DNS) first, followed by NetBIOS over TCP/IP (NetBT), if DNS fails. With the use of this registry value, the order of hostname resolution 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 name resolution mechanisms), perform the following steps:
- Run Registry Editor (Regedt32.exe).
Go to the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
On the Edit menu, click Add Value and enter the following value information:
Value Name: DnsNbtLookupOrder Data Type: REG_DWORD Value: 1 or 0 (default=0, value of 1 causes NetBT name resolution to be attempted before DNS)
- Exit the Registry Editor and restart the computer for the change to take effect.
Additional query words: 4.00 multihomed
Keywords: kbhotfixserver kbqfe kbbug kbfix kbnetwork KB171567