When Windows Remote Desktop won’t connect, start at the remote PC rather than changing random network settings. The host must run a Windows edition that supports incoming Remote Desktop connections, Remote Desktop must be enabled, and the client must use the host’s current PC name and an expected account. Only after those checks should you investigate network reachability, firewall policy, or a recent Windows update.
This order separates an unsupported or misconfigured host from a connection that is being blocked on the path. It also avoids a common but unsafe shortcut: turning off firewall protection globally.
As an Amazon Associate I earn from qualifying purchases.
What must be true before Remote Desktop can work?
Remote Desktop has two different sides: the remote PC, which accepts the session, and the client, which initiates it. Microsoft’s setup guidance requires the remote PC to run Windows Pro edition. The connecting device can run any Windows edition or a different operating system.
| Check | Correct state | Where to verify it | What a failure means |
|---|---|---|---|
| Host edition | Windows Pro on the PC you want to control | Remote PC: Settings > System > About | An unsupported host cannot accept incoming Remote Desktop sessions through this feature. |
| Remote Desktop service | Remote Desktop is turned on | Remote PC: Settings > System > Remote Desktop | The client may be correct, but there is no enabled host endpoint to connect to. |
| PC name | The client uses the name currently shown by the remote PC | Remote PC: Settings > System > Remote Desktop | A stale, mistyped, or wrong computer name sends the request to the wrong destination. |
| Account | The client signs in with the expected account for that host | Remote Desktop sign-in prompt | A reachable host can still reject the session when the supplied account is not the one intended for access. |
| Network path | The client can reach the remote PC on the relevant local or organizational network | Client network status and the organization’s access path | A working Wi-Fi icon does not prove that this particular host is reachable. |
| Firewall and policy | Rules permit the needed Remote Desktop traffic | Windows Security > Firewall & network protection, plus any organization policy | Local firewall rules, network profile policy, or central management can block the session. |
These checks also explain why one symptom can have several causes. A disabled host and a blocked network path can look similar from the client, but they require different fixes.
#1 Best Overall
- 𝐇𝐢𝐠𝐡-𝐒𝐩𝐞𝐞𝐝 𝐔𝐒𝐁 𝐄𝐭𝐡𝐞𝐫𝐧𝐞𝐭 𝐀𝐝𝐚𝐩𝐭𝐞𝐫 - UE306 is a USB 3.0 Type-A to RJ45 Ethernet adapter that adds a reliable wired network port to your laptop, tablet, or Ultrabook. It delivers fast and stable 10/100/1000 Mbps wired connections to your computer or tablet via a router or network switch, making it ideal for file transfers, HD video streaming, online gaming, and video conferencing.
- 𝐔𝐒𝐁 𝟑.𝟎 𝐟𝐨𝐫 𝐅𝐚𝐬𝐭𝐞𝐫, 𝐌𝐨𝐫𝐞 𝐒𝐭𝐚𝐛𝐥𝐞 𝐃𝐚𝐭𝐚 𝐓𝐫𝐚𝐧𝐬𝐟𝐞𝐫𝐬- Powered via USB 3.0, this adapter provides high-speed Gigabit Ethernet without the need for external power(10/100/1000Mbps). Backward compatible with USB 2.0/1.1, it ensures reliable performance across a wide range of devices.
- 𝐒𝐮𝐩𝐩𝐨𝐫𝐭𝐬 𝐍𝐢𝐧𝐭𝐞𝐧𝐝𝐨 𝐒𝐰𝐢𝐭𝐜𝐡- Easily connect your Nintendo Switch to a wired network for faster downloads and a more stable online gaming experience compared to Wi-Fi.
- 𝐏𝐥𝐮𝐠 𝐚𝐧𝐝 𝐏𝐥𝐚𝐲- No driver required for Nintendo Switch, Windows 11/10/8.1/8, and Linux. Simply connect and enjoy instant wired internet access without complicated setup.
- 𝐁𝐫𝐨𝐚𝐝 𝐃𝐞𝐯𝐢𝐜𝐞 𝐂𝐨𝐦𝐩𝐚𝐭𝐢𝐛𝐢𝐥𝐢𝐭𝐲- Supports Nintendo Switch, PCs, laptops, Ultrabooks, tablets, and other USB-powered web devices; works with network equipment including modems, routers, and switches.
Use the first check that can actually disprove a theory. If the host edition is ineligible, stop there rather than editing firewall rules. If the host is eligible and enabled but the client has no route to it, focus on the network path. If only managed computers fail, policy is more likely than a setting on one user’s client.
How the symptoms point to different causes
| What you observe | Most useful first question | What to avoid |
|---|---|---|
| The connection has never worked to this PC | Is the host running Windows Pro, and is Remote Desktop enabled? | Assuming a firewall problem before checking host eligibility. |
| The connection worked until the PC name changed | Does the client use the name currently displayed on the host? | Continuing to reuse a saved shortcut without verifying its destination. |
| Other internet activity works, but this host does not | Is the host reachable on the local or organization-controlled path? | Using the Wi-Fi icon as proof that this computer is reachable. |
| Several users or managed devices fail | Has a central firewall, access rule, or Remote Desktop policy changed? | Changing one client repeatedly when the restriction is centrally enforced. |
| Failure began after a September 2026 update | Is the host Windows 11 24H2 or 25H2, and is the September 14 fix installed? | Treating a dated issue as a universal explanation. |
Fix Remote Desktop in the safest order
1. Confirm that the remote PC has an eligible Windows edition
On the computer you want to control, open Settings > System > About and look under Windows specifications for the edition. The host needs Windows Pro edition for incoming Remote Desktop connections according to Microsoft’s support guidance.
The edition that matters is the edition on the remote PC, not the edition on the device you are using to connect. The client can run any Windows edition or another operating system. This distinction is important when a home laptop is connecting to a work computer or when several machines have different editions.
If the remote PC is running an edition that does not provide the host feature, changing client settings, reinstalling the Remote Desktop app, or opening firewall ports will not make that PC eligible. Record the edition before continuing, especially when several similarly named computers are involved.
2. Turn on Remote Desktop and record the exact PC name
On the remote PC, open Settings > System > Remote Desktop. Turn on Remote Desktop and note the PC name displayed on that page. Use that exact name from the client.
Do not rely on an old note, a shortcut created for a previous computer name, or a name copied from another device. A computer may have been renamed, replaced, or confused with another system. Recording the name directly from the host removes that ambiguity.
If the setting is already on, do not change it repeatedly; move to confirming the client details and network path. Repeatedly toggling the setting does not correct a wrong destination or a blocked organizational route.
3. Check the client’s destination and account
Enter the recorded PC name in the Remote Desktop client and sign in with the account you expect to use on that host. Check spelling, punctuation, and the selected account before treating the failure as a firewall problem.
Rank #2
- Connects a USB 3.0 device (computer/laptop) to a router, modem, or network switch to deliver Gigabit Ethernet to your network connection. Does not support Smart TV or gaming consoles (e.g.Nintendo Switch).
- Supported features include Wake-on-LAN function, Green Ethernet & IEEE 802.3az-2010 (Energy Efficient Ethernet)
- Supports IPv4/IPv6 pack Checksum Offload Engine (COE) to reduce Cental Processing Unit (CPU) loading
- Compatible with Windows 8.1 or higher, Mac OS
Keep the destination and identity separate in your notes. A correct name with an unintended account can produce a sign-in failure, while an incorrect name can send the request to a different computer. Neither symptom proves that the host firewall is blocking traffic.
If more than one computer has a similar name, verify that the name came from the intended remote PC’s Remote Desktop page. A successful connection to a different machine is still a wrong-destination problem, not evidence that the original host is functioning.
4. Separate a general network problem from a host-specific problem
First ask whether the client has a broader connectivity problem. Microsoft’s Wi-Fi guidance notes that a device can show as connected while a particular app or firewall remains unable to communicate. Therefore, a connected Wi-Fi indicator is not a sufficient Remote Desktop test.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Check whether other ordinary network activity from the client works.
- Determine whether the client and host are on the same local network or whether the connection depends on an organization’s remote-access path.
- If you suspect Wi-Fi specifically, a wired Ethernet connection can be used as an optional comparison. It is an isolation step, not a general Remote Desktop fix and not a required purchase.
- If only this host fails while the client’s broader connectivity is normal, focus on the host name, host availability, firewall rules, and organizational policy rather than resetting the entire client network immediately.
- If several hosts fail from one client, consider a client-side network or access-path issue. If one host fails for several clients, consider that host’s configuration or a shared policy.
Do not assume that a client connected to the internet can automatically reach a particular PC. Local-network segmentation, a company access path, and host-side policy can all produce a Remote Desktop failure even when general browsing works.
When comparing wired and Wi-Fi behavior, change only that one variable and keep the host name and account the same. If both paths fail identically, buying a cable or changing hardware is not established as the solution; continue with host, firewall, policy, or update checks.
5. Review firewall rules without disabling protection
Open Windows Security > Firewall & network protection and review the active network profile and the rules affecting Remote Desktop. If Windows Firewall is blocking the application, use the option to allow an app through the firewall and permit only the required access.
Microsoft states that adding an app to the allowed list is generally safer than opening a port. It also warns that opening a port can make the device less secure. Avoid creating a broad, permanent port exception merely to see whether the connection works.
PC 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 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchUse the narrowest change that addresses the observed block. Note the original setting, apply the permitted app rule if appropriate, and test again. Remove exceptions or rules that are no longer needed instead of allowing temporary troubleshooting changes to become permanent exposure.
Rank #3
- [Expansion Ports] The USB C to Ethernet Adapter expands the device to three USB 3.0 ports and one Gigabit Ethernet port. Provides you more peripheral ports while maintaining a stable network connection, plug and play, no driver required.
- [Gigabit Network Port] ALL-LUCKY USB Ethernet Adapter transmission rate up to 1000Mbps, also compatible with 10/100Mbps bandwidth. It allows you to enjoy a smooth and stable network connection and avoid too much lag. (Note: To reach 1Gbps, please use CAT6 or above Ethernet cable connection)
- [Convertible Connector]This usb hub with ethernet not only has USB-A connector, but also can be converted to USB-C connector, so that you can easily convert the connector according to the device port, improve the convenience of use.
- [High-Speed Data Transfer] The usb to ethernet adapter adopts USB 3.0 transmission technology, supports up to 5Gbps transmission rate, and is compatible with USB 2.0(480Gbps),USB 1.0(12Mbps), easily transfer video, files and other data for you in seconds. (Note: Maximum output current is 900mA, does not support charging devices.)
- [Widely Compatible]The usb c ethernet adapter for iMac, MacBook Pro, iPad Pro, XPS and many other devices. Compatible with Windows 11/10/8.1/8, Mac OS, iPad OS, Chrome OS.（Note: Driver is required on Win 7） It can be used in office, school, library and other occasions, compact and portable, easy to carry around.
Do not turn off Windows Firewall as a routine diagnostic. Microsoft warns that doing so can make the device more vulnerable to unauthorized access. If a narrowly scoped rule does not resolve the problem, restore the original protection and continue checking the network path or policy instead of leaving the firewall disabled.
On a work-managed computer, the controls may be locked or automatically restored by policy. In that case, the administrator needs to confirm whether Remote Desktop is permitted, which network profile is expected, and whether a central firewall or access rule is blocking the session. Do not try to bypass a management control by repeatedly changing local settings.
6. Check Windows version, update history, and the timing of the failure
If the connection worked previously and failed after an update, record the Windows version and inspect Settings > Windows Update > Update history on the affected host. Write down when the failure began, which update was installed, and whether the symptom is a failed connection, a failed sign-in, or an unresponsive server during Remote Desktop configuration.
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 errorsThis is particularly important for a dated Microsoft issue involving some organizations running Windows 11 versions 24H2 and 25H2.
Microsoft’s September 8, 2026 release note described Remote Desktop Services instability after the September 2026 security update. In affected environments, symptoms could include failed RDP connections or sign-ins and servers becoming unresponsive while Remote Desktop was being configured. Microsoft’s September 14, 2026 out-of-band update says the issue was fixed, and Microsoft’s release information says the issue was resolved in updates released on and after September 14.
That report applies to some environments, not every Windows 11 computer. Compare the host’s version, update history, symptom timing, and installed fixes with Microsoft’s release-health information. If the September issue matches, install the applicable resolution rather than making unrelated firewall changes. If the host is not on Windows 11 24H2 or 25H2, or the failure did not begin around that update, this specific incident is not a sufficient explanation.
Windows 10 support ended on October 14, 2025. Treat that date as lifecycle context when assessing an older host; it is not evidence that every Windows 10 Remote Desktop connection stopped working on that day.
7. Escalate server-side or managed-device failures
Contact the administrator when the device is managed, the firewall or Remote Desktop setting cannot be changed, the connection uses an organization-controlled access path, or multiple users cannot reach the same host. An administrator can check central policy, server-side Remote Desktop Services, network segmentation, and update deployment.
Rank #4
- The Anker Advantage: Join the 65 million+ powered by our leading technology.
- Instant Internet: Connect to the internet instantly from virtually any USB-C 3.0 device, and enjoy stable connection speeds of up to 1 Gbps.
- Lightweight and Compact: The space-saving and portable design measures just over half an inch thick and weighs about the same as a AA battery.
- Premium Build: Features a sleek aluminum exterior and braided-nylon cable to complement the design of high-end devices.
- What You Get: PowerExpand USB-C to Gigabit Ethernet Adapter, welcome guide, 18-month worry-free warranty, and friendly customer service.
Escalation is also appropriate when the host becomes unresponsive during Remote Desktop configuration, when the same failure appears after a centrally deployed update, or when local settings keep reverting. Those patterns are not solved reliably by changing one user’s client.
For a personal computer, escalation may mean checking the host locally rather than continuing from the client. A host that is powered off, asleep, disconnected, or no longer on the expected network cannot accept a session even when its saved PC name is correct.
Use Network reset only as a later general network measure
Microsoft describes Network reset as a last step for broader network problems, not as an early Remote Desktop fix. It removes and reinstalls network adapters and returns network settings to their defaults.
Recommended Free Tools
Use it only after the host, name, account, network path, firewall, and update checks above have narrowed the problem to the client’s general networking. It is not a substitute for enabling Remote Desktop on an ineligible host or obtaining permission through a managed access path.
Plan for side effects: VPN clients or virtual switches may need to be configured again afterward, and other custom network settings can be lost. Record those settings and ensure you can restore the organization’s connection method before proceeding. If only one host is unreachable, Network reset is especially unlikely to be the first appropriate action.
What not to do when Remote Desktop fails
- Do not keep retrying a client connection to an unqualified host edition.
- Do not substitute an old computer name for the name shown on the remote PC’s current Remote Desktop page.
- Do not treat a connected Wi-Fi status as proof that the host is reachable.
- Do not open a broad firewall port when an app-specific allow rule is sufficient.
- Do not leave Windows Firewall disabled after a test.
- Do not apply the September 2026 Windows 11 issue as a universal explanation without matching the version, environment, and timing.
- Do not perform Network reset before considering its adapter, VPN, virtual-switch, and settings consequences.
- Do not purchase networking hardware or repair utilities as a presumed fix; the available guidance does not establish a product purchase as the cause-specific solution.
Record these details before asking for help
Precise details make it possible to distinguish a setup error from a network or servicing problem. Record:
- The remote PC’s Windows edition and version.
- Whether Remote Desktop is enabled and the PC name displayed on its settings page.
- The account used by the client.
- Whether the client and host share a local network or rely on an organization’s access path.
- Whether general network activity works from the client.
- Whether the problem affects one host, one client, or multiple users.
- The active firewall or network profile and whether settings are controlled by policy.
- The exact date the failure began and whether it followed a Windows update.
- The full error text or sign-in symptom, without paraphrasing it.
- Whether the September 14, 2026 or later applicable update is installed when the host is Windows 11 24H2 or 25H2.
There is no reliable population-wide failure rate to use as a shortcut diagnosis. The useful evidence is specific to the host edition, configuration, network path, policy, Windows version, and update history in the affected environment.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Bottom line for a failed connection
Work from the remote PC outward: verify Windows Pro, enable Remote Desktop, copy the current PC name, and confirm the account. Then test whether the client can reach that host, review firewall rules without disabling protection, and check update history when the failure is recent. A managed device or a matching Windows 11 24H2/25H2 servicing issue belongs with the administrator or the relevant Microsoft fix, not with increasingly broad firewall changes.
Best Value
![BENFEI USB 3.0 to Ethernet Adapter, USB C to RJ45 Gigabit LAN (1000Mbps) Network Adapter, Compatible with MacBook/Pro/Air, Surface Pro, Windows 11/10/8/7, Mac OS [Aluminium Shell&Nylon Cable]](https://m.media-amazon.com/images/I/41fk9DHmdwL._SL160_.jpg)
- COMPACT DESIGN - The compact-designed portable BENFEI USB A/C to Ethernet adapter connects your computer or tablet to a router,modem or network switch for network connection. It adds a standard RJ45 port to your Ultrabook, notebook or Macbook Air for file transferring, video conferencing, gaming, and HD video streaming.
- SUPERIOR STABILITY - Built-in advanced IC chip works as the bridge between RJ45 Ethernet cable and your USB A/C devices. The driver-free installation with native driver support in Chrome, Mac, and Windows OS; The USB A/C Ethernet adapter dongle supports important performance features including Wake-on-Lan (WoL), Full-Duplex (FDX) and Half-Duplex (HDX) Ethernet, Crossover Detection, Backpressure Routing, Auto-Correction (Auto MDIX).
- INCREDIBLE PERFORMANCE - Supports full 10/100/1000Mbps gigabit ethernet performance over USB A/C's 5Gbps bus, faster and more reliable than most wireless connections. Link and Activity LEDs. USB powered, no external power required. Backward compatible with USB 2.0/1.1.✅ To reach 1Gbps, make sure to use CAT6 & up Ethernet cables.
- BROAD COMPATIBILITY - The USB A/C-Ethernet adapter is compatible with Windows 11/10/8.1/8/7/Vista/XP, Mac OSX 10.6/10.7/10.8/10.9/10.10/10.11/10.12, Linux kernel 3.x/2.6, Android and Chrome OS.Compatible with IEEE 802.3, IEEE 802.3u and IEEE 802.3ab. Supports IEEE 802.3az (Energy Efficient Ethernet).❌Do Not Support Windows RT. (NOT compatible with Nintendo Switch.)
- 18 MONTH WARRANTY - Exclusive BENFEI Unconditional 18-month Warranty ensures long-time satisfaction of your purchase; Friendly and easy-to-reach customer service to solve your problems timely.
Frequently Asked Questions
Why does Remote Desktop say it cannot connect even though Wi-Fi works?
A connected Wi-Fi indicator proves only that the client has a network connection. The host may still be unreachable on the local network or organization-controlled access path, or a firewall or policy may block this application. Check the host name, host availability, network path, and firewall rules separately.
Can I connect to a Windows Home PC with Remote Desktop?
Microsoft’s setup guidance requires the remote PC—the computer accepting the session—to run Windows Pro edition. The client can run any Windows edition or another operating system. Verify the host edition in Settings > System > About before changing network settings.
Where do I find the correct computer name?
On the remote PC, open Settings > System > Remote Desktop and record the PC name shown there. Enter that current name in the client rather than relying on an old shortcut or note.
Free tools Windows power users keep installed
One-click scans. No signup required.
Should I turn off Windows Firewall to test Remote Desktop?
No. Microsoft warns that turning off Windows Firewall can make the device more vulnerable to unauthorized access. If the firewall is blocking the app, use a narrowly scoped allowed-app rule, and ask an administrator when policy controls the setting.
What if Remote Desktop stopped working after a Windows update?
Check the host’s Windows version and Settings > Windows Update > Update history, then compare the timing and symptoms with Microsoft’s release-health information. A September 2026 issue affected some Windows 11 24H2 and 25H2 environments and was fixed in an out-of-band update released September 14, 2026 and subsequent updates.
Is Network reset a good first fix for Remote Desktop?
No. Microsoft describes Network reset as a last step for broader network problems. It removes and reinstalls network adapters and resets network settings; VPN clients, virtual switches, and other custom settings may need reconfiguration afterward.
When should I contact my IT administrator?
Contact the administrator when the device is managed, local firewall or Remote Desktop settings are locked, the connection depends on an organizational access path, multiple users fail to reach the same host, or the server becomes unresponsive during Remote Desktop configuration.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Is buying an Ethernet cable a Remote Desktop fix?
No product is established as a general fix. A wired connection can be an optional comparison if you suspect Wi-Fi, but it is only an isolation step. If both wired and Wi-Fi attempts fail, continue with host, account, network-path, firewall, policy, and update checks.
The Bottom Line
Verify the remote PC’s edition, Remote Desktop setting, current PC name, and account first. Then isolate network reachability, review firewall and policy safely, and check update history for version-specific issues. Avoid broad firewall changes and use Network reset only as a later, general network measure.
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.
