Games Microsoft WINS

Understanding and Implementing WINS

Understanding and Implementing WINS

Contents

Home windows Web Identify Server (WINS) Overview

WINS is an enhanced NetBIOS identify server (NBNS) which was designed by Microsoft to resolve NetBIOS pc names to IP addresses, and on the similar time remove the utilization of broadcasts for identify decision. On this method, WINS eliminates visitors generated by broadcasting on the community. WINS supplies a WINS database that it makes use of to retailer and keep NetBIOS pc names to IP addresses mappings. WINS registers NetBIOS pc names, and shops these shopper identify registrations within the WINS database. The registrations are used when shoppers question for host identify decision and service info. The database is then utilized to resolve a NetBIOS identify to an IP tackle.

WINS can resolve NetBIOS names for native hosts and distant hosts. Shoppers which are configured to make the most of a WINS server as a NetBIOS identify server (NBNS) are referred to as WINS enabled shoppers or just WINS shoppers. Shoppers that aren’t configured to make the most of WINS for identify decision are referred to as broadcast shoppers.

The primary benefits of utilizing WINS to resolve the NetBIOS names of computer systems into IP addresses are summarized under:

  • NetBIOS shopper requests are transmitted to the WINS server. If the WINS server resolves the NetBIOS identify to an IP handle, no broadcast visitors is shipped over the community. This principally signifies that visitors generated by broadcasting is decreased. Broadcasts are solely used if the WINS server is unable to resolve the NetBIOS identify.

  • The WINS database is up to date dynamically. This ensures that the database stays present.

  • When a WINS shopper’s IP handle modifications, the WINS shopper routinely updates the WINS server database with the change.

  • The necessity to manually keep a LMHOSTS file for every pc is eradicated.

  • A WINS enabled shopper can talk with a WINS server that’s situated anyplace on the internetwork.

When a WINS enabled shopper queries the WINS database, the next occasions happen. This chain of occasions is usually referred to as the WINS identify decision course of:

  1. The NetBIOS identify cache is first checked for an entry that’s related to the requested identify.

  2. A NAME QUERY REQUEST message is shipped to the first WINS server configured for the WINS shopper.

  3. WINS makes use of Consumer Datagram Protocol (UDP) port 137 for communication.

  4. The WINS server performs a search in WINS database to find out if the queried identify exists within the database.

  5. Based mostly on whether or not the NetBIOS identify is discovered within the database, the WINS server returns both a constructive response or a adverse response to the shopper.

  6. If the WINS server locates the NetBIOS identify within the WINS database throughout its search, and the NetBIOS identify has an lively state, the related IP tackle is returned to the shopper. Queried service lookups are additionally returned. That is referred to as a constructive response, and is shipped within the type of a POSITIVE NAME QUERY RESPONSE message to the shopper.

  7. If the WINS server locates the NetBIOS identify within the WINS database throughout its search however the NetBIOS identify has a state aside from the lively state, a unfavorable response is returned to the shopper, whereby the shopper is knowledgeable that the requested NetBIOS identify is unavailable. The shopper shouldn’t be pressured to transmit a broadcast for NetBIOS identify decision.

  8. If the WINS server can’t find the NetBIOS identify within the WINS database throughout its search, a unfavorable response is returned to the shopper. This takes the type of a NEGATIVE NAME QUERY RESPONSE message. The shopper is then pressured to transmit a broadcast for NetBIOS identify decision.

  9. The WINS server sends the shopper a variety of WAIT FOR ACKNOWLEDGEMENT RESPONSE messages if it can’t instantly reply to the request. This prevents shoppers from timing out whereas they anticipate a response from the WINS server.

  10. If a clientis configured to make use of a main WINS server and a secondary WINS server, the shopper makes use of the secondary WINS server if the first WINS server fails to answer its request. The shopper proceeds to ship NAME QUERY REQUEST messages to the secondary WINS server for identify decision.

As a result of WINS shopper registrations aren’t everlasting, registration info can turn out to be outdated. The validity of the WINS shopper registrations is decided by the point to stay interval of the WINS servers. WINS shoppers use a 3 step course of to make sure that registration info within the WINS database stays present:

  • WINS Identify Registration: A WINS shopper is configured with the IP handle of 1 or two WINS servers:

    • Main WINS server: The WINS shopper registers its NetBIOS identify and IP handle with the first WINS server when the shopper initially begins. To do that, the WINS shopper sends a NAME REGISTRATION REQUEST message on to the configured main WINS server. The NAME REGISTRATION REQUEST message consists of the time that the NetBIOS identify is registered to the shopper. That is outlined because the Time to Stay (TTL). The WINS server then shops the NetBIOS identify to IP handle mapping within the WINS database.
      If the first WINS server is unavailable, the WINS shopper tries two extra occasions to register with the first WINS server earlier than trying to register with a secondary WINS server.

    • Secondary WINS server: When a shopper is configured with the IP handle of two WINS servers, the secondary WINS server is simply tried for WINS identify registration after the shopper unsuccessfully tried to contact the first WINS server.
      When both the first WINS server or secondary WINS server receives a WINS identify registration request, the WINS server first searches its database to find out whether or not the requested identify exists. The shopper is efficiently registered with the WINS server if the identify which the shopper is registering doesn’t exist within the WINS database. If the identify already exists within the database, the WINS server sends a NAME QUERY REQUEST message to the proprietor of the actual document to find out whether or not the identify continues to be lively. If the present proprietor responds with a POSITIVE NAME QUERY RESPONSE, the WINS server sends the brand new shopper a NEGATIVE NAME REGISTRATION RESPONSE message. On this case, the WINS server denies identify registration to the brand new shopper. If the present proprietor responds with a NEGATIVE NAME QUERY RESPONSE, the WINS server purges the prevailing document from its database, and assigns the identify to the brand new shopper.

  • WINS Identify Renewal: The NetBIOS names within the WINS database are registered for less than a selected time period. That is referred to as the TTL interval. The default TTL periodis 6 days. This principally signifies that the NetBIOS identify registrations with the WINS server is simply short-term. WINS shoppers subsequently should renew their names so as to stay present within the WINS database. As talked about earlier, the WINS database is dynamically updates. Shoppers can each register their names and un-register their names. That is accomplished on the configured time intervals, and is dependant on the TTL interval of registered names.
    The TTL interval is reset when the next occasions happen:

    • Each time a WINS shopper restarts, it registers its identify with the WINS server. This leads to the TTL interval being reset.

    • If nevertheless the WINS shopper stays logged on the community for half of the TTL interval, its begins sending NAME REFRESH REQUEST messages to the WINS server. The WINS server replies with a POSITIVE NAME REFRESH RESPONSE message that resets the TTL interval.

    If nevertheless the WINS server replies to a WINS shopper with a NEGATIVE NAME REFRESH RESPONSE message, the shopper has to register a unique NetBIOS identify with the WINS server. The prevailing identify registration is then cancelled.
    If the first WINS server is unavailale when the shopper makes an attempt identify renewal, the shopper repeats it request for identify renewal for every 10 minutes till an hour has handed. At this stage, the shopper will use a secondary WINS server if one is configured. If the secondary WINS server fails to reply, the shopper additionally repeats it request for identify renewal at 10 minutes intervals till an hour has handed. This means of switching WINS servers to aim identify renewal continues till both of the next occasions happen:

  • WINS Identify Launch: The WINS identify launch course of happens when WINS shoppers carry out the next occasions:

    When these occasions happen, the pc sends a NAME RELEASE REQUEST message to the WINS server. The message signifies that the registered NetBIOS identify ought to be expired within the WINS database. The identify is launched when the WINS server returns a POSITIVE NAME RELEASE RESPONSE message. On this case, the WINS server situated the NetBIOS identify and IP handle within the WINS database, and they matched to that of the sending shopper. A NEGATIVE NAME RELEASE RESPONSE message is shipped when the document for the NetBIOS identify within the WINS database holds a special IP handle to that of the sending WINS shopper.

NetBIOS shoppers use the Enhanced h-node (hybrid) sort for identify decision querying. Enhanced h-node sort makes use of the p-node sort (peer-to-peer) and b-node sort (broadcasts), and DNS to resolve NetBIOS names to IP addresses. Enhanced h-node sort is the default node sort used for Home windows 2000, Home windows XP, and Home windows Server 2003 NetBIOS shoppers who’ve a configured WINS server for identify decision. The order through which Enhanced h-node sort shoppers resolve NetBIOS identify are:

Issues for Implementing WINS Servers

Since Home windows 2000 was the primary Home windows working system the place NetBIOS naming was not required, you may nonetheless want to offer help for NetBIOS naming when you have legacy purposes. Keep in mind that all Home windows working system previous to Home windows 2000 require NetBIOS identify help.

A WINS server is usually not required for NetBIOS identify decision when your community is just a small LAN that resides on one bodily community phase, and there are not more than 50 shoppers.

To implement WINS, you solely want one WINS server for an internetwork. Nevertheless, implementing two WINS servers supplies fault tolerance for identify decision. The suggestions for implementing WINS servers are:

  • Implement two WINS servers. This offers fault tolerance for identify decision. The secondary WINS server can be used for identify decision if the first WINS server is unavailable to service WINS shoppers’ requests.

  • A WINS server can deal with 1,500 identify registrations and roughly four,500 identify queries per minute. It is suggested to have one WINS server and a backup server for every 10,000 WINS shoppers.

  • It is suggested to not use DHCP to configure the TCP/IP properties of the WINS server.

  • The WINS server have to be statically assigned with the next TCP/IP parameters:

    • A static IP handle

    • Subnet masks

    • Default gateway

How one can set up the WINS service utilizing Management Panel/Add or Take away Packages

  1. Click on Begin, and then click on Management Panel.

  2. Click on Add or Take away Packages.

  3. Click on Add/Take away Home windows Elements to start out the Home windows Element Wizard.

  4. In Window Elements web page, within the Elements listing, click on Networking Providers. Click on the Particulars button.

  5. Within the Networking Providers dialog field, choose the Home windows Web Identify Service (WINS) checkbox.

  6. Click on OK, and then click on Subsequent.

  7. The WINS service set up course of begins.

  8. Click on End.

Tips on how to set up the WINS service utilizing Management Panel/Community Connections window

  1. Click on Begin, and then click on Management Panel.

  2. Click on Community Connections.

  3. Proper-click Community Connections and choose Open from the shortcut menu.

  4. Click on Superior, and select Non-compulsory Networking Elements.

  5. Set up the WINS service via the Home windows Elective Networking Elements Wizard.

Configuring the WINS Server

Configuring the WINS server, and managing it consists of the next key administrative duties:

The MMC console used to configure the WINS server is the WINS console. The WINS console is mechanically added to the Administrative Instruments Menu if you set up the WINS service. By means of the WINS console, you possibly can carry out the next features:

  • View info on the configured WINS servers on the community.

  • Carry out WINS configuration duties, and administration duties.

  • View the contents of the WINS database, and find entries within the database.

To open the WINS console,

  1. Click on Begin, Administrative Instruments, and then click on WINS

As talked about beforehand, you need to implement redundancy in your WINS design in order that your WINS servers can push or pull database info between one another. This ensures that each one WINS database info is analogous for all of your WINS servers. The mechanism which can be utilized to implement redundancy in your WINS design is WINS replication. If all the knowledge within the WINS databases is identical, you’ll be able to configure NetBIOS shoppers with the IP addresses of quite a few WINS server. This ensures that WINS can nonetheless be used for identify decision if one of many WINS servers has a failure.

How you can configure WINS replication

To duplicate amongst one another, the WINS servers in your community need to be configured as replication companions. This may be carried out manually, or mechanically:

  • Manually configuring WINS server replication companions is completed by an administrator. It’s a must to know the WINS server identify or the IP tackle of the WINS server that you simply need to configure as a replication associate.

  • Mechanically creating WINS replication companions takes place by way of the Automated Associate Configuration function of Home windows 2000 and Home windows Server 2003.

Methods to manually configure WINS server replication companions

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, right-click the WINS server, and click on New Replication Associate on the shortcut menu.

  3. Within the New Replication Companion dialog field, enter the IP tackle of the WINS server that you really want replication to happen with.

  4. Click on OK

  5. Carry out the above course of on the opposite WINS server.

How you can mechanically create WINS replication companions

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, right-click Replication Companions, and then choose Properties from the shortcut menu.

  3. Click on the Superior tab.

  4. Choose the Allow A Associate Configuration checkbox.

  5. Click on OK.

The right way to configure WINS replication strategies

After the WINS replication companions are configured, you need to specify how replication will happen between your WINS servers. The 2 out there strategies are:

  • Pull replication: With pull replication, WINS knowledge is pulled by WINSserver1 from WINSserver2. This technique must be used if community connectivity between the WINS servers shouldn’t be as quick. The pull replication technique lets you configure when replication is to happen between your WINS servers.

  • Push replication: With push replication, WINS knowledge is pushed from WINSserver1 to WINSserver2. Push replication ought to be used when quick community connectivity exists between the WINS servers. With push replication, a selected quantity (Variety of modifications in model ID) signifies what number of modifications should happen within the WINS database earlier than replication happens. When the precise quantity is reached, a message is shipped to the replication associate, informing the companion that WINS knowledge must be replicated. To ensure that push replication to happen, the replication associate has to ship a constructive replication request message earlier than its push associate can push WINS knowledge modifications to it.

By default, when WINS replication companions are configured, each pull and push replication is specified. To view the prevailing replication technique(s),

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, choose Replication Companions

  3. Choose the replication companion whose replication technique you need to view within the Particulars pane.

  4. Proper-click on the precise replication companion, and then choose Properties from the shortcut menu.

  5. When the Properties dialog field for the precise replication associate opens, click on the Superior tab.

Learn how to configure pull replication

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, right-click Replication Companions, and then choose Properties from the shortcut menu.

  3. Click on the Pull Replication tab.

  4. Within the Hours, Minutes, and Seconds bins of the Begin Time subject, enter the time whenever you need pull replication to start out routinely. The default setting of all 0s signifies that pull replication doesn’t happen mechanically.

  5. Within the Hours, Minutes, and Seconds bins of the Replication Interval area, enter the pull replication time interval. The default setting is 30 minutes.

  6. Within the Quantity Of Retries area, enter what number of makes an attempt the WINS service ought to make to attach with a replication companion.

  7. Choose the Begin pull replication at service startup checkbox if you’d like pull replication to happen when the WINS service begins.

  8. Choose the Use persistent connections for pull replication companions checkbox if you need a connection to a replication associate to stay open for replication.

  9. Click on OK.

How you can configure push replication

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, right-click Replication Companions, and then choose Properties from the shortcut menu.

  3. Click on the Push Replication tab.

  4. Choose the At service startup checkbox if you need the WINS server to tell its replication companions of database modifications when the WINS service begins. The default setting is that this feature isn’t chosen.

  5. Choose the When handle modifications checkbox if you would like the WINS server to tell its replication companions of database modifications when tackle modifications happen. The default setting is that this feature shouldn’t be chosen.

  6. Within the Variety of modifications in model ID earlier than replication subject, specify what number of database modifications need to happen previous to replication companions being knowledgeable that push replication is ready to happen./li>

  7. Choose the Use persistent connections for pull replication companions checkbox if you’d like a connection to a replication companion to stay open for replication.

  8. Click on OK.

Easy methods to manually pressure replication with all replication companions

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, right-click Replication Companions, and then choose Replicate Now from the shortcut menu.

  3. Click on OK to the message requesting verification that guide replication ought to happen with all replication companions.

Methods to manually drive replication with a selected replication companion

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, choose Replication Companions, and then right-click the precise replication companion.

  3. Choose Begin Pull Replication from the shortcut menu if you wish to begin pull replication. Click on Sure to the message stating that the request might trigger can improve in community visitors. Click on OK to start out pull replication.

  4. Choose Begin Push Replication from the shortcut menu if you wish to begin push replication. When the Begin Push Replication dialog field seems, choose the Begin with this associate solely choice. Click on OK to start out push replication.

Configuring Superior WINS Configuration Choices

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, right-click the WINS server, and then choose Properties on the shortcut menu.

  3. Click on the Superior tab.

  4. Allow the Log detailed occasions to Home windows occasion log checkbox if you would like the WINS service to log WINS particular occasions within the System log of the WINS server. Enabling this feature for troubleshooting functions is advisable.

  5. Choose the Allow burst dealing with checkbox if you wish to allow the WINS server to concurrently deal with numerous requests. This superior choice setting is enabled by default. Select between the next choices: Low (300), Medium (500), Excessive (1,000), or Customized and then enter your personal quantity).

  6. You’ll be able to change the trail the place the WINS database and log information are situated within the Database Path field.

  7. Within the Beginning Model ID (hexadecimal) field, enter the quantity that will probably be used for the beginning model ID variety of the WINS database. The default setting is 1.

  8. Choose the Use pc names which might be suitable with LAN Supervisor checkbox if you’d like non-Microsoft NetBIOS shoppers to register with the WINS server. This setting is by default enabled.

  9. Click on OK.

Managing the WINS Database

The executive duties that you could carry out to mange the WINS database are:

  • Find WINS report entries within the WINS database: You should use the WINS console to find particular WINS entries or data. You possibly can filter data within the WINS database by:

    With Home windows 2000 WINS, you’ll be able to find entries within the WINS database utilizing the next search standards:

    • Report identify

    • Report proprietor.

    With Home windows Server 2003 WINS, you possibly can find entries within the WINS database utilizing the next search standards:

  • Add WINS data to the WINS database: Identify to IP tackle mappings might be added to the WINS database:

    • Dynamically: This occurs when a WINS shopper registers or renews NetBIOS names with the WINS server.

    • Manually: An administrator can manually add identify to IP addresses mappings to the WINS database.

  • Take away WINS data from the WINS database: This happens:

  • Confirm WINS database consistency:By means of verification of the consistency of the WINS data, you possibly can be sure that the WINS database solely accommodates present WINS entries. Checking database consistency assists you in figuring out incorrect WINS data within the WINS database.

  • Reconcile WINS data: That is the method whereby WINS data are verified, or validated. This ensures that the integrity of the data within the WINS database is maintained.

  • Manually compact the WINS database: You would wish to manually compact the WINS database to take care of the database measurement. The WINS database grows as extra WINS shoppers are added to it.

  • Again up and restore the WINS database

The WINS database is known as wins.mdb, and is situated within the following folder by default:

Learn how to view data within the WINS database

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, right-click the WINS server whose WINS database data you need to view, and then choose Show Data from the shortcut menu.

Methods to view particular data within the WINS database

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, right-click Lively Registrations and then choose Show Data from the shortcut menu.

  3. When the Show Data dialogue field opens, you may be introduced with the next tabs:

    • Report Mapping

    • Document House owners

    • Report Varieties

  4. You possibly can specify search parameters on every tab. When the search of the WINS database is carried out, it’ll embrace the info specified on every tab.

  5. You possibly can filter the search by:

  6. You possibly can choose the Allow outcome caching checkbox if you need the search outcomes cached regionally on the machine operating the question.

The right way to add WINS data to the WINS database

WINS solely dynamically provides entries to the WINS database for WINS enabled shopper. Shoppers that aren’t configured to make use of WINS don’t mechanically have their identify to IP tackle mappings added to the WINS database. You possibly can manually add document entries for non WINS enabled NetBIOS shoppers in order that your WINS shoppers can use WINS to question non WINS shoppers. Once you manually add report entries to the WINS database, the entries that you simply add are considered being static entries, or static identify to IP tackle mappings. These entries stay within the WINS database till they’re manually deleted.

The several types of static NetBIOS names which could be added to the WINS database are the identical as these names that WINS routinely registers:

  • Distinctive; identifies a singular NetBIOS identify to IP handle mapping.

  • Group; provides the entry to a workgroup the IP tackle is just not saved in WINS and is resolved by means of broadcasting.

  • Area Identify; identifies a website identify mapping of Home windows NT area controllers with a document entry.

  • Web Group; for creating teams to handle assets. This group is used for administration functions.

  • Multihomed; identifies a pc that has a number of interface playing cards with totally different IP addresses.

