Background knowledge of Netbios
The NetBIOS interface is first developed by Sytec Inc. (current Hughes Lan Systems) in 1983 for International Commercial Machinery (IBM). It operates on the IBM's PC network to operate on the Sytec all protocol. This PC network is an early form of broadband LAN technology, which can accommodate up to 72 connection devices. One thing should be emphasized that NetBIOS has never considered upgrading to a large network at the beginning.
At Microsoft, NetBIOS is started as an advanced programming interface for an MS-DOS program that networked IBM PC (compatible microcomputer) network introduced in the late 1980s. In order to establish LAN, Microsoft and other vendors based on the networked hardware and software provided by those computers, standardize the use of NetBIOS interface design networking system components and programs. This interface uses length to limit the name of 16 characters to identify each network resource.
The NetBIOS namespace is a single layer, which means that only this name can be used in one network. These names are dynamically registered when the computer is started, the service start, or when logged in. The NetBIOS name can be registered as a unique name or group name. The only name has an address associated with the name. The group name has multiple addresses mapped to the name.
Prior to Windows 2000, all MS-DOS and Windows operating systems require NetBIOS naming interfaces to support network functions. After Windows 2000 is released, the computer's network connection no longer needs support for NetBIOS named interfaces. For example, using Windows 2000 and other operating systems that do not require NetBIOS names (such as certain versions of UNIX), you can build and run a environment that supports hosts and programs that support the use of the Domain Name System (DNS) ". However, most networks still need to integrate old operating systems that require NetBIOS network names with computers running Windows 2000.
For this reason, Microsoft Windows 2000 continues to provide default support for NetBIOS names to facilitate interaction with old operating systems that require their old operating system.
Disable NetBIOS on TCP / IP
Windows 2000 provides the ability to disable NetBIOS (NetBt) on TCP / IP, which is useful when selecting customers. If you need or like to use DNS to play a specific or secure-to-active specific computer (for example, the edge proxy server or host in the firewall environment), you can choose to disable the computer installed. NetBT services for one or all NIC interfaces.
When NetBt is disabled, pay attention to the following items for computers running Windows 2000:
The computer no longer monitors or accepts the User Data Rights (UDP) "datagram that is sent by the disabled network connection to NetBIOS service. The NetBIOS service receives communication on the following UDP ports: 137 (WINS or NETBIOS Name Server), 138 (NetBIOS Datashers) and 139 (NetBT Customer Request Program Service). Once disabled, all communications on these interfaces are received through the adapter interface, and they will be ignored without notice.
If WINS is installed on your computer, the computer can no longer act as a WINS server to pass through this connection to WINS Customer Service unless NetBT is re-enabled.
If the computer needs to participate in the WINS as a customer, it must be a host of host (that is, it must have other activity physical network connections, and it can be used) so that it can continue to work with Wins. Server communicates and uses the WINS server. For all WINS servers configured for the disabled NICs in the TCP / IP property, all WINS servers configured in the TCP / IP property are not applied to other NIC. To make these adapters use WINS, you must manually configure a WINS server list on the NetBT connection, or give these connections from the DHCP server.
One possible application of this configuration is that the server computer is a dual-and-hold computer that is located both in an internal dedicated network, which is located on an open external network (such as an Internet). In this case, the NetBT that disables the installed external network connection will work. This allows the dual-hosted computer to continue to act as a WINS server or internal network, and can still serve the WINS customer service by connecting to other physical network cards installed on the computer.
