Partager via

Use WINS commands interactively at the command prompt

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server 2008, Windows Server 2008 R2, Windows Server 8 Beta

To use WINS commands interactively at the command prompt

  1. Open Command Prompt.

  2. Type netsh.

  3. At the netsh> command prompt, type wins.

  4. At the wins> command prompt, type:

    **server\\**ServerName

    Or, type:

    serverip_address

    Where ServerName and ip_address are the server that you want to manage.

    Once a server that you have rights to manage has been successfully contacted, you should see "You have Read and Write access to the server ServerName."

  5. Once you are connected to this WINS server, you can use any supported command.

    Type /? or help to display the immediate WINS subcommand menu. Or, type list to display all of the Netsh subcommands that are available for use with WINS.

Notes

  • You must be a member of the Administrators group to change configuration information on WINS servers using the WINS console or the netsh wins commands. Administrator group membership should be restricted to the minimum number of users necessary to administer the server.

  • If there are users who need read-only access to the WINS console, add them to the WINS Users group instead of the Administrators group. WINS Users can search for WINS records and view replication partners and other configuration information, but they cannot change settings on the WINS server.

  • To open a command prompt, click Start, point to All programs, point to Accessories, and then click Command prompt.

Information about functional differences

  • Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.

See Also

Concepts

Managing WINS from the command line
Use WINS commands non-interactively or in scripts
Configure the command prompt