If you add static mappings to the WINS database, they by default override any conflicting dynamically added WINS report. You possibly can nevertheless configure this to not happen by way of enabling the Overwrite distinctive static mappings at this server(migrate on) choice. When the choice is enabled for a WINS server, all manually configured static mappings within the database are dealt with as dynamically added WINS data. The choice could be configured in another way (enabled/disabled) for every WINS server.

When WINS entries or data are added to the WINS database, they’re structured in a method that lets you type the data in line with area identify. The sector names within the WINS database are:

  • Report Identify; that is the registered NetBIOS identify that defines a singular identify, group, Web group or multihomed pc.

  • Sort;that is the service identifier, and its related hexadecimal worth.

  • IP Tackle;that is the IP tackle related to the NetBIOS identify.

  • State; data might be in both of the next states:

    • Lively: Signifies that the NetBIOS identify is at present getting used on the community.

    • Launched: Signifies that the NetBIOS identify of the report has been launched from the WINS database.

    • Tombstoned: Signifies a document that’s flagged to be deleted when the next extinction interval happens.

  • Static;signifies static entry.

  • Proprietor; signifies the WINS document’s proprietor.

  • Model; this can be a distinctive quantity assigned to a registered document that’s used throughout replication to find out probably the most present model of the document.

  • Expiration; signifies when (date, time) the lease of a report is because of expire.

How one can configure a static mapping within the WINS database

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, choose Lively Registrations, right-click it and then choose New Static Mapping from the shortcut menu.

  3. The New Static Mapping dialog field opens.

  4. Within the Pc Identify field, enter the NetBIOS pc identify of the non WINS NetBIOS shopper.

  5. For the NetBIOS Scope (optionally available) field, you possibly can depart the field empty, or you’ll be able to enter a NetBIOS scope identifier.

  6. Within the Sort field, choose one of many following entry varieties: Distinctive, Group, Area Identify, Web or Multihomed.

  7. Within the IP handle field, enter the IP handle for the pc.

  8. Click on Apply so as to add this entry to the WINS database.

  9. Add any further static mapping data, and click on Apply after including every entry.

  10. Click on OK.

The right way to configure the Overwrite distinctive static mappings at this server (migrate on) choice for a WINS server

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, choose Lively Registrations, right-click it and then choose Properties from the shortcut menu.

  3. On the Common tab, allow the Overwrite distinctive static mappings at this server (migrate on) checkbox.

  4. Click on OK.

How one can take away WINS data from the WINS database

The strategies that you should use to manually take away WINS data from the WINS database are:

  • Begin scavenging: This informs the WINS service to flag all data for deletion instantly.

  • Delete a WINS document from a single WINS server: That is carried out from inside the WINS database.

  • Tombstone a WINS report. This is able to replicate the deletion of the WINS document via your WINS topology. That is carried out from inside the WINS database.

Easy methods to begin scavenging of the WINS database

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, choose the precise WINS server whose database you need to provoke scavenging for.

  3. Proper-click the WINS server and then choose Scavenge Database from the shortcut menu.

  4. Click on OK within the message dialog field that seems.

How one can delet WINS data from inside the WINS database

You delete WINS data from inside the WINS database by choosing the document, and then urgent the Delete key on the chosen document. Urgent the Delete key on a WINS report shows the Delete Document dialog field, with the next choices:

  • Delete the report solely from this server: Choose this feature if you wish to delete the WINS report from this particular WINS server solely. Clicking OK after choosing this feature instantly removes the document from the WINS database.

  • Replicate deletion of this document to different servers (tombstoned): Choose this feature if you wish to replicate the deletion of the report by means of your WINS topology. The WINS document is tombstoned within the database, and is then marked to be replicated to the opposite WINS servers when the subsequent extinction interval happens. After choosing this feature, click on Sure to the WINS message that’s displayed, requesting possession to be taken of the actual WINS report.

How you can confirm WINS database consistency

Once you confirm the consistency of the WINS database, you’re principally figuring out whether or not the database has any incorrect data. Database consistency pulls WINS data from the opposite WINS databases, and then compares these data to the native WINS database.

The results of the examine results in both of the next occasions occurring:

  • For data within the native WINS database that match WINS data pulled from the opposite WINS databases, the native WINS document is time stamped with the document proprietor’s database.

  • For a WINS report the place the distant WINS document has a better model ID, the next happens:

You’ll be able to carry out WINS database consistency checks:

You possibly can carry out two forms of WINS database consistency checks:

  • Database consistency: The native WINS database’s consistency is verified with different WINS server databases.

  • Model consistency: This consistency verify takes place on every WINS server in your WINS topology, to find out whether or not every WINS server has the very best model ID quantity on every of its owned WINS data. WINS servers should not have possession of any WINS data which have been added to their databases by way of WINS replication.

The best way to manually confirm database consistency

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, right-click the precise WINS server that you simply need to carry out database consistency on and then choose Confirm Database Consistency from the shortcut menu.

  3. Click on Sure to confirm that you simply need to schedule database consistency for the WINS server, and to proceed together with your request.

  4. Click on OK to the second message that seems, indicating that the database consistency examine has been queued on the server.

  5. You’ll be able to seek the advice of the Home windows occasion log to examine when the database consistency verify has accomplished.

Methods to confirm model consistency

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, right-click the WINS server and then choose Confirm Model ID Consistency from the shortcut menu.

  3. Click on Sure to the message that’s displayed, requesting verification that you simply need to proceed with the model consistency operation.

  4. The Confirm Model ID Consistency Progress window shows, displaying the outcomes of the model consistency course of.

Tips on how to configure automated database verification

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, right-click the precise WINS server and ten choose Properties from the shortcut menu.

  3. When the Properties dialog field of the WINS server opens, click on the Database Verification tab.

  4. Choose the Confirm database consistency each: checkbox.

  5. Within the Hours field, enter how typically database verification ought to happen.

  6. Use the Start Verifying At: packing containers to set when database verification ought to begin.

  7. Enter the suitable worth within the Most variety of data verified every interval field.

  8. Choose whether or not you need the database ought to be verified towards:

  9. Click on OK.

Find out how to reconcile WINS data

Integrity of the WINS database and the validity of the WINS data within the database are achieved by means of reconciling your WINS database data.

There are two strategies of reconciling the WINS database:

Earlier than to trying to reconcile the WINS database, it is advisable to decide the next info

To reconcile WINS data,

  1. Click on Begin, Administrative Instruments, and then click on WINS to open the WINS console.

  2. Within the console tree, broaden the WINS server node, and then choose Lively Registrations.

  3. Proper-click Lively Registrations, and then choose Confirm Identify Data from the shortcut menu.

  4. The Confirm Identify Data dialog field that opens is split right into a Identify Data part, and a Servers part.

  5. Within the Identify Data part, choose the Record (case delicate) choice.

  6. Enter the identify of the WINS document(s) that you simply need to reconcile. The hexadecimal service locator ought to be included as nicely. Click on the Add button.

  7. Within the Servers part, choose the Record choice.

  8. Enter the IP handle of the WINS server(s) that you simply need to reconcile the simply specified WINS document towards. Click on Add.

  9. Click on OK to start out the verification of the WINS document(s).

  10. The Checking Names Registrations window shows the outcomes of the identify document verification course of.

How you can manually compact the WINS database

The WINS service routinely schedules for the WINS database to be compacted, by default. Nevertheless, you need to use the jetpack.exe software to manually compact the WINS database.

  1. Open a command immediate window

  2. Enter internet cease wins to cease the WINS database.

  3. Navigate to the situation of the WINS database.

  4. Enter jetpack wins.mdb temp_dbname.mdb to compact the WINS database.

  5. Enter internet begin wins to start out the WINS database.

Configuring WINS Shoppers

In an effort to use WINS to resolve NetBIOS names to IP addresses, you need to configure your shoppers as WINS shoppers. A pc operating any of the next working methods could be configured as WINS shoppers:

  • Home windows Server 2003

  • Home windows XP

  • Home windows 2000

  • Home windows NT three.5 or later

  • Home windows Me

  • Window 98 or Home windows 95

  • Home windows for Workgroups three.11 operating the Microsoft TCP/IP-32 stack.

  • Microsoft Community Shopper three.zero for MS-DOS

  • LAN Supervisor 2.2c for MS-DOS

  • Non Microsoft working methods reminiscent of Macintosh, Unix and Linux.

Tips on how to configure a WINS shopper

  1. Click on Begin, Management Panel, and then click on Community Connections.

  2. Choose Native Space Connection, and then click on Properties.

  3. The Native Space Connection Properties dialog field opens.

  4. Choose Web Protocol (TCP/IP) from the record, and then click on Properties.

  5. When the Web Protocol (TCPIP) Properties dialog field opens, click on Superior.

  6. The Superior TCP/IP Settings dialog opens.

  7. Click on the WINS tab.

  8. Click on the Add button so as to add the IP tackle of the WINS server(s).

  9. Within the TCP/IP WINS Server dialog field, enter the tackle of your WINS server and click on Add.

  10. Confirm that the WINS server you specified is displayed within the record on the Superior TCP/IP Settings dialog field.

  11. After including all of the WINS servers, use the arrow buttons to outline priority in your WINS servers. The WINS servers on the prime of the record are used earlier than these near the underside of the listing.

  12. Click on OK on the Superior TCP/IP Settings dialog field.

  13. Click on OK on the Web Protocol (TCP/IP) Properties dialog field.

  14. Click on OK on the Native Space Connection Properties dialog field.

Easy methods to configure WINS and DNS integration

  1. Click on Begin, Administrative Instruments, and then click on DNS.

  2. The DNS console opens.

  3. Increase the Ahead Lookup Zones container.

  4. Choose the zone which you need to configure.

  5. Proper-click the zone, and then choose Properties on the shortcut menu.

  6. When the Properties dialog field for the zone opens, click on the WINS tab.

  7. Choose the Use WINS ahead lookup checkbox.

  8. Enter the IP tackle of the WINS server, and click on Add.

  9. Click on the Superior button on the WINS tab.

  10. Enter the suitable worth within the Cache time-out field. This setting’s worth determines the period for which DNS servers are capable of cache WINS entries.

  11. Enter an applicable worth within the Lookup time-out field. The worth of this setting determines the time period for which a DNS server will look forward to a response from the WINS ahead lookup server.

  12. Click on OK.

How one can configure WINS and DHCP integration

The DHCP choices that you would be able to allow to configure DHCP to help WINS are:

  • 044 WINS/NBSN Servers: This feature lets you specify the IP addresses of the WINS servers within the order through which shoppers register and question for NetBIOS names. The IP tackle on the prime of the record is used as the first WINS server, and the IP addresses beneath it are used as secondary WINS servers.

  • 046 WINS/NBT Node Sort: This feature requires you to specify the node sort that you really want shoppers to make use of.

Different essential configuration settings for configuring WINS and DHCP help are:

  • Allow LMHOSTS Lookup; informs the shopper to seek for a configured LMHOSTS file within the %systemrootpercentsystem32drivers listing.

  • NetBIOS setting choices decide whether or not a shopper is configured for NetBIOS use:

    • Default: The seller particular setting in DHCP is used to find out if the shopper is enabled/disabled for NetBIOS use. The Disable NetBIOS over TCP/IP (NetBT) DHCP choice disables the shopper for NetBIOS use.

    • Allow NetBIOS over TCP/IP: This setting allows NetBIOS use.

    • Disable NetBIOS over TCP/IP: This setting disables NetBIOS use.

To configure DHCP for WINS help,

  1. Click on Begin, Administrative Instruments, and then click on DHCP.

  2. The DHCP console opens.

  3. Within the console tree, right-click Server Choices and then choose Configure Choices from the shortcut menu.

  4. When the Server Choices dialog field opens, choose the 044 WINS/NBNS Servers choice or the 046 WINS/NBT Node Sort choice.

Recent Comments

    Categories