📖 ~1 min read
Table of contents
Symptom & Impact
UNC paths using hostnames fail while direct IP access works, disrupting file operations.
Environment & Reproduction
Mixed legacy environments relying on NetBIOS/WINS behavior.
ping fileserver
net use \fileservershare
Root Cause Analysis
Name resolution order is misconfigured, and NetBIOS over TCP/IP is disabled where still required.
Quick Triage
Test DNS, LLMNR, and NetBIOS lookup responses.
nslookup fileserver
nbtstat -a fileserver
Step-by-Step Diagnosis
Inspect node type, WINS settings, and SMB client errors.
ipconfig /all
nbtstat -n
Get-SmbConnection

Solution — Primary Fix
Correct DNS records and enable NetBIOS only where legacy dependencies exist.
Still having issues? Our Network Design team can diagnose and resolve this for you. Get in touch for a free consultation.
ipconfig /registerdns
nbtstat -R
nbtstat -RR

Solution — Alternative Approaches
Migrate legacy hostname dependencies to DNS and remove WINS reliance.
Add-DnsServerResourceRecordA -Name fileserver -ZoneName contoso.local -IPv4Address 10.0.30.10
Verification & Acceptance Criteria
SMB hostname access succeeds across affected clients.
Test-Path \fileservershare
Get-SmbMapping
Rollback Plan
Revert NetBIOS setting changes if specific legacy app behavior regresses.
wmic nicconfig where (IPEnabled=TRUE) call SetTcpipNetbios 0
Prevention & Hardening
Standardize DNS-based service discovery and phase out legacy name services.
Resolve-DnsName fileserver.contoso.local
Related Errors & Cross-Refs
Related to browser service deprecation and SMB signing policy mismatches.
Related tutorial: View the step-by-step tutorial for Windows Server 2016.
View all Windows Server 2016 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
Microsoft SMB and name resolution troubleshooting guidance.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.