There is service used to automatically associate names with addresses. DNS that is domain name system is the one that provides that mapping . DNS assigns name to the IP addresses .
DNS (Domain Name System)
dns
WINS
Lmhosts: provides NetBIOS-name-to-IP-address resolution
No...it resolves to an ip address
you see the file name is WINS. which stands for window internet name service see the resolution happens like this (p.s WINS, is not a file name it is a protocol) NetBIOS, broadcasts names to listening nodes on the network. NetBIOS utilizes a User Datagram Protocol UDP, query to broadcast names. NetBIOS names identified computer on the network before the introduction of Windows 2000. The NetBIOS name is resolved to an IP address through windows Internet Name Service WINS,broadcasting, or the LMHOSTS file. If the LAN is a NetBIOS LAN, the NetBIOS name is then the network address. The NetBIOS name is assigned by an administrator when the operating system is installed. To enable communication, the following requirements exist. i hope i have helped
when is NetBIOS routable
No, you cannot have the same netbios names because there would be a conflict between the computers and Netbios names are unique names.
As far as I know, NetBIOS was a own protocol once. Nowadays, Microsoft uses some components of it for networking via TCP/IP. When you access the properties of your network connection and choose "advanced", there is an option for deactivating NetBIOS. When you have Windows XP: Choose properties of you LAN connection properties of TCP/IP "advanced" (right part on the end of the properties window) click the third title "WINS" Here you might be able to deactivate NetBIOS, but I would not recommend it, because it is used for communicating with older systems and non-Windows enviroments.
No DNS is based on the hirearchal system not NetBIOS.
It allows you to connect to a computer using its NetBIOS name rather than an IP address. It is similar in function to the IP Hosts file. This technology is effectively deprecated (NetBIOS is an old technology) but allows the LMHost file to resolve NETBIOS names to IP address for environments with older applications. It is the last 'name resolution' mechanism to be used before name resolution fails. Physically, it is a text file that is stored in Windows\System32\drivers\etc. A sample LM Host file with explanation can be found there (LMHost.sam). It cannot be used with IPv6 and Windows uses DNS in preference to NetBIOS names since at least Windows 2000.
Worth noting is the popular confusion between the names NetBIOS and NetBEUI. NetBEUI originated strictly as the moniker for IBM's enhanced 1985 NetBIOS emulator for token ring. The name NetBEUI should have died there, considering that at the time, the NetBIOS implementations by other companies were known simply as NetBIOS regardless of whether they incorporated the API extensions found in that emulator. For MS-NET, however, Microsoft elected to name its implementation of the NBF protocol "NetBEUI" - literally naming its implementation of the transport protocol after IBM's second version of the API. Consequently, even today, Microsoft file and printer sharing over Ethernet continues to be called NetBEUI, with the name NetBIOS commonly used only in reference to file and printer sharing overTCP/IP. In truth, the former is NetBIOS over NBF, and the latter is NetBIOS over NBT.
NetBIOS is an non-routing protocol(unlike RIP OSPF asf). It is unroutable (just useable on local LANs via Hubs or Switches.
If you have Windows ME/9x and below systems, use WINS for a NETBIOS name resolution server as DNS does not resolve up NETBIOS.