From there it will be necessary to either change the connection type to TCP/IP sockets or to troubleshoot the problem as a NetBIOS issue. Depending on the client configuration the client may bypass host name resolution. The application may be configured to connect to resources using NetBIOS. Many applications have multiple methods that they can utilize to resolve names, this is especially true of mail and database applications. If the name exists in one of the resources, such as a DNS server or a Windows Internet Name Service (WINS) server and the client is not resolving the name correctly, focus your attention on troubleshooting that specific resource.Īlso, confirm that the client is trying to resolve a host name and not a NetBIOS name. If the name does not exist in any of the resources that the client uses, then you must decide to which resource to add it. If a client cannot resolve a host name, then it is best to verify the Host name resolution sequence listed above that the client should be using. Problem: Client is unable to resolve a host name. These are documented in the Resource Kits for the specific operating systems, as well as in the Microsoft Knowledge Base.ġ71567 Windows NT 4.0 ServiceProvider Priority Values Not Appliedġ39270 How to Change Name Resolution Order on Windows 95 and Windows NTġ19372 Setting the Name Resolution Search Order for TCP/IP-32 The method for changing host name resolution order differs among operating systems and versions. If no DNS server IP addresses are entered in the client TCP/IP configuration, then the client will skip to the next step in the sequence after DNS. For example, if there is no hosts file on the system, then it will skip step #2 above and try a query to a DNS server. When resolving names the client will skip methods for which it is not configured. ![]() Lan Manager 2.2c or Microsoft Client 3.0 clients will not use NetBIOS name resolution as a backup.įor additional information, please see the following articles in the Microsoft Knowledge Base:ġ69141 NetBIOS and hostname resolution for MS-Client and LM 2.2c Windows NT, Windows 95, and Windows for Workgroups clients using Microsoft TCP/IP 3.11b follow this sequence. The Windows client will try each of these methods until it either successfully resolves the name or exhausts these methods. This order can be changed by configuring the NetBIOS node type of the client. If the name is still not resolved, NetBIOS name resolution sequence is used as a backup. Where %Systemroot% is the folder in which Windows NT is installed, is the drive on which the OS is installed, and refers to a boot floppy disk or drive C.Ī sample hosts file, Hosts.sam, is installed with the TCP/IP protocol showing the proper format.ĭomain Name System (DNS) servers are queried. Windows NT %Systemroot%\System32\Drivers\Etc NOTE: The Hosts file location depends on the operating system: The client then searches a local Hosts file, a list of IP address and names stored on the local computer. The client checks to see if the name queried is its own. Host name resolution generally uses the following sequence: A Windows NT server will take the role of client when it requires access to resources that require host name resolution. NOTE: In the context of this article, the term "client" does not necessarily refer to a workstation. When troubleshooting name resolution issues, it is important to narrow down whether the application is resolving a NetBIOS name or a host name. Examples of these types of applications are Outlook and Exchange. Many modern database and mail applications that connect using Winsock, the Microsoft Windows implementation of TCP/IP sockets, also use host name resolution. Other examples include Internet applications such as Ping, FTP, and Telnet. The most common example of this is a Web browser such as Microsoft Internet Explorer. ![]() Host name resolution resolves the names of TCP/IP resources that do not connect through the NetBIOS interface. Clients connecting to resources on Microsoft servers, typically through Windows File Manager or Network Neighborhood, most often use NetBIOS name resolution.įor additional information, please see the following article in the Microsoft Knowledge Base:ġ19493 NetBIOS over TCP/IP Name Resolution and WINS There are two main sequences used in almost all cases: NetBIOS resolution and Host name resolution. Microsoft Windows clients will follow a sequence of methods in attempting to resolve a name to an address, stopping the search when it successfully matches a name to an IP address. On a network using the TCP/IP protocol, it is necessary to convert names of resources to IP addresses to connect to these resources. The sequence of methods is different than the sequence used to resolve NetBIOS names to IP addresses. This article discusses the different methods of host name to IP address resolutions used by Microsoft Windows clients.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |