Detailed configuration and use of Windows Server 2003 wins

NetBIOS Name Overview

A computer in the network can be named with NetBIOS and DNS two naming, and in the NetBIOS standard, a name of up to 16 characters is used to uniquely identify each network resource to identify the resource or service type. In the actual work. The computer name, workgroup name, or domain name that you see through my Network Places in the Windows operating system is the NetBIOS name.

The working process of NetBIOS

When you use NetBIOS names in your network, the basic work process includes the registration, deallocation, and querying of NetBIOS names. Registration is performed dynamically when the computer starts, when the service starts, or when the user logs on. The NetBIOS name is released when the computer shuts down properly, the service stops properly, or the user exits normally. If a computer tries to access another computer through a NetBIOS name, a NetBIOS name query is required so that it can communicate properly, and the registration and release of the NetBIOS name is essentially for the name lookup service. In 2003, you can implement NetBIOS name registration, deallocation, and querying based on the NetBEUI and TCP/IP two protocols.

1. Support NetBIOS based on NetBEUI protocol

The NetBEUI protocol is a non-routed protocol that IBM introduced and developed in 1985, which lacks routing and network layer addressing capabilities. All communication can only be done by means of broadcast messages, so it can only be applied to small workgroup or local area networks, because the NetBEUI information only has the Data link layer MAC address, no additional network address and network layer to the tail. If you are using only NetBIOS names for communication in your network, you can simply deploy the NetBEUI protocol without deploying the TCP/IP protocol. In the current network, the NetBEUI protocol has been largely used to NETBIOS. 2003 also no longer provides it, the replacement is the TCP/IP protocol.

2. NetBIOS based on TCP/IP protocol support

implemented by its components. is enabled by default in 2003.

NetBIOS name resolution

When using NetBIOS on TCP/IP to support NetBIOS, you need to resolve NetBIOS to an IP address and then communicate via IP address, in WIN2003, NetBIOS parsing can be implemented in several ways. The top 3 below are standard NetBIOS name resolution methods, followed by Microsoft's proprietary NetBIOS name resolution method.

1. Resolving NetBIOS names through NetBIOS name resolution cache

The NetBIOS name cache holds the NetBIOS name that the local host has recently queried and uses Nbtstat to view the NetBIOS name information. NetBIOS name resolution is the primary parsing method.

2. Resolve NetBIOS names by sending broadcast messages

When the host needs to resolve the NetBIOS name, it can send a broadcast message to the network that contains the NetBIOS name to resolve, all hosts in the network will receive the broadcast message, and check whether the registered NetBIOS name matches the NetBIOS name of the broadcast message. This resolution encounters two problems: the broadcast interferes with each node on the network. Routers typically do not forward broadcasts, so only ntbios names on the local network can be resolved.

3. Resolve NetBIOS name by NetBIOS name server

In real-world applications, you can deploy a dedicated NetBIOS name server (NBNS) to resolve NetBIOS names, use NetBIOS name servers, enable support for NetBIOS names in network environments that span subnets, and effectively provide network performance, WIN2003 through WINS implements the NetBIOS name server, which provides support for NetBIOS names.

4. Resolve NetBIOS name through LMHOSTS file

The Lmhosts file is a static, plain text file that holds the corresponding information for the NetBIOS name and IP address, each of which is referred to as an entry, which must be entered manually. When parsing, the top-down contrasts each entry in turn. Lmhosts must be stored on the host that needs to resolve the NetBIOS name, by default, each WIN2003 host has Lmhosts files, stored in the%systenroot% \ststem32\drivers\etc directory, and is named Lmhost. SAM. You need to rename it to Lmhosts when you use it.

5. Resolve NetBIOS names through hosts file and DNS

The NetBIOS name defaults to the same host name, in which case the NetBIOS name can also be resolved through the Hosts file and DNS.

NetBIOS node type

B-node: broadcasts a message to resolve the Ntetbios name.

P-node: Use NetBIOS name server to resolve NetBIOS, not broadcast, but query name server directly

M-node: is a combination of the above two nodes.

H-node: is a combination of P-node and B-node, by default, the H-node is used as a P-node, and if the H-node cannot resolve the NetBIOS name through the NetBIOS name server, the name is resolved using broadcast.

Running the WIN2003 computer defaults to B-node. Automatically becomes an H-node when you configure a WINS client

WINS overview

1. What is wins

Wins (Windows Internet name service,windows), is an enhanced NetBIOS name server that uses WINS when NetBIOS name resolution requests are sent directly to the WINS server. If it can resolve, it sends the IP address directly to the requesting host.

WINS working mechanism

Name registration, name update, name release, and name lookup and parsing procedures between WINS clients and WINS servers

1 Name Registration

When the WINS client initializes, it issues a registration request directly to the specified primary WINS server via unicast, requiring that information such as its NetBIOS name and IP address be registered with the WINS server's database, and that the following 3 scenarios may occur after the WINS client issues a name registration request

(1) Accept registration. If the primary WINS server is functioning properly, receives a name registration request from the client, and the name of the client requesting registration is not registered by another client, the WINS server will accept the registration and return a successful registered message to the client, which will contain the lifetime of the client registration, NetBIOS name , which is the TTL

(2) Duplicate name. If the primary WINS server is working correctly, but the name that the client requests to register is already registered in the WINS database by another user, the WINS server sends challenge to the current owner of the name if duplicate name is present. Challenge will be sent in the form of a name inquiry, and sent 3 times in a row, with a time interval of 500US, and if the WINS server receives a message that the name currently has a response to it, the WINS server will send a message rejecting the registration to the client attempting to register the name. If the current owner of the name does not respond to the WINS server's challenge, the WINS server will send a successful registration message to the client attempting to register the name.

(3) The WINS server is unresponsive. If the WINS client does not receive any response from the primary WINS server for a specified time, indicating that the primary WINS server is inaccessible, the WINS client will attempt 3 attempts to find the primary WINS server, and if 3 attempts fail and the WINS client is configured with a secondary WINS server, The name registration request is sent to the secondary WINS server, and if no WINS server is available, the WINS client may be registered by broadcasting.

2. Name update

The NetBIOS name registered by the WINS client has a lifetime, and in order to continue to use the registered NetBIOS name, the WINS client must have NetBIOS name registration updates to the WINS server before the time is in place.

3. Name Release

When the WINS client shuts down gracefully, it sends a name-release request to the WINS server as a unicast, removes its registered NetBIOS name from the database of the WINS server, and when the WINS server receives a name-release request, it checks the WINS database for the name of the release. If a matching NetBIOS name and IP address are found, the WINS server sends a positive name release response message to the client, and the name in the database is set to "not activated"

4. Name query and name resolution

When the WINS client needs to communicate with other hosts through the NetBIOS name, the IP address corresponding to the NetBIOS name of the host needs to be queried, as determined by the NetBIOS node type, if the WINS client default node type (H-node) is used. The NetBIOS name cache is checked first, then the name query request is sent directly to the primary WINS server, and the client will resend two times if the primary WINS server is not responding. If the primary WINS server is not responding, turn to the secondary WINS server.

Deploying the WINS Service

Point more information

Select Wins, and then click OK

The installation started

It appears that the verification, such as the file and so on installation success

Below to configure and test the client

Manually configure the WINS client first

Here is the advanced in the client, manual configuration point

Click Add, enter the IP address of the WINS server.

and enable NetBIOS on TCP/IP

To verify the WINS client configuration, you can see the address of the primary WINS server

Lists the NetBIOS names registered by the current computer

The following is a look at automating the configuration of WINS clients through DHCP and verifying configuration

This is the configuration scope option in the DHCP scope

Specify the IP address of the WINS server

Specifies the NetBIOS node type of the WINS client, which is the H-node

Here is the client configuration, which is selected by default.

The following validation follows

Use the command to clear the manually configured WINS server.

Specifies that the WINS client obtains the IP address of the WINS server through DHCP. Finally, the WINS client configuration is validated by Ipconfig/all and the previous results are visible

To display WINS database records on a WINS server

After you configure the WINS client, you can view the NetBIOS registered by the WINS client on the WINS server by displaying the WINS database records.

Point Display record

Here's a record that shows

Click Find Now

will appear as a record. These are the NetBIOS names that are registered by the client

Let's look at configuring WINS replication

Click New Replication Partner

This is the partner's IP address.

You can see that this is a push or pull WINS server partner

Properties of the point replication partner

In real-world applications, two or more WINS servers are typically deployed in order to balance the load and provide fault tolerance. There are two replication partners where a push partner sends a WINS database change notification to its corresponding pull partner in the specified case. The pull partner requests the updated WINS database record in the specified case to its corresponding push partner.

WINS Replication Policy

(1) Bidirectional replication: In high-speed connected LAN, can adopt two-way replication policy, if two-way replication, each WINS server must be configured as a "push/pull" partner of other WINS server, two-way replication, each WINS server database will contain all replication partners database records

(2) One-way replication. Deploying WINS replication over a slow network connection between different physical locations can take a one-way replication policy. In real-world applications, the pull partner is configured to perform WINS replication at a specific time to enable one-way replication/

Click Start push or pull copy to start copying

Point Properties

Configuring the update interval and backup path

In general, if the WINS client shuts down gracefully, the WINS server automatically marks the name record for that client registration as released, but if the WINS client shuts down abnormally, the WINS server waits until the update interval expires before identifying the name of the client registration as released.

Configure Database Validation

Configuring WINS to support non-WINS clients

By adding static mappings to resolve

Click Active to register the right key, and then account for the new static mapping. Enter the computer name and IP address of the non-WINS client above.

You can see that the selected is a static mapping record, AC qq2881064152

Detailed configuration and use of Windows Server 2003 wins