Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
WINS pros & cons 2
- Thread starter jmandiaz
- Start date
-
2
- #2
butchrecon
MIS
Windows Internet Name Service (WINS)
WINS provides a distributed database for registering and querying dynamic NetBIOS names to IP address mapping in a routed network environment. It is the best choice for NetBIOS name resolution in such a routed network because it is designed to solve the problems that occur with name resolution in complex Internetworks.
The LMHOSTS file addressed only one disadvantage of broadcast based systems—it allowed resolution of names across routers. Since the system itself was still broadcast-based, the problems of broadcast traffic and load on local nodes were not solved. RFCs 1001/1002 address these problems. They define a protocol that allows name registration and resolution through unicast datagrams to NetBIOS Name Servers (NBNS). Because unicast datagrams are used, the system inherently works across routers. This eliminates the need for an LMHOSTS file, restoring the dynamic nature of NetBIOS name resolution. This, in turn, allows the system to work seamlessly with DHCP. For example, when dynamic addressing through DHCP results in new IP addresses for computers that move between subnets, the changes are automatically updated in the WINS database. Neither the user nor the network administrator needs to make manual accommodations for name resolution in such a case.
The WINS protocol is based on and compatible with the protocols defined for NBNS in RFCs 1001/1002, so it is interoperable with other implementations of these RFCs. Another RFC-compliant implementation of the client can talk to the WINS server. Similarly, a Microsoft TCP/IP client can talk to other implementations of the NBNS server. However, because the WINS server-to-server replication protocol is not specified in the standard, the WINS server will not interoperate with other implementations of a NetBIOS Name Server. Data will not be replicated between the WINS server and the non-WINS NBNS. Therefore, the WINS system as a whole will not converge and name resolution will not be guaranteed. WINS consists of two main components, the WINS server and WINS client.
WINS Server
Handles name registration/release requests from WINS clients and registers/releases their names and IP addresses.
Responds to name queries from WINS clients by returning the IP address of the name being queried (assuming the name is registered with the WINS server).
Replicates the WINS database with other WINS servers.
WINS Client
Registers/releases its name with the WINS server when it joins/leaves the network.
Queries the WINS server for remote name resolution.
Benefits of Using WINS
Dynamic database maintenance to support computer name registration and resolution.
Centralized management of NetBIOS name database.
Reduction of IP broadcast traffic in the Internetwork, while allowing the clients to locate remote systems easily across local or wide-area networks.
The ability for the clients (Windows NT 3.5 (or newer), Windows® for Workgroups 3.11, Windows 95) on a Windows NT Server-based network to browse remote domains without a local domain controller being present on the other side of the router.
On a Windows NT network, the ability to browse transparently across routers (for domains that span multiple subnets). To allow browsing without WINS, the network administrator must ensure that the users' primary domain has Windows NT Server or Windows NT Workstation computers on both sides of the router to act as master browsers. These computers need correctly configured LMHOSTS files with entries for the domain controllers across the subnet.
Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.
James Collins
Computer Hardware Engineer
A+, MCP
email: butchrecon@skyenet.net
WINS provides a distributed database for registering and querying dynamic NetBIOS names to IP address mapping in a routed network environment. It is the best choice for NetBIOS name resolution in such a routed network because it is designed to solve the problems that occur with name resolution in complex Internetworks.
The LMHOSTS file addressed only one disadvantage of broadcast based systems—it allowed resolution of names across routers. Since the system itself was still broadcast-based, the problems of broadcast traffic and load on local nodes were not solved. RFCs 1001/1002 address these problems. They define a protocol that allows name registration and resolution through unicast datagrams to NetBIOS Name Servers (NBNS). Because unicast datagrams are used, the system inherently works across routers. This eliminates the need for an LMHOSTS file, restoring the dynamic nature of NetBIOS name resolution. This, in turn, allows the system to work seamlessly with DHCP. For example, when dynamic addressing through DHCP results in new IP addresses for computers that move between subnets, the changes are automatically updated in the WINS database. Neither the user nor the network administrator needs to make manual accommodations for name resolution in such a case.
The WINS protocol is based on and compatible with the protocols defined for NBNS in RFCs 1001/1002, so it is interoperable with other implementations of these RFCs. Another RFC-compliant implementation of the client can talk to the WINS server. Similarly, a Microsoft TCP/IP client can talk to other implementations of the NBNS server. However, because the WINS server-to-server replication protocol is not specified in the standard, the WINS server will not interoperate with other implementations of a NetBIOS Name Server. Data will not be replicated between the WINS server and the non-WINS NBNS. Therefore, the WINS system as a whole will not converge and name resolution will not be guaranteed. WINS consists of two main components, the WINS server and WINS client.
WINS Server
Handles name registration/release requests from WINS clients and registers/releases their names and IP addresses.
Responds to name queries from WINS clients by returning the IP address of the name being queried (assuming the name is registered with the WINS server).
Replicates the WINS database with other WINS servers.
WINS Client
Registers/releases its name with the WINS server when it joins/leaves the network.
Queries the WINS server for remote name resolution.
Benefits of Using WINS
Dynamic database maintenance to support computer name registration and resolution.
Centralized management of NetBIOS name database.
Reduction of IP broadcast traffic in the Internetwork, while allowing the clients to locate remote systems easily across local or wide-area networks.
The ability for the clients (Windows NT 3.5 (or newer), Windows® for Workgroups 3.11, Windows 95) on a Windows NT Server-based network to browse remote domains without a local domain controller being present on the other side of the router.
On a Windows NT network, the ability to browse transparently across routers (for domains that span multiple subnets). To allow browsing without WINS, the network administrator must ensure that the users' primary domain has Windows NT Server or Windows NT Workstation computers on both sides of the router to act as master browsers. These computers need correctly configured LMHOSTS files with entries for the domain controllers across the subnet.
Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.
James Collins
Computer Hardware Engineer
A+, MCP
email: butchrecon@skyenet.net
- Status
Similar threads
- Locked
- Question
- Locked
- Question