In the LAN environment, there are a lot of broadcast transmissions. For example, the server enables users to obtain a list of all computers on the network through MicrosoftLANServicesBrowser. Each WindowsNetworking client regularly registers its NetBIOS name by sending a broadcast, and each computer also sends a broadcast to elect a main browser for the network. The main browser (and several backup main browsers) is responsible for maintaining the computer and address list. When users browse the network, the client sends a broadcast request, and then the main browser responds. The main browser response does not require all devices to respond to the broadcast request. A large number of broadcasts not only occupy bandwidth, but also are inefficient.
Name resolution is very important in windows network environment, because it allows PC to communicate with devices only by knowing the name of the device it wants to connect to. Without some form of name resolution, every PC must know all the information of any other device on the network. Fortunately, WindowsNetworking customers have four solutions to achieve name resolution: First, broadcasting.
Broadcasting is the default operation of all Microsoft products. By sending a broadcast on a subnet, Windows users will cause browser elections. The designated main browser maintains a list of available resources on the subnet. Because registration, browser election and name query all generate broadcasts, this method is not scalable. It is strongly recommended that all clients turn off the default broadcast function. Try to reduce unnecessary broadcasts in the local area network.
Advantages of broadcasting: Windows system runs by default, and there is no need to manually intervene in system setting and IP address configuration. In practical application, in general, as long as two or more Windows system PCs are connected to the same hub or switch and do nothing, other Windows system PCs can be found in the online neighborhood.
Disadvantages of broadcasting: bandwidth occupation, low efficiency and difficulty in troubleshooting. In practical application, because Windows98 system doesn't handle NT server and NT domain information, the default setting of Windows98 system client is to browse the host. If the client of Windows98 system is wrongly declared as the browsing host, it will block the browsing of every computer in the whole subnet. In other words, some Windows98 system clients often can't see some Windows2000 system clients in the online neighborhood, and vice versa.
Some solutions to broadcasting: add NetBEUI protocol and restart the client. There is an application in windows nt Server Resourceit: browstat, which runs on Windows NT computers in the affected subnet and can be used to find fake broadcasting companies in the subnet.
Suggestions on broadcasting scheme: The broadcasting scheme is out of date, and the broadcasting function should be disabled at the client. Different Windows systems have different disabling methods.
How to disable broadcasting:
1. for windows for workgroups 3.11:modify the system. INI and set the maintenance server list = no.
2. For Windows9x: Online Neighborhood properties/files and printers enjoy properties/browse the main server in/Microsoft network * * *, the default is automatic, and it is disabled instead. Restart the client.
3. For windows nt 3.5 1 workstations and servers, it is configured not to send broadcasts after WINS name resolution.
4. For NT, the default settings are adopted, and the current control settings of HKEY _ local _ machine system are registered.
The entries in the servicesrowserparameters field are set as follows: MaintainServerList is set to Yes, and IsDomainMaster is set to False. The MasterPeriodicity setting (in seconds) specifies how often the subnet browsing server queries the domain administrator for the browsing list. This item needs to be set to 1 hour or longer when the subnet browsing server and the domain supervisor are separated by slow or per-packet change links. Second, LMHOSTS
Customers query static tables maintained by PDC. In order to make this method scalable, PDC needs to maintain not only the static IP address list of all current computers and domains, but also the computer names and addresses of all other domains in the network. All clients must be configured with LMHOSTS files. It contains the IP address of the local PDC and the path of the LMHOSTS file.
Advantages of LMHOSTS: quick response, easy troubleshooting and simple configuration.
Disadvantages of LMHOSTS: the corresponding configuration needs manual intervention, and the scalability is not good. The application scale is limited.
Suggestions on LMHOSTS scheme: It can only be used in small networks. It can be used for special customers under special circumstances. Can only be used as a temporary or test solution. Third, victory.
WINS allows clients to dynamically register and browse the network on different IP subnets without sending broadcasts. The client sends a unicast packet to the WINS server with a recognizable address, and the WINS server converts NetBIOS into the IP address of the client.
Advantages of WINS: eliminating the inherent broadcast in NetBIOS, simple configuration, high efficiency and easy troubleshooting.
Disadvantages of WINS: WINS is only applicable to local area network (LAN).
Suggestions on WINS scheme: WINS is the best way to realize the scalability of MicrosoftNetworking. Fourth, DNS.
DNS is a common TCP/IP application, which provides the conversion of Internet names to IP addresses. WINS server and DNS server must be located on the same WindowsNT computer.
Advantages of DNS: fast resolution of domain name or host name to IP address conversion. High efficiency. Widely used on the Internet.
Disadvantages of DNS: Windows9x and NT4.0 systems in local area network (LAN) are not supported.
Suggestions on DNS scheme: use on WAN. It is best to cooperate with WINS on the local area network. V. Optimization scheme
WINS and DNS work together to provide fast and effective DNS to NetBIOS to IP address lookup for end-user devices. Establish WINS and DNS services on the same server.
1. Disable all client broadcast functions.
2. It is strongly recommended to establish a DHCP server in every conditional place. The information distributed by DHCP includes WINS and DNS, gateway, domain name, WINS/NBT node type, etc.
There are four types of WINS/NBT nodes: 0X 1(B, broadcast), 0X2(P, WINS), 0X4(M, mixed, broadcast first and then find WINS), 0X8(H, mixed, find WINS first and then broadcast).
3. The client obtains the IP configuration information from the DHCP server.
4. The client registers the NetBIOS name on the WINS server.
5. Configure the DNS server to look up names on the WINS server.
6. Configure push/pull replication partners for WINS in large LAN.
7. Adjust the WINS refresh interval according to the specific situation. The interval between stable networks can be slightly longer.
8. Back up WINS and DNS regularly, check the consistency of WINS version ID and database regularly, and clean up the database.