Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →“The name service is unavailable” is the Windows status RPC_NT_NAME_SERVICE_UNAVAILABLE. It means the computer could not complete a name-resolution or service-discovery request; it does not identify one failed component. The cause may be DNS, legacy NetBIOS/WINS resolution, RPC endpoint discovery, a disabled Net Logon dependency, or a firewall, VPN, or network ACL blocking the path. Work through the diagnostic sequence below before restarting services, because the logs often identify the real fault.
What the error means
Windows uses several layers to turn a computer, domain, share, or service name into a reachable endpoint. DNS normally supplies host records and the service-location records used by Active Directory. Older environments may still use NetBIOS name resolution or WINS. After a name is resolved, RPC, SMB, LDAP, or another protocol must reach the destination. A failure at any of those stages can produce the same published message.
As an Amazon Associate I earn from qualifying purchases.
The status therefore does not prove that DNS is broken. A workstation can resolve a name correctly and still fail because Net Logon is stopped, an RPC dynamic port is filtered, a VPN is routing only part of the traffic, or a dependency service cannot start. The same error can appear during domain sign-in, access to a network share or printer, remote administration, or an application that calls a Windows service.
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 minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Microsoft describes Net Logon as maintaining a security channel between a computer and a domain controller for authenticating users and services. Net Logon also publishes service-location records in DNS and relies on RPC, LDAP, SMB, and, in some deployments, NetBIOS paths. A problem in that chain is why a domain-controller discovery error can look like a generic name-service failure.
#1 Best Overall
- DUAL-BAND WIFI 6 ROUTER: Wi-Fi 6(802.11ax) technology achieves faster speeds, greater capacity and reduced network congestion compared to the previous gen. All WiFi routers require a separate modem. Dual-Band WiFi routers do not support the 6 GHz band.
- AX1800: Enjoy smoother and more stable streaming, gaming, downloading with 1.8 Gbps total bandwidth (up to 1200 Mbps on 5 GHz and up to 574 Mbps on 2.4 GHz). Performance varies by conditions, distance to devices, and obstacles such as walls.
- CONNECT MORE DEVICES: Wi-Fi 6 technology communicates more data to more devices simultaneously using revolutionary OFDMA technology
- EXTENSIVE COVERAGE: Achieve the strong, reliable WiFi coverage with Archer AX1800 as it focuses signal strength to your devices far away using Beamforming technology, 4 high-gain antennas and an advanced front-end module (FEM) chipset
- OUR CYBERSECURITY COMMITMENT: TP-Link is a signatory of the U.S. Cybersecurity and Infrastructure Security Agency’s (CISA) Secure-by-Design pledge. This device is designed, built, and maintained, with advanced security as a core requirement.
DNS and NetBIOS/WINS are not interchangeable
| Resolution method | Where it is normally used | What to check |
|---|---|---|
| DNS | Modern Windows and Active Directory discovery | The client’s assigned DNS servers, host records, and Active Directory SRV records; DNS uses UDP and TCP port 53. |
| NetBIOS name service | Legacy name resolution or fallback when NetBIOS over TCP/IP is enabled | UDP 137 reachability and whether the network still provides the expected NetBIOS behavior. |
| WINS | Older, centrally managed NetBIOS deployments | Whether the WINS server is available and whether clients point to the correct address. |
Do not replace a domain DNS server with a public resolver when Active Directory discovery is required. A public resolver may answer ordinary internet names but will not contain the organization’s private host and service records.
Run this diagnostic sequence before changing anything
-
1. Confirm the scope
Write down the operation that failed, such as domain logon, opening one share, finding a printer, or running a remote administration task. Test whether the problem affects one computer, one named host, one share, an entire site, or every client. If only one machine fails, prioritize its local DNS assignment, services, cache, and firewall. If every client fails, investigate the domain DNS service, domain controller, VPN concentrator, or network ACL first.
-
2. Capture the exact evidence
Record the complete message, any numeric code, the application that displayed it, the target name, and the time. In Event Viewer, open Windows Logs > System and save events from the failure window. Service Control Manager Event ID 7001 indicates that a dependency failed; Event ID 7003 indicates an invalid or missing dependency. Also note any Netlogon entries on a domain controller or affected workstation. Do this before rebooting, because a restart can remove the transient state that explains the failure.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
3. Check the client’s network configuration
In Windows, open Settings > Network & internet, select the active Ethernet or Wi‑Fi connection, and inspect the assigned DNS servers. On managed computers, compare the values with a working client on the same network. A manually entered address, a stale VPN adapter, or a DHCP scope that supplies the wrong resolver can send domain queries to a server that cannot answer them.
-
4. Test the names, not just the internet connection
Use
nslookupfrom the affected client to query the target host, the domain name, and the domain controller name. Repeat the query against each configured DNS server if the tool permits it. A successful lookup should return the expected address, not an obsolete address or a response from an unrelated resolver. For Active Directory, query the required service-location records as well; a host record alone does not prove that a domain controller can be located. -
5. Inspect services and dependencies
Open
services.mscand check Net Logon, Workstation, and the RPC-related services shown in their Dependencies tabs. A service that is set to Disabled when the deployment expects it to start will prevent the dependent service from operating. Do not change a dependency at random: use Event ID 7001 or 7003 to identify the named service, then confirm its executable path and startup configuration.Rank #2
Sale
TP-Link AC1200 WiFi Router Dual Band Wireless Internet Router (Archer A54) | 4 x 10/100 Mbps Fast Ethernet Ports, EasyMesh Compatible, Support Guest WiFi, Access Point Mode, IPv6 & Parental Controls- Dual-band Wi-Fi with 5 GHz speeds up to 867 Mbps and 2.4 GHz speeds up to 300 Mbps, delivering 1200 Mbps of total bandwidth¹. Dual-band routers do not support 6 GHz. Performance varies by conditions, distance to devices, and obstacles such as walls.
- Covers up to 1,000 sq. ft. with four external antennas for stable wireless connections and optimal coverage.
- Supports IGMP Proxy/Snooping, Bridge and Tag VLAN to optimize IPTV streaming
- Access Point Mode - Supports AP Mode to transform your wired connection into wireless network, an ideal wireless router for home
- Advanced Security with WPA3 - The latest Wi-Fi security protocol, WPA3, brings new capabilities to improve cybersecurity in personal networks
-
6. Test the route through policy controls
Check the local Windows firewall, site firewall, VPN profile, and inter-site ACLs. A ping or a successful DNS lookup does not prove that RPC, SMB, or LDAP traffic is allowed. Test from the affected network segment to the actual domain controller or file server, and compare the result with a working segment. Keep the original logs open while testing so you can correlate blocked connections with the event time.
Recommended Free Tools
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Fix a DNS or Active Directory discovery failure
Correct the DNS server assignment
For a domain-joined Windows client, configure the network adapter to use the organization’s internal DNS service that hosts or forwards the Active Directory zone. If DHCP supplies DNS addresses, correct the DHCP scope rather than applying a one-off setting to every workstation. If the machine has both a physical adapter and a VPN adapter, verify which interface receives the domain DNS server and which interface supplies the default route.
After correcting the assignment, resolve the domain name, the domain controller’s host name, and the relevant Active Directory service records. The expected address should belong to a reachable controller in the correct site. If the record is missing, stale, or points to a decommissioned controller, repair the zone and replication rather than masking the problem with a hosts-file entry.
Check the DNS Server service and records
The DNS Server service answers name queries and is required for locating devices and Active Directory domain controllers. On the DNS server, verify that the service is running and that the authoritative zone is loaded. Confirm that the zone contains the controller’s host records and the service-location records that clients use for domain discovery. A server can be online while its zone is unavailable, not replicated, or populated with outdated records.
DNS queries use both UDP and TCP port 53. A firewall that allows only one transport can produce intermittent behavior: small responses may work over UDP while larger responses or fallback traffic fail over TCP. Permit both transports between clients, DNS servers, and any forwarding path required by the design.
Do not use a public resolver as an Active Directory substitute
Public DNS can be appropriate for internet names, but it is not a replacement for the private DNS service that contains a domain’s controller and service records. If a client needs both internal and external resolution, use the organization’s DNS servers with the intended forwarding configuration. Splitting requests between unrelated resolvers can make one application work while domain logon or share discovery continues to fail.
Rank #3
- NIGHTHAWK WIFI 6 ROUTER FOR YOUR WHOLE HOME: Delivers fast, reliable WiFi across every room of your apartment or small home for streaming, gaming, video calls, and smart home devices, all running at the same time without slowing each other down.
- WORKS WITH YOUR EXISTING INTERNET SERVICE: Pairs with your existing modem or gateway via ethernet. Compatible with most cable, fiber, DSL, and satellite providers. Some gateways and modem router combos may require bridge mode. No coax needed.
- SET UP AND MANAGE YOUR NETWORK WITH THE NIGHTHAWK APP: Download the free Nighthawk app on iOS or Android for guided setup. Manage WiFi, run speed tests, pause devices, and set up guest networks from anywhere. Active internet required.
- READY FOR THE DEVICES YOU ALREADY OWN: Your phones, laptops, and TVs work right out of the box. WiFi 6 delivers speeds up to 1.8 Gbps across 2.4 GHz and 5 GHz bands. Backward compatible with WiFi 5 and earlier.
- COVERAGE IN EVERY ROOM: Covers up to 1,500 sq. ft. for up to 20 connected devices. Walls, floors, and interference can reduce range. Larger or multi-story homes may benefit from a NETGEAR Orbi mesh WiFi system.
Repair Net Logon and dependency failures
Identify the failed dependency from Event Viewer
Event ID 7001 reports that a required dependency failed; Event ID 7003 reports an invalid or missing dependency. Open the event’s details and note the exact service name. In services.msc, open that service’s properties and inspect its Dependencies tab. Check whether the dependency is stopped, disabled, configured with an invalid executable path, or unable to load a required DLL.
Microsoft’s service troubleshooting guidance also calls out invalid registry values, missing executables or DLLs, and restrictive permissions. If the event names a dependency that should start automatically, restore its intended startup mode, start it, and then start Net Logon. If the dependency data itself is wrong, verify the DependOnService registry value against a known-good system or documented build before editing it. Export the relevant key first and avoid deleting entries simply to make the service start.
Start services in the correct order
- Resolve the dependency error and start the named dependency.
- Confirm that the Workstation service is running on a client that needs SMB or domain resources.
- Start or restart Net Logon only after its dependencies are healthy.
- Refresh the original operation and watch the System and Netlogon logs for a new failure.
Net Logon maintains the computer’s secure channel to a domain controller. If it starts and immediately stops, the service state is a symptom rather than the root cause; return to the dependency event, missing-file check, DNS records, and network path instead of repeatedly restarting it.
Free tools Windows power users keep installed
One-click scans. No signup required.
Validate the secure channel after service repair
Once Net Logon remains running, verify that the client can locate a reachable domain controller and that the original domain operation succeeds. A running service alone is insufficient if the secure channel cannot reach its controller through the required RPC, LDAP, SMB, and DNS paths.
Investigate a paused Net Logon service
A paused Net Logon service on a domain controller has a specific effect: the controller does not answer DC Locator requests and is not used for NTLM authentication or for issuing new Kerberos tickets. Microsoft notes that a paused service does not respond to DC Locator requests on LDAP port UDP 389. This can make several otherwise healthy clients report that the name service is unavailable.
Inspect the Netlogon log for messages such as Netlogon Service Paused, Waiting for RPCSS, or SysVol not ready. Correct the condition named by the message—such as an RPC service that has not initialized or a SYSVOL readiness problem—before resuming Net Logon. Resuming a service without fixing the underlying condition can leave discovery and authentication unreliable.
Rank #4
- 𝐅𝐮𝐭𝐮𝐫𝐞-𝐑𝐞𝐚𝐝𝐲 𝐖𝐢-𝐅𝐢 𝟕 - Designed with the latest Wi-Fi 7 technology, featuring Multi-Link Operation (MLO), Multi-RUs, and 4K-QAM. Achieve optimized performance on latest WiFi 7 laptops and devices, like the iPhone 16 Pro, and Samsung Galaxy S24 Ultra.
- 𝟔-𝐒𝐭𝐫𝐞𝐚𝐦, 𝐃𝐮𝐚𝐥-𝐁𝐚𝐧𝐝 𝐖𝐢-𝐅𝐢 𝐰𝐢𝐭𝐡 𝟔.𝟓 𝐆𝐛𝐩𝐬 𝐓𝐨𝐭𝐚𝐥 𝐁𝐚𝐧𝐝𝐰𝐢𝐝𝐭𝐡 - Achieve full speeds of up to 5764 Mbps on the 5GHz band and 688 Mbps on the 2.4 GHz band with 6 streams. Enjoy seamless 4K/8K streaming, AR/VR gaming, and incredibly fast downloads/uploads.
- 𝐖𝐢𝐝𝐞 𝐂𝐨𝐯𝐞𝐫𝐚𝐠𝐞 𝐰𝐢𝐭𝐡 𝐒𝐭𝐫𝐨𝐧𝐠 𝐂𝐨𝐧𝐧𝐞𝐜𝐭𝐢𝐨𝐧 - Get up to 2,400 sq. ft. max coverage for up to 90 devices at a time. 6x high performance antennas and Beamforming technology, ensures reliable connections for remote workers, gamers, students, and more.
- 𝐔𝐥𝐭𝐫𝐚-𝐅𝐚𝐬𝐭 𝟐.𝟓 𝐆𝐛𝐩𝐬 𝐖𝐢𝐫𝐞𝐝 𝐏𝐞𝐫𝐟𝐨𝐫𝐦𝐚𝐧𝐜𝐞 - 1x 2.5 Gbps WAN/LAN port, 1x 2.5 Gbps LAN port and 3x 1 Gbps LAN ports offer high-speed data transmissions.³ Integrate with a multi-gig modem for gigplus internet.
- 𝐎𝐮𝐫 𝐂𝐲𝐛𝐞𝐫𝐬𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐂𝐨𝐦𝐦𝐢𝐭𝐦𝐞𝐧𝐭 - TP-Link is a signatory of the U.S. Cybersecurity and Infrastructure Security Agency’s (CISA) Secure-by-Design pledge. This device is designed, built, and maintained, with advanced security as a core requirement.
Check firewalls, VPNs, and RPC port ranges
Name resolution and service discovery require more than one port. The exact set depends on the Windows versions, roles, and policies in the deployment, but these are the protocol values identified for the common Windows path:
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 errors| Protocol or function | Port | Why it matters |
|---|---|---|
| DNS | UDP and TCP 53 | Resolves host names and Active Directory service records. |
| RPC Endpoint Mapper | TCP 135 | Helps a client discover which RPC service endpoint to use. |
| SMB | TCP 445 | Supports modern Windows file-share access and related operations. |
| NetBIOS name service | UDP 137 | Legacy name resolution where NetBIOS is enabled. |
| NetBIOS datagrams | UDP 138 | Legacy NetBIOS datagram traffic. |
| NetBIOS sessions | TCP 139 | Legacy session traffic for older SMB paths. |
| LDAP where required | UDP 389 | Used for DC Locator traffic in the documented scenario. |
| Dynamic RPC | TCP 49152–65535 | Modern Windows dynamic RPC ports after endpoint discovery. |
TCP 135 by itself is not enough. The client may discover an RPC endpoint successfully and then fail when the selected dynamic port is blocked. Depending on the operation, SMB, LDAP, DNS, and legacy NetBIOS ports must also cross the path. Modern Windows commonly uses dynamic RPC ports 49152–65535, but the effective range depends on the operating-system generation and local policy.
Test the complete path
Review both endpoint firewalls and every intermediate control: the workstation firewall, server firewall, VPN tunnel policy, site-to-site ACL, and any segmentation rule between client and controller. A VPN may carry DNS while excluding dynamic RPC or SMB. An ACL may permit a controller’s address but not the subnet that contains its dynamic endpoints. Permit only the protocols and ranges required by the organization’s deployment; do not open every port as a trial fix.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Repair missing or corrupted service files
If Event Viewer identifies a missing executable or DLL, verify the file path in the service configuration and check whether the file was quarantined, deleted, or replaced. Microsoft lists system-file scanning, restoring a missing DLL from a trusted backup, and repairing or reinstalling the operating system as possible remedies.
Run the organization’s approved system-file scan from an elevated command prompt and record its result. If it reports corruption that it cannot repair, use a known-good backup or the supported Windows repair process rather than downloading a DLL from an untrusted site. After restoring a file, confirm its permissions and service path, reboot only when the repair procedure requires it, and then recheck the System log for Event IDs 7001 or 7003.
A successful file scan does not prove that the network path is fixed. If Net Logon starts normally but the same operation still fails, return to DNS records, controller discovery, and firewall or VPN testing.
Best Value
- Dual band router upgrades to 1200 Mbps high speed internet (300mbps for 2.4GHz plus 900Mbps for 5GHz), reducing buffering and ideal for 4K stream
- Full Gigabit Ports - Gigabit Router with 4 Gigabit LAN ports, ideal for any internet plan and allow you to directly connect your wired devices
- Boosted Coverage - Four external antennas equipped with Beamforming technology extend and concentrate the Wi-Fi signals
- MU-MIMO technology - (5GHz band) allows high speeds for multiple devices simultaneously
- Access Point Mode - Supports AP Mode to transform your wired connection into wireless network, an ideal wireless router for home
Windows and Samba or mixed-network environments
In a Samba environment, DNS becomes essential when NetBIOS over TCP/IP is disabled. Samba’s integration guidance recommends checking the resolver configuration rather than assuming that a Windows-style Services console exists.
Check resolver order on the Samba host
- Inspect
/etc/resolv.confand confirm that it lists the intended DNS servers for the domain. - Inspect
/etc/hostsfor a local override that maps a domain controller or server name to an obsolete address. - Inspect
/etc/nsswitch.confand confirm that the resolver order includes the intended sequence, such ashosts: files dns. - Resolve the Active Directory SRV records from the Samba host and verify that the returned controller is reachable.
A correct entry in /etc/hosts can help with one host name, but it does not replace the SRV records used to locate domain services. If SRV queries fail, fix the DNS service or resolver path instead of adding a collection of manual host entries.
Check WINS settings when the design still uses NetBIOS
On a WINS server, verify wins support = Yes in the Samba configuration. On a Samba client that uses an existing WINS server, verify wins support = No and wins server = <address>. Confirm UDP 137 reachability between the client and WINS server. These settings are relevant only when WINS is part of the network design; they do not repair a modern DNS-only Active Directory deployment.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Compare the Windows and Samba failure surfaces
| Environment | Primary checks | Typical evidence |
|---|---|---|
| Windows client or domain controller | DNS assignment and records, Net Logon and Workstation services, dependency events, RPC/SMB/LDAP firewall rules. | System Event IDs 7001 or 7003, Netlogon.log messages, failed controller or share discovery. |
| Samba host | /etc/resolv.conf, /etc/hosts, /etc/nsswitch.conf, SRV resolution, and smb.conf WINS settings. |
Resolver output that lacks the expected SRV records or WINS traffic that cannot reach UDP 137. |
Use the symptom to choose the next branch
Only one hostname or share fails
Compare that name with a working server. An incorrect A record, stale hosts-file entry, or a server-specific firewall rule is more likely than a domain-wide Net Logon outage. Test the name from the affected client and from another client on the same subnet before changing domain-wide settings.
Domain logon and controller discovery fail
Prioritize the client’s DNS server assignment, Active Directory SRV records, Net Logon state, and the complete RPC and LDAP path. If multiple clients fail at once, inspect the DNS service and domain controller logs before editing individual workstations.
Names resolve but remote administration or shares fail
This pattern points toward reachability after resolution. Check TCP 135, the dynamic RPC range, SMB TCP 445, and any VPN or ACL rule between the two systems. A successful DNS response does not authorize the subsequent service connection.
Only legacy names fail
If fully qualified DNS names work but short NetBIOS names do not, determine whether the environment still requires WINS or NetBIOS. Check UDP 137, the WINS client settings, and whether NetBIOS over TCP/IP was intentionally disabled. Do not re-enable legacy protocols solely to hide a missing DNS record in a modern domain.
Final verification checklist
- The affected hostname resolves to the expected address from the affected client.
- Domain-controller locator queries return a controller that the client can reach.
- Net Logon, Workstation, and the required RPC services remain running after a refresh.
- DNS, RPC Endpoint Mapper, dynamic RPC, SMB, LDAP where required, and any legacy NetBIOS ports pass through the organization’s firewall and VPN path.
- The original operation—domain logon, share access, printer discovery, or RPC administration—succeeds.
- No new dependency errors appear in the System log, and Netlogon.log no longer reports a paused service or an unresolved readiness condition.
If the error returns, preserve the exact time, affected client and target, DNS responses, service state, event IDs, firewall or VPN test results, and relevant Netlogon or Samba resolver output. That evidence distinguishes a local dependency failure from a domain-wide DNS or routing problem and prevents repeated, blind restarts.
Quick Recap
As an optional shortcut after the manual checks, Outbyte PC Repair can address more than 100 common Windows issues where possible, including broken system elements and shared DLL problems, while offering settings adjustments, temporary-file cleanup, vulnerability checks, and an app-crash log. It runs on Windows 11, 10, 8, and 7 and has a free trial of at least two days before a subscription; it complements antivirus software, results vary, and no tool repairs every crash.
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.
