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. CAUSE
Unlike 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. STATUS
Microsoft 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 INFORMATION
In 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.
Additional query words: 4.00 multihomed
Keywords : kbnetwork kbbug4.00 kbfix4.00 nttcp ntregistry NTSrvWkst |
Last Reviewed: February 24, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |