NetBIOS wins DNS

NetBIOS name Network basic INPUT/OUTPUT System (RFC-1001,1002) networking fundamental input/output protocol

NetBIOS is an advanced network interface that was originally implemented in hardware. NetBIOS applications to establish a data structure called network control BLOCK,NCB, and then issue a BIOS function call to send the contents of the NCB to the network adapter. Windows Server 2003 provides support for NetBIOS applications through a NetBIOS emulation program. The simulator captures the BIOS call and translates it into a network function call. NetBIOS was first developed by Sytec Inc. in 1983 for IBM, and later became a factual standard for PC network interfaces. At the same time, IBM and Microsoft developed the Network command language together with the 3Com, which eventually evolved into SMB (service message block, services messages blocks). Earlier versions of the SMB application used NetBIOS as a network interface, using the NetBEUI (NetBIOS Extended User interface) as the transport protocol. Currently, it is mainly used for resource access in peer-network mode. NetBIOS is based on the NetBEUI protocol, it can only be used for Windows operating system, not for Linux, UNIX and other systems.

NetBIOS provides a network identification name for a resource, such as a workgroup name, computer name, and so on, and can access resources with those names. NetBIOS is used when we access computers on the network by using the names in our web places or UNC addresses.

NetBIOS cannot be routed, so using NetBIOS can only access computers in the same network segment .

NetBIOS name NetBIOS name consists of 16 bytes, of which the first 15 bytes are specified by the user, and the 16th byte is the name suffix, specifying a service.

NetBIOS names can contain only letters, numbers, and wires--and cannot exceed 15 in length. A computer can have multiple NetBIOS names and can be viewed with the "nbtstat-n" command.

A UNC address is used when accessing the network with a NetBIOS name, the format of which is: \\NetBIOS name \ Path where NetBIOS names can also be directly replaced with IP addresses.

NetBIOS name resolution the same as the domain name, the NetBIOS name does not directly access the computer, it must be resolved to an IP address to access. There are two main methods of parsing: 1, sending the broadcast in the network to query, 2, using the WINS server to parse. In addition, there is a NetBIOS cache on the local computer to hold the results of the most recently queried. Users can also manually create Lmhosts files for parsing.

NetBIOS offers three different types of services:

Name Services: Name registration and resolution session service: reliable connection-based communication packet service: unreliable, non-connected communication when NetBIOS is the Data Link layer protocol, it can be accessed through a 5Ch interrupt. The messages passed to these functions use the NCB format. NetBIOS and NetBEUI are designed for LAN only, so routing is not supported and can only handle up to 72 nodes or devices. NetBIOS and NetBEUI are often implemented using broadcasts, especially those related to the name service. NBT uses one or more NBNS (NetBIOS name Server (s)) to extend the moniker service to multiple subnets. NBNS is a dynamic DNS, and Microsoft's NBNS implementation is called wins. In addition, to extend a virtual NetBIOS network to multiple IP subnets, the WINS standard also introduces one or more NBDD (NetBIOS Datagram distribution) servers. Unfortunately, Microsoft's NBDD implementations have never worked.winsThe  windows Internet Naming Service (Windows Internet name Service,wins) provides a distributed database for dynamic mappings that register and query the NetBIOS names of computers and user groups on the network. WINS maps the NetBIOS name to an IP address and is designed to resolve issues that occur in the NetBIOS name resolution of the routing environment. WINS provides the best choice for NetBIOS name resolution in a NetBIOS routed network using TCP/IP. WINS reduces local IP broadcasts that use NetBIOS name resolution and allows users to easily locate systems on the remote network. Because WINS registrations are performed automatically each time a client starts and joins the network, the WINS database is automatically updated when the dynamic address configuration is changed. For example, when a DHCP server publishes a new or changed IP address to a WINS-enabled client computer, the client's WINS information is updated. This does not require a user or network administrator to make manual changes. The 10.2.2.WINS composition of the typical WINS system consists of the WINS server and the WINS client two parts. WINS servers are responsible for collecting registration information for WINS clients and for maintaining and managing the WINS database. The WINS client registers its NetBIOS computer name and IP address with the WINS server at startup. In a network system, there may also be non-WINS clients, such as Linux computers, if the WINS server and the WINS client are in different subnets, you also need to configure the WINS proxy (WINS proxies), similar to the DHCP Relay agent described in Chapter Nineth: 10.2.3. WINS's work process wins simplifies the management of NetBIOS namespaces in a TCP/IP-based network. When the WINS client starts, it registers its own computer name with the WINS server (note: Unlike the host name described in chapter eighth), the NetBIOS name and the corresponding IP address are added to the database, which is the registration process for the WINS server. WINS clients are registered at the WINS server each time they are started, so the database on the WINS server is always up to date. The working process of wins when communication is required between WINS clients, they first need to know the IP address of the other through name resolution, and the WINS server completes the resolution work in the WINS system. When the WINS server receives a communication request from the WINS client, it automatically queries the computer name and IP address from the local database and provides it to the WINS client requesting communication to complete the resolution of the name.  

NetBIOS wins DNS