You cannot query a WINS server directly with nslookup. nslookup sends DNS queries, while WINS resolves NetBIOS computer names. To test a Windows client’s NetBIOS/WINS-related resolution, use nbtstat. If you specifically need an nslookup-style test, query a DNS server configured to use WINS integration as a fallback.
Why nslookup cannot query WINS
DNS and WINS use different namespaces and protocols:
As an Amazon Associate I earn from qualifying purchases.
| Service | Resolves | Typical diagnostic |
|---|---|---|
| DNS | DNS names and records, such as server.example.com |
nslookup or Resolve-DnsName |
| WINS | NetBIOS computer and service names | nbtstat and WINS management tools |
| Local NetBIOS mechanisms | Names from cache, broadcast, LMHOSTS, or WINS | nbtstat /c, nbtstat /r, and nbtstat /n |
WINS is Microsoft’s implementation of NetBIOS Name Service, not an older form of DNS. Microsoft documents WINS as a legacy name-resolution service separate from the DNS namespace.
This command is therefore not a valid WINS test:
nslookup FILESERVER 10.10.10.20The second argument tells nslookup which DNS server to contact. It does not change the request into a WINS query. If 10.10.10.20 runs only WINS, the command may time out or report that there was no response. If that computer also runs DNS, a successful response proves only that its DNS service answered.
#1 Best Overall
The same applies inside interactive nslookup:
server DNS_NAME_OR_IP
lserver DNS_NAME_OR_IPBoth commands select DNS servers. The distinction between server and lserver concerns how the DNS server name is resolved; neither command selects a WINS server. See Microsoft’s nslookup documentation and server parameter documentation.
Use nbtstat for a NetBIOS or WINS-related test
nbtstat tests NetBIOS behavior using the client’s configured resolution mechanisms. It does not offer an nslookup-style option for specifying an arbitrary WINS server, and a successful lookup does not automatically prove that WINS supplied the answer. Cache, broadcast, LMHOSTS, and WINS can all affect the result.
1. Identify configured WINS servers
netsh interface ipv4 show winsserversFor one interface:
netsh interface ipv4 show winsservers name="Ethernet"These commands show WINS servers configured on the client. The settings may have been supplied by DHCP or configured statically. If no WINS server is listed, the client may be using broadcast, LMHOSTS, or another local NetBIOS mechanism instead.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →2. Check NetBIOS resolution statistics
nbtstat /rThis displays NetBIOS name-resolution statistics, including activity associated with WINS.
3. Inspect the local cache
nbtstat /cA cached entry can make a name appear to resolve without demonstrating that the WINS server answered the current request.
4. Query a remote computer by NetBIOS name
nbtstat /a FILESERVERThis requests the remote computer’s NetBIOS name table by name. Replace FILESERVER with the target’s NetBIOS computer name.
5. Query a known target by IPv4 address
nbtstat /A 10.10.10.25The uppercase /A indicates that the target is an IP address rather than a remote NetBIOS name. This avoids ambiguity in the name-resolution step and tests whether the target responds to NetBIOS name-table requests.
6. Refresh the local WINS registrations
nbtstat /RR/RR releases and refreshes the local computer’s NetBIOS names registered with WINS. It is a registration operation, not a general-purpose query for an arbitrary WINS record.
To clear the local NetBIOS cache and reload pre-tagged LMHOSTS entries, use:
nbtstat /RMicrosoft lists these options in the nbtstat command reference.
A practical diagnostic sequence
From an elevated or regular Command Prompt, depending on your environment, run:
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallnetsh interface ipv4 show winsservers
nbtstat /r
nbtstat /c
nbtstat /R
nbtstat /a FILESERVERIf you know the target address, also run:
nbtstat /A 10.10.10.25Compare the results carefully. A failed name-based test but successful IP-based test points toward name-resolution, registration, or configuration issues. A failure with both forms may indicate that the target is offline, NetBIOS over TCP/IP is disabled, traffic is filtered, or the target has no usable NetBIOS registration.
How to use nslookup indirectly through DNS WINS integration
Windows Server DNS can be configured with a WINS resource record in a forward lookup zone. When DNS cannot find a matching A record, the DNS server can use the host portion of the request to send a NetBIOS name request to WINS and return the result to the DNS client as an A-record-style response.
After an administrator enables WINS lookup integration on the relevant DNS zone, query the DNS server:
nslookup FILESERVER.example.com 10.10.10.10This means:
- Incorrect: “
nslookupqueries WINS.” - Correct: “
nslookupqueries DNS, and that DNS server may use WINS as a configured fallback.”
Microsoft describes this DNS WINS integration as a compatibility feature. To troubleshoot it, verify that:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- The selected DNS server hosts or serves the relevant forward lookup zone.
- WINS integration is enabled for that zone.
- The DNS server can reach the configured WINS server.
- The host portion of the DNS name matches the NetBIOS name registered in WINS.
- A stale or incorrect DNS A record is not taking precedence over WINS fallback.
- The request is not being sent to a different DNS server that lacks the WINS-enabled zone.
Normal DNS commands remain DNS operations even when WINS fallback is enabled:
nslookup FILESERVER.example.com
nslookup -debug FILESERVER.example.com 10.10.10.10
nslookup -type=A FILESERVER.example.com 10.10.10.10A successful result proves that DNS returned an answer. It does not, by itself, reveal whether that answer came from a DNS record or a WINS fallback lookup.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting common failures
“No response from server” or a timeout
If you used nslookup NAME WINS_IP, the failure is expected when the address provides WINS but not DNS. Repeat the test with nbtstat /a NAME after checking the client’s WINS configuration.
No WINS server is configured
netsh interface ipv4 show winsservers may show no server. In that case, determine whether the environment intentionally relies on broadcast or LMHOSTS. A NetBIOS name can sometimes resolve without WINS, but that does not prove that a WINS service is available.
The cache contains an old mapping
Use nbtstat /c to inspect the cache and nbtstat /R to clear it. Cache clearing does not guarantee that the next lookup will use WINS; the client may use broadcast or another configured method.
Best Value
The target is not registered
The target may be offline, its registration may have expired, NetBIOS over TCP/IP may be disabled, or the computer may not be using WINS. If the local computer’s own registration is stale, nbtstat /RR can release and refresh its names.
DNS works but NetBIOS does not
This is possible and is not contradictory. DNS and WINS resolve different namespaces. A successful nslookup does not validate WINS connectivity, and a failed nbtstat test does not indicate that DNS is broken.
The WINS server also runs DNS
An nslookup command may succeed against the WINS server’s IP address if that computer also provides DNS. The result still proves only that DNS answered. Check the DNS record and zone configuration rather than treating the response as evidence of a direct WINS query.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsReverse lookups do not work as expected
Do not treat WINS as a normal reverse-DNS database. WINS is not indexed by IP address in the same way DNS supports PTR records. Windows DNS has WINS-R behavior for reverse zones, but Microsoft explains that it uses a node adapter status request to the target IP rather than performing a conventional reverse lookup against a WINS database. See the Microsoft WINS lookup documentation.
Quick reference
| Goal | Command or method | What it proves |
|---|---|---|
| Query DNS directly | nslookup name dns-server |
Tests DNS resolution through the selected DNS server |
| Test a NetBIOS name | nbtstat /a name |
Tests NetBIOS behavior using the client’s configured mechanisms |
| Test a known NetBIOS target | nbtstat /A address |
Tests the target by IPv4 address |
| View configured WINS servers | netsh interface ipv4 show winsservers |
Shows client WINS configuration |
| Inspect NetBIOS cache | nbtstat /c |
Shows previously learned local mappings |
| Refresh local WINS registrations | nbtstat /RR |
Releases and refreshes this computer’s registered names |
| Use nslookup with legacy names | Query a DNS server with WINS integration enabled | Tests DNS-mediated WINS fallback, not direct WINS access |
Should you still use WINS?
WINS remains documented for legacy compatibility, but Microsoft classifies it as legacy and recommends migrating to DNS-only name resolution where feasible. WINS integration can bridge older systems during a migration, but it preserves a dependency on NetBIOS and should not be mistaken for a modern replacement for DNS. See Microsoft’s WINS guidance and migration context.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
