Windows NT 4.0 ServiceProvider Priority Values Not AppliedLast reviewed: February 10, 1998Article ID: Q171567 |
The information in this article applies to:
SYMPTOMSYou may notice that changing the ServiceProvider priority values, as specified in Knowledge Base article Q139270, "How to Change Name Resolution Order on Windows 95 and Windows NT," does not change the hostname resolution order as expected.
CAUSEUnlike Windows NT 3.x, Windows NT 4.0 does not implement the ServiceProvider priority values.
RESOLUTIONContact Microsoft Technical Support to obtain the updated files mentioned below.
STATUSMicrosoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.
MORE INFORMATIONIn the fix mentioned above, Microsoft has 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: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk. To change the hostname resolution order (between DNS and NetBT name resolution mechanisms), perform the following steps:
WINS returns the list in the same order every time. NetBT uses the local route table to sort the IP addresses in the list into the "best" order. In the case where the calling system shares a common subnet with the called system, the "best" IP address would be the one on the same subnet, and this would be used every time. Because of this sorting, using NetBT name resolution can result in performance and efficiency improvements.
|
Additional query words: 4.00 multihomed
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |