Leaked source code of windows server 2003
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

237 lines
9.3 KiB

  1. winscl.exe is a non-gui administration tool for WINS. It can be used
  2. for monitoring a WINS's activity and for examining its database.
  3. It can also be used for sending commands to WINS to initiate an activity
  4. such as replication, scavenging, registering a record, etc.
  5. Note: Unlike WINS Manager, winscl can not be used to configure a WINS.
  6. The following commands are supported by winscl
  7. RN - Register Name
  8. You can register a unique/multihomed/normal group/internet group names.
  9. QN - Query Name
  10. You can query any name in the wins db.
  11. DN - Delete Name
  12. Deletes a name. This action permanently gets rid of the name from the
  13. WINS db.
  14. GV - Get Version Counter Value
  15. Gets the current value of the version counter used to stamp records with
  16. version numbers
  17. GM - Get Mappings
  18. Gets the configuration intervals being used by WINS. These intervals
  19. are in secs. It also retrieves the priority class and the number of
  20. query threads in WINS. The owner id to address to version number mappings
  21. used by the replicator to determine how up-to-date the WINS db is relative
  22. to other WINSs is also retrieved. This command works only with an
  23. NT 3.51 WINS. Note: Owner Id is a number corresponding to a WINS address
  24. that is stored with a record in the WINS db. It indicates who the owner
  25. of the record is.
  26. GMO - Get Mappings (to be used with NT 3.5 WINS)
  27. Same as above except that this command should be used when connected to an
  28. NT 3.5 WINS.
  29. GST - Get Statistics
  30. Gets the various timestamps and statistics maintained by WINS. This command
  31. works only with an NT 3.51 WINS
  32. GSTO - Get Statistics (to be used with NT 3.5 WINS)
  33. Same as above except that this command should be used when going to an
  34. NT 3.5 WINS.
  35. PUSHT - Push Trigger
  36. Used to instruct the connected WINS to send a push trigger to another WINS.
  37. The local WINS will send a push trigger to the remote WINS only if either the
  38. remote WINS is listed under the Wins\Parameters\Push key in the registry or
  39. if RplOnlyWCnfPnrs value of the Wins\Parameters key in the registry is
  40. either non-existent or is set to 0. Likewise, the remote WINS will accept
  41. this trigger only of the local WINS is either listed listed under the
  42. Wins\Parameters\Pull key in its registry or if RplOnlyWCnfPnrs value of the
  43. Wins\Parameters key in its registry is either non-existent or is set to 0.
  44. Once the trigger is sent and accepted, the remote WINS, depending upon
  45. whether or not its db is out of sync with the connected WINS's db may or
  46. may not pull records from the local WINS.
  47. PULLT - Pull Trigger
  48. Used to instruct the connected WINS to send a pull trigger to another WINS.
  49. The local WINS will send a pull trigger to the remote WINS only if its db
  50. is out of sync with it and if and only if the remote WINS is either listed
  51. under the Wins\Parameters\Pull key or if RplOnlyWCnfPnrs value of the
  52. Wins\Parameters key either non-existent or is set to 0. Likewise,
  53. the remote WINS will accept this trigger only of the local WINS is either
  54. listed listed under the Wins\Parameters\Push key in its registry or if
  55. RplOnlyWCnfPnrs value of the Wins\Parameters key in its registry is either
  56. non-existent or is set to 0.
  57. SI - Statically Initialize WINS
  58. Used to statically initialize WINS from a file which has records in
  59. the format used in an lmhosts file.
  60. CC - Use this command to initiate Consistency Checking on WINS. Consistency
  61. checking results in WINS communicating with other WINSs to check the
  62. consistency of its database. THIS OPERATION RESULTS IN HIGH OVERHEAD
  63. ON THE WINS AND ALSO CAN HOG UP NETWORK BW (A FULL REPLICATION IS DONE).
  64. If you have a large database, you should probably do this at times when
  65. there is less network traffic.
  66. SC - Scavenge records
  67. Used to instruct WINS to scavenge records. This means that records that
  68. are old enough to be released will be released. Those that need to be
  69. made extinct will be made so. Extinct records that need to be deleted
  70. will be deleted. replica records that need to be verified will be verified.
  71. DRR - Delete all or a range of records
  72. Used to deleted records by giving the range of version numbers. You can
  73. delete all records of a WINS too. Only the records owned by the WINS
  74. selected (when prompted) will be deleted. Other information regarding
  75. the WINS, such as highest version number pulled, will not be deleted.
  76. PRR - Pull all or a range of records
  77. Used to pull a range of records from another WINS. The range is given
  78. in terms of version numbers. If the range being pulled overlaps records
  79. of the remote WINS already there in the WINS db, they will first be
  80. deleted before the new records are pulled. This command is used to pull
  81. record(s) that somehow never got replicated and have no chance of
  82. replicating unless their version number becomes more than the highest the
  83. local WINS has for the remote WINS.
  84. Again, like the PULLT command, the replication will happen only after the
  85. appropriate registry check (refer: PULLT command)
  86. GRBN - Get record by Name
  87. Retreives one or more records starting with a string. The names of
  88. records are lexicographically sorted in the WINS db (Exception:
  89. Names with 0x1B in the 16th byte are stored with the 1st and 16th byte
  90. transposed - they are displayed correctly). You are given a choice to
  91. search the db from the beginning or the end. So, if you want to retrieve
  92. lets say 100 names starting with Z, it is a good idea to specify that
  93. WINS should search the names from the end of the db. This will cause
  94. less overhead on WINS.
  95. GRBV - Get records by version numbers
  96. Retrieve records from the local WINS db by specifying the range of
  97. version numbers.
  98. BK - Backup the WINS db.
  99. Backup the WINS db to a directory on the same machine as WINS.
  100. RSO - Restore the WINS db (db created by WINS prior to SUR)
  101. Restores the WINS db to the directory it was backed up from. NOTE: WINS
  102. SHOULD NOT BE RUNNING WHEN YOU RUN THIS COMMAND.
  103. RS - Restore the WINS db (db created by WINS in SUR or beyond)
  104. Restores the WINS db to the directory it was backed up from. NOTE: WINS
  105. SHOULD NOT BE RUNNING WHEN YOU RUN THIS COMMAND.
  106. RC - Reset WINS counters
  107. Resets the WINS counters displayed via GST (or GSTO for NT 3.5 WINS) to
  108. 0.
  109. CR - Count records in the db.
  110. Counts the number of records for an owner in the WINS db. The owner
  111. is identified by the address. You can either count all or a range of
  112. records. NOTE: this can be a high overhead operation when the records
  113. being counted are a lot.
  114. SDB - Search the db
  115. Search the database for records for a record with a particular name or
  116. address. NOTE: When the db contains a lot of records, this can be
  117. a time-consuming and "consistent overhead" operation on WINS.
  118. GD - Get domain names
  119. Gets the list of domain names registered in the WINS db. These are the
  120. 1B names (0x1B in the 16th byte) registered by PDCs of the domains.
  121. DW - Delete Wins
  122. This deletes all the information relevant to a WINS (identified by its
  123. address) from the db of the connected WINS. This includes all records
  124. belonging to the WINS as well as administrative information kept for the
  125. WINS. When the connected WINS is specified for deletion, all its records
  126. are deleted. Other information such as highest version number of records
  127. in db. is not removed.
  128. CW - Connect to Wins
  129. MENU - Show MENU
  130. NOMENU - Don't show MENU (helpful if you don't want to clutter up the output
  131. from a script driving the tool).
  132. Used to connect to another WINS
  133. EX - Exit the tool
  134. Points to Note:
  135. 1) Addresses of WINS should be given in dotted decimal notation
  136. 2) A version number is 64 bits long. When prompted for it, it should be
  137. given in decimal with the high word first followed by the low word
  138. The two words should be seperated by a space.
  139. 3) Many commands such as PULLT, PUSHT, SI, PRR, etc are executed
  140. in the background. A return status of SUCCESS indicates that the
  141. command has been queued to WINS for execution. It does not mean that
  142. WINS has successfully executed the command.
  143. 4) winscl is case sensitive. So, BOB is different from bob or Bob (when
  144. input to RN, QN, DN, etc).
  145. 5) Scope if given should be in domain name form - explained in
  146. rfc 883. Example: netbios.com.
  147. 6) Whenever a pull (or a push) replication is done, the local WINS will
  148. send a request for it to the remote WINS only if the remote WINS is
  149. either listed under the Wins\Parameters\Pull (or Push) key or
  150. if RplOnlyWCnfPnrs value of the Wins\Parameters key is either
  151. non-existent or is set to 0. Likewise, the remote WINS will accept
  152. the above request only if the WINS making the request is either
  153. listed under the Wins\Parameters\Push (or Pull) key or if
  154. the RplOnlyWCnfPnrs value of the Wins\Parameters key is either
  155. non-existent or is set to 0.
  156. The two WINSs look up the above keys/values in their local registries.
  157. 7) When prompted for Version Number, give it in the following form
  158. <high word> <long word>. Example 0 9567. The numbers are in decimal.