WINS Error 0X00000FA5 Fix: Name Not in Database

This Error Is Annoying — Let's Fix It Fast

You're staring at a WINS error that says the name doesn't exist, and the exact code is 0X00000FA5. I know that sinking feeling when network shares or legacy apps just stop working. The good news: you can resolve this in under five minutes. Let's get your NetBIOS name back online.

The Quick Fix: Add a Static Mapping

The most reliable fix is to create a static mapping in WINS. This bypasses dynamic registration issues. Here's how:

Open the WINS console on your Windows Server (typically Server 2012 R2, 2016, or 2019).
Expand your WINS server, right-click Active Registrations, and select New Static Mapping.
Enter the computer name (e.g., FILESRV01), its IP address, and select the NetBIOS service type (usually Unique for a single IP).
Click Apply and then OK.

That's it. The error should vanish immediately for queries against that name. If you're dealing with multiple names, repeat for each. This works because WINS treats static mappings as authoritative — they never get scavenged or purged automatically.

Why This Error Happens

WINS databases are dynamic. Records can disappear for three main reasons:

Scavenging: WINS runs a cleanup process every few hours. If a computer didn't renew its registration (maybe it was offline or the NetBIOS service crashed), the record gets tombstoned and eventually deleted.
Replication lag: In multi-WINS environments, if one server holds the record but hasn't replicated it to another, queries hit the empty server and boom — 0X00000FA5.
Manual deletion: Someone might have removed the record accidentally during cleanup.

The static mapping sidesteps all these issues. It's your safety net.

Less Common Variations and Deeper Fixes

Force a Client Refresh

If the computer is still alive and you'd rather not use a static mapping, force it to re-register. On the client machine (the one that owns the name), open a command prompt as admin and run:

nbtstat -RR

This sends a name release and refresh to the WINS server. Wait 30 seconds, then check the WINS console under Active Registrations for the name. If it appears, you're good. I've seen this fix work on Windows 10 and Windows Server 2022 right after a network team changed something on the switch.

Check WINS Replication Partners

In a multi-server setup, the error might only occur on one WINS server. Verify replication:

Open the WINS console, right-click Replication Partners, and select Replicate Now.
Check if the missing name shows up on the partner after a few seconds. If not, your replication configuration might be broken — check push/pull settings.
Also look for version ID inconsistencies. If version IDs between servers drift too far, records can be rejected. Reset the highest version ID on the server that has the record.

Real world: I once spent two hours on this only to find a firewall blocking UDP 137 between WINS servers. A quick telnet test (yes, I still use it) revealed the block.

Use nbtstat to Verify Name Ownership

Sometimes the name exists but the error is triggered by a query against a stale cache. On the client, run:

nbtstat -c

This shows your local NetBIOS name cache. If the IP is wrong, clear it with nbtstat -R and try again. Then re-register with nbtstat -RR.

Preventing This in the Future

You don't want to keep battling this. Here's how to stop it:

Set static mappings for critical servers like domain controllers, file servers, and printers. They don't change IP often, so static entries are safe and eliminate refresh failures.
Tune scavenging intervals on your WINS server. Default is 3 days for renewal, 6 days for extinction, and 6 more for tombstone deletion. That's fine for most, but if you have flaky clients, lengthen the renewal to 7 days so they don't drop off during a weekend outage.
Monitor replication health weekly. Use the WINS console's Verify Server Version ID Consistency option under Replication Partners. If you see version ID mismatches, fix them before records vanish.
Log WINS events — enable logging in the WINS console (right-click server, Properties, Advanced tab). Look for warnings about scavenging or replication failures.

One last thing: if you're migrating off WINS (good idea in 2024), but hitting this error on legacy apps, static mappings buy you time. Just don't forget to remove them after migration — they'll cause duplicate name errors later.

That's it. You should have the error squashed and a plan to keep it gone. If you're still stuck, check DNS — sometimes people confuse WINS with DNS. Totally different, but both can give you a headache.