|
|
Get Certify Get Ahead
MCSE CAMP
+91-9821043107
Schedule
FAQ
Why Vibrant
Location
Leading MCSE, CCNA, CCNP Certification boot camp training provider in India, USA, UK.
Name Resolution
WINS clients send name resolution requests to the WINS server. A name resolution request typically occurs when the client computer tries to map a network drive. To connect to a network drive, the user needs to specify two things: a system name and a share name. The system name provided needs to be resolved to an IP address. The basic flow of a name resolution request is as follows:
| 1. | When a client computer wants to resolve a name, it first checks its local NetBIOS name cache. (You can view the cache using the nbtstat command, which is covered in detail in Chapter 7.) |
| 2. | If the name is not in the local cache, a name query is sent to the primary WINS server. If the primary WINS server is unavailable, the request is re-sent twice before going to the secondary WINS server. If either WINS server resolves the name, a success message is sent to the client, containing the requested NetBIOS name and IP address. |
| 3. | If neither the primary nor secondary WINS server is available, or if neither server can resolve the query, a negative response is sent to the client. The WINS client then attempts to resolve the name using either an LMHOSTS file, a broadcast request, or DNS. Note that WINS clients can be configured to use many name resolution strategies. |
WINS clients can be configured to use various methods of name resolution. These are referred to as b-node, h-node, m-node and p-node. Each method differs slightly.
These name resolution strategies are shown in the following list:
- b-node name resolution does not use WINS. It relies entirely on broadcast packets for name registration and resolution. This is the type of name resolution used in environments that do not have a WINS server, and can result in a large quantity of broadcast traffic.
- p-node name resolution uses WINS exclusively. The client does not fall back on broadcast messages when the WINS server cannot resolve the query or is unavailable.
- m-node name resolution is a combination of b-node and p-node. The client first uses b-node to attempt to resolve a query, and if the query is unsuccessful, the client resorts to p-node. The client computer can use WINS, but primarily uses broadcast messages.
- -node name resolution also combines b-node and p-node strategies. Unlike m-node, the client uses p-node first and uses b-node as a last resort. This is the most efficient implementation because it reduces the reliance on broadcast messages, and still provides WINS clients with a backup method of name resolution if the WINS server is unavailable or cannot resolve the query.
WINS clients can be configured to use either method. Details on how to configure WINS clients are discussed in the “WINS Client Configuration” section of this chapter.
Vibrant Advantage :
![]()
No Prestudy
Longest Duration Camp
Chalk Talk Training![]()
Highest Passing Rate
Bootcamp since 1999
Guaranteed
Certification ...
Testimonials :

The instructor taught real world experience and did not just teach us to pass the test. He knew the subject well and was encouraging. His lectures were very well delivered....
Colver Dennis, USA
|
MCSE Boot Camp India
| MCSE
Camp
UK
| MCSE
Camp USA
|
India Information
|
Card Payment
|
Site Map
|
Contact
|
Home
|
ref1 |
Ref2
|
RHCE |
RHCT |
Redhat |
RHCE / RHCT |
RHCE Boot Camp
© Copyright 2007
MCSE
Camp