![]() ![]() Technically, you could create a NetBIOS naming server that is not a WINS server, but it is rarely done. In most cases, the naming server contacted is a Windows Internet Naming Server (WINS). Third resolution: The third resolution mechanism used by the local computer to resolve the NetBIOS name involves consulting one or more naming servers. Typically, %SYSTEMROOT% is the C:\WINNT directory. The LMHosts file is located in %SYSTEMROOT%\SYSTEM32\DRIVERS\ETC. This can be helpful if you are trying to find a domain controller to log into. The second option, #DOM (domain), is used to associate the computer with a NetBIOS domain name. This has little effect in today’s environment. ![]() The first option is #PRE, which causes the entry to be cached into memory. In addition to the IP address and NetBIOS name, you have two more options. In its simplest form, the LMHosts file contains an IP address and a host name. Second resolution: The second resolution method is where the LMHosts file is consulted to see if there are any NetBIOS names that match the NetBIOS name being queried. Although in today’s world of 512-MB desktop computers this may seem odd, it was a real concern when the NetBIOS naming strategy was developed and we were still dealing with conventional (640K) memory. It is also important to have a limited lifetime for the cache to minimize the amount of memory used for caching. However, entries put into cache by the LMHosts file option never expire. In order to reduce the possibility that the cache will become invalid because too much time has passed since the name was resolved, the cache has a limited lifetime, typically 10 minutes. If you need to resolve the name again, the name is cached in order to improve responsiveness and limit network traffic. The idea behind the cache is that, if the software needed to resolve the name once, it is quite likely that it will soon need to do so again. This cache is populated by previous name resolution attempts and by a special option in the LMHosts file (described next). It is an internal cache that is in each Windows machine. Before you begin, you need to understand the four kinds of resolution that NetBIOS does natively.įirst resolution: The first resolution mechanism is not really a resolution mechanism at all. You then check an LMHosts file and, lastly, progress into a broadcast message that looks for the name (that is, unless the default actions have been changed). NetBIOS names are located through a series of steps that begins with checking the local cache. The best way to determine what is broken in NetBIOS name resolution, however, starts with understanding how NetBIOS name resolution works. You not only have to troubleshoot all of the NetBIOS name resolution options, but you must also troubleshoot the IP host name resolution. Although the net effect is making it easier to resolve names, the substitution strategy makes troubleshooting problems more difficult. Just to muddy the waters, Microsoft allows IP host names to be used as a substitute for NetBIOS names. These names are resolved either by using an LMHosts file on the local machine or WINS server, or by broadcasting a request. These are the names that are used when you are mapping a drive or connecting to a printer. ![]() The second kind of name is the NetBIOS name, which is used for Windows (SMB) type sharing and messaging. Host name resolution uses a host’s file and DNS for resolution. The first kind is a name for IP addresses. In the Windows client world, there are two basic types of names. The first issue is determining the kind of name. That is great, but what happens if NetBIOS name resolution is not functioning? To help you overcome this obstacle, I will explore the components of NetBIOS resolution and help isolate the cause of name resolution problems. It seems simple enough: If you can connect to a computer by IP address and not by NetBIOS name, the problem is with name resolution. One of the important steps in trying to resolve IP problems is determining if name resolution is working. Understanding how NetBIOS works is the key. Unfortunately, when NetBIOS problems occur they can be difficult to detect. NetBIOS alone should not give you many headaches. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |