Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I run up 'netsh' on my Windows XP box, and type


One of the options is wins (to change to the 'netsh wins' context).

From the netsh context I can type "wins" and I get into the wins context just fine.

Problem is, from another machine on the same domain, I can list netsh options, but wins is missing.

Why would this be?

share|improve this question

No idea, why this Windows XP is missing the WINS tool. Windows Vista's netsh doesn't include it, but it should be available on Windows XP.

As a workaround you could use Microsoft's

NBLookup.exe command-line tool

NBLookup is a command line diagnostic tool that uses the User Datagram Protocol (UDP) to send NetBIOS name queries to Microsoft Windows Internet Naming Service (WINS) servers. NBLookup requires TCP/IP version 4 to run. WINS servers accept name resolution requests on UDP port 137.

share|improve this answer
This is great! Thanks for the link. It perfectly solves my problem - and is better than using netsh. I've since figured out the answer to my original question though, so I'll put that down as the accepted answer. – christianlinnell Jun 16 '09 at 1:20
up vote 1 down vote accepted

Turns out the Windows 2003 Administration Tools Pack installs the WINS component into netsh.

share|improve this answer

What service pack of XP are you running?

I just fired up an XP SP1 vm, had a look at the command list and the winsock ("wins") is missing. So that machine looks like it needs to be upgraded to SP2 at least.

share|improve this answer
wins != winsock – splattne Jun 15 '09 at 7:40

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.