Network troubleshooting technician providing live chat help

Joe B.

Reviewed for technical accuracy

Specialities: Windows Remote Desktop, VPN access, Wi-Fi and LAN troubleshooting, firewalls & ports, office / work-from-home setup

Fix Remote Desktop not connecting over Wi-Fi — RDP works on Ethernet, “can’t connect to remote PC”, Wi-Fi disconnects

Technician avatar Technician
Hi! We’ll get your Remote Desktop not connecting over Wi-Fi issue fixed so you can reach your remote PC again. I just need a quick picture of the setup so we pick the right path. Are you trying to use Windows Remote Desktop (mstsc) from a laptop on Wi-Fi to another computer on the same network, or to a work PC over the internet/VPN? Does Remote Desktop connect when you plug in Ethernet or use a mobile hotspot, and only fail on Wi-Fi? Also, what exact error do you see — “Remote Desktop can’t connect to the remote computer”, stuck on “Configuring remote session…”, or it disconnects after a few seconds?
Customer
It’s my work PC I’m trying to reach from home with Remote Desktop Connection. I’m on a Windows 11 laptop over home Wi-Fi. When I run mstsc and type the computer name my company gave me, I get “Remote Desktop can’t connect to the remote computer”. If I plug the same laptop directly into the router with an Ethernet cable, it works. Also, if I use my phone’s hotspot it usually works. It’s just Remote Desktop over Wi-Fi that refuses to connect.
Technician avatar Technician
That’s really helpful — if Remote Desktop works on Ethernet but not Wi-Fi, the remote PC and your work network are probably fine, and the problem is on the Wi-Fi side or in how Windows treats that network.

Typical causes when Remote Desktop is not working over Wi-Fi:

• The Wi-Fi network is set as Public, so Windows blocks Remote Desktop traffic and some VPN connections.
• A security suite or Windows Defender Firewall has different rules for Wi-Fi versus wired and is blocking TCP 3389.
• Your router uses AP isolation / client isolation or strict QoS rules that interfere with RDP packets over wireless.
• When you’re remote, a VPN is required for RDP but isn’t connecting properly over Wi-Fi, even though it works on Ethernet.

We’ll start by confirming Windows sees that Wi-Fi as a trusted Private network, then check that Remote Desktop is allowed through the firewall on Wi-Fi, and finally we’ll look at VPN and router settings if needed.
Customer
On Ethernet, I just connect the VPN app from my company and then Remote Desktop works fine. On Wi-Fi, the VPN still connects but RDP fails with the same error every time. Web browsing over Wi-Fi is totally fine, speed tests look good. I just checked and Windows shows the Wi-Fi as “Public network”. Could that really stop Remote Desktop over Wi-Fi?
Technician avatar Technician
Yes, that “Public network” status is a big clue. On Public networks Windows tightens firewall rules, and some VPN profiles behave differently, which can block Remote Desktop traffic.

Step A — Make Wi-Fi a Private, trusted network
1) On your Wi-Fi laptop, open Settings > Network & Internet > Wi-Fi, then click your connected Wi-Fi network.
2) Under Network profile type, change it from Public to Private (Home/Work).
3) Open Windows Defender Firewall > Allow an app through firewall and confirm that Remote Desktop (and your VPN app) are checked for Private networks.
4) Disconnect from the VPN, reconnect it, then try your Remote Desktop Connection again by computer name and by IP address if your company provides one.

If Remote Desktop over Wi-Fi still isn’t working after that, we’ll run a quick test with ping and check whether anything on the router (like AP isolation) is blocking the wireless traffic differently from Ethernet.
Customer
I switched the Wi-Fi profile to Private and made sure Remote Desktop and the VPN are allowed on Private networks in the firewall. After reconnecting the VPN, I tried RDP again and still got “can’t connect to the remote computer”. If I unplug Wi-Fi and use Ethernet, it connects in a couple of seconds. I tried pinging the remote PC name on Wi-Fi and it resolves, but the ping times out. On Ethernet it replies.
Technician avatar Technician
That’s classic “Wi-Fi path blocked, wired path OK” behaviour. The VPN tunnel is up, but traffic to your work subnet is being filtered when it originates from Wi-Fi.

A few things to check that often fix Remote Desktop not working on Wi-Fi:

• Log into your router and turn off any AP/client isolation or “Wi-Fi isolation / guest Wi-Fi” features on the network you’re using.
• If your router separates 2.4 GHz and 5 GHz networks, test both. Some older routers handle VPN and RDP packets poorly on 2.4 GHz.
• On the laptop, temporarily disable any third-party security suite or “web shield” that could be inspecting VPN traffic over Wi-Fi.
• In Remote Desktop, try connecting by the remote PC’s IP address instead of name, in case DNS over the VPN behaves differently on Wi-Fi.

After you’ve disabled Wi-Fi isolation and confirmed you’re on the main SSID (not guest Wi-Fi), try RDP again. If it still fails only on Wi-Fi, we’ll collect the exact error details from the Remote Desktop client logs and look at MTU/packet size issues, which can also cause RDP to fail on wireless while browsing works.
Customer
I realized I was actually on the router’s “Guest Wi-Fi” SSID. It says clients are isolated. I switched to the main Wi-Fi network and now pinging the remote PC over VPN works. Remote Desktop gets a bit further but now I get a black screen for 10–15 seconds and then “Your Remote Desktop session has ended” or sometimes it just drops back to the login window over Wi-Fi. Ethernet sessions are still stable.
Technician avatar Technician
Great catch on the guest Wi-Fi — that alone explains why Remote Desktop wasn’t connecting over Wi-Fi at first. Now we’re dealing with unstable RDP sessions on Wi-Fi, which is usually a combination of wireless quality, power-saving settings, and MTU.

Step B — Stabilize Remote Desktop on Wi-Fi
1) On the laptop, go to Device Manager > Network adapters, open your Wi-Fi adapter, and under Power Management uncheck “Allow the computer to turn off this device to save power”.
2) In Advanced tab, enable options like “Throughput Booster” or “Maximum Performance” if available, then update the Wi-Fi driver from the laptop or adapter manufacturer’s site.
3) In the Remote Desktop client, click Show Options > Experience and set the connection speed to Detect connection quality automatically, unchecking heavy features like font smoothing or persistent bitmap caching to reduce bandwidth.
4) If your VPN app has an MTU/packet size setting, try lowering it slightly (for example 1400 instead of 1500) and reconnect. Fragmented VPN packets can make RDP look like it’s randomly disconnecting over Wi-Fi.

After these changes, restart the laptop, connect Wi-Fi, then VPN, then try Remote Desktop again. Tell me if the black screen and drops still happen, or if it now stays connected for longer sessions.
Customer
I updated the Wi-Fi driver, disabled power saving on the adapter, and turned off the fancy visual features in the Remote Desktop client. I also lowered the MTU in the VPN settings like you suggested. Now the session actually connects and stays open. I tested about 20 minutes on Wi-Fi without a disconnect. The only weird thing is that sometimes it takes a long time to connect by computer name, but if I use the IP address it’s quick.
Technician avatar Technician
Nice — that means the core Remote Desktop not working on Wi-Fi issue is resolved, and now we’re just improving speed and reliability.

The delay when using the computer name is usually DNS resolution over VPN being slow or flaky on Wi-Fi:

• On the laptop, open a Command Prompt after connecting VPN and run nslookup YOURWORKPCNAME to see which DNS server answers and how long it takes.
• If your IT allows it, you can add a line to the local hosts file mapping the work PC name to its IP, so name lookups resolve instantly even over Wi-Fi.
• In the Remote Desktop Connection window, hit Show Options, enter the remote computer and username, and click Save As to create an .rdp file that you can reuse, with the best settings already applied for your Wi-Fi connection.

For most people, simply using the IP address in the RDP client is enough — especially if the IP is static or reserved. The important part is that your Remote Desktop sessions over Wi-Fi are now stable and usable.
Customer
Using the IP in the RDP file works great, it connects almost instantly on Wi-Fi now. I’ll ask IT later about the hosts file. One more question: sometimes I also use Remote Desktop from my home desktop PC to another computer in the house, and occasionally that fails over Wi-Fi too. Are there any general settings I should change on the remote PCs themselves so Remote Desktop on Wi-Fi is less picky?
Technician avatar Technician
Good question — yes, there are a few things you can standardize on each remote PC to avoid future “Remote Desktop can’t connect” messages, especially when connecting over Wi-Fi.

Step C — Hardening the remote PC for Wi-Fi RDP
• On the remote PC, go to Settings > System > Remote Desktop and make sure Remote Desktop is turned on and set to allow connections only from PCs with Network Level Authentication (NLA) where possible.
• Click Advanced settings and confirm it’s listening on the default RDP port 3389 unless your IT has assigned a custom port.
• Ensure the remote machine’s power plan doesn’t put the PC to sleep or turn off the network adapter while you’re away — sleep will kill RDP availability even if Wi-Fi is fine.
• Open Windows Defender Firewall and verify that “Remote Desktop” is allowed on Private networks so home Wi-Fi clients can connect.
• Add your main user account to the Remote Desktop Users group so you don’t run into “You must be granted the Allow log on through Remote Desktop Services right” errors.

Once those are set on remote machines and your router isn’t using guest or isolated Wi-Fi networks, Remote Desktop over Wi-Fi on your home LAN should behave very similarly to Ethernet.
Customer
I checked my home desktop and turned on Remote Desktop with NLA, added my user to Remote Desktop Users, and set the power plan so it doesn’t sleep. I also confirmed the firewall rule is enabled on Private networks. Testing from my laptop over Wi-Fi works first try now. So both my work connection over VPN and my home PC over Wi-Fi are working with Remote Desktop.
Technician avatar Technician
Awesome — that’s exactly what we wanted.

Summary: When Remote Desktop is not connecting over Wi-Fi but works on Ethernet or a hotspot, the usual fix is to switch Wi-Fi to a Private network, allow Remote Desktop and VPN apps through the firewall on Private networks, avoid guest/isolated Wi-Fi SSIDs, update Wi-Fi drivers and disable aggressive power-saving, then tune RDP and VPN settings (MTU, visuals) for wireless. Finally, make sure the remote PC is configured for Remote Desktop, stays awake, and has proper firewall rules.

If this ever breaks again — sessions dropping, RDP not working over Wi-Fi after an update, or new error messages — you can open a chat with an expert and we’ll walk through your Wi-Fi, VPN, firewall, and Remote Desktop settings live.
Customer
Thank you, this was super helpful. Remote Desktop over Wi-Fi is finally reliable again and I know what to check next time if it stops working.
Technician avatar Technician
You’re very welcome! If a coworker ever says their Remote Desktop won’t connect over Wi-Fi, or RDP only works when they plug in a cable, you can share this checklist — and if you’d like someone to click through the settings with you in real time, just start a chat with an expert and we’ll take it from there.

Quick answer: the accepted fix

Accepted fix when Remote Desktop is not connecting over Wi-Fi: set your Wi-Fi network to Private, allow Remote Desktop and VPN through the firewall on Private networks, avoid guest/isolated Wi-Fi, update Wi-Fi drivers, and tune RDP/VPN settings (MTU & visuals). On the remote PC, keep Remote Desktop enabled, ensure it stays awake, and verify firewall rules so Wi-Fi clients can connect.

Why Remote Desktop stops connecting over Wi-Fi (firewall, VPN, router, Wi-Fi profile)

Most Remote Desktop not working over Wi-Fi problems are not caused by the remote PC itself. Instead, Windows treats the wireless network as Public, a VPN behaves differently on Wi-Fi, or the router is using guest Wi-Fi / AP isolation that blocks RDP traffic. Firewalls that allow TCP 3389 on Ethernet but not on Wi-Fi, or aggressive Wi-Fi power-saving settings, can also make RDP sessions disconnect or fail to start even though browsing and streaming work fine.

Thinking of the path as Wi-Fi device → router → VPN (if used) → remote network → remote PC lets you see where “Remote Desktop can’t connect to the remote computer” appears. If RDP works on Ethernet but not Wi-Fi, focus on Wi-Fi profile type, firewall rules, VPN, and router wireless settings. If Remote Desktop fails on every connection type, then it’s time to check the remote PC’s own Remote Desktop settings, user permissions, and firewall.

How to check whether the problem is Wi-Fi, Remote Desktop, or the remote PC

To quickly narrow down a Remote Desktop not connecting over Wi-Fi issue, start with simple tests:

First, try the same Remote Desktop connection on Ethernet or via a mobile hotspot. If RDP works there but not on Wi-Fi, the remote PC and credentials are fine and Wi-Fi is the culprit. Next, confirm that the Wi-Fi network is marked as Private, not Public, and that both Remote Desktop and any VPN client you use are allowed through the firewall on Private networks. Use ping and tracert after your VPN connects to see whether the remote host’s IP is reachable on Wi-Fi. If Wi-Fi and VPN look good but RDP still fails, check the remote PC: make sure Remote Desktop is enabled, the PC is awake, you’re in the Remote Desktop Users group, and its firewall allows RDP from the networks you’re using.

Remote Desktop not connecting over Wi-Fi — quick troubleshooting tips

Confirm Wi-Fi and VPN first, then fix firewall, Remote Desktop, and router settings.

Fast path: change your Wi-Fi profile to Private → make sure you aren’t on guest or isolated Wi-Fi → reconnect your VPN (if required for work) → allow Remote Desktop and the VPN client through the firewall on Private networks → update Wi-Fi drivers and disable power-saving on the adapter → on the remote PC, enable Remote Desktop with NLA and confirm it can accept RDP on TCP 3389. Keeping drivers updated and avoiding guest Wi-Fi helps prevent random “Remote Desktop can’t connect” errors in the future.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your Remote Desktop setup, VPN, and firewall rules, please consult a verified expert on Whizz-Tech before making decisions.

Getting Started Is Easy

Ask for help, 24/7

Members enjoy round-the-clock access to 12,000+ verified Experts for Remote Desktop not connecting over Wi-Fi, RDP errors, VPN issues, and more.

Expert will respond in minutes

We match you with a Windows and networking specialist who knows Remote Desktop, VPN, firewalls, Wi-Fi routers, and common RDP errors like “can’t connect to the remote computer”.

Save time & money

Stop guessing at Wi-Fi and VPN settings or waiting on hold with corporate IT. Get a clear step-by-step Remote Desktop fix in chat and get back to work quickly.

FAQ

Why is Remote Desktop not connecting over Wi-Fi but works on Ethernet?

When Remote Desktop works on Ethernet but not Wi-Fi, the issue is usually how Windows and your router treat the wireless network. Common causes include the Wi-Fi profile set to Public instead of Private, guest Wi-Fi / AP isolation enabled on the router, different firewall rules for Wi-Fi versus wired, or VPN traffic that’s filtered on wireless. Switching Wi-Fi to Private, disabling guest/isolated Wi-Fi, and allowing Remote Desktop and VPN apps through the firewall on Private networks usually resolves it.

How do I fix “Remote Desktop can’t connect to the remote computer” on Wi-Fi?

If you see “Remote Desktop can’t connect to the remote computer” while on Wi-Fi, first confirm you have a working internet connection and that any required VPN is connected. Then make sure your Wi-Fi is marked Private, not Public, and allow Remote Desktop through the firewall for Private networks. Avoid guest Wi-Fi, update your Wi-Fi drivers, and test RDP using the remote PC’s IP address as well as its name. Finally, verify on the remote PC that Remote Desktop is enabled, the PC is awake, and that you have permission to connect.

Do I need to open port 3389 on my router for Remote Desktop over Wi-Fi?

If you are connecting to another PC inside the same home or office Wi-Fi network, you do not normally need to open port 3389 on your router — Remote Desktop traffic stays on the local LAN. You only need to configure port forwarding or a Remote Desktop gateway if you’re connecting from outside your network without a VPN, which has security implications. For most work-from-home setups, your company provides a VPN so that RDP runs through the tunnel and uses internal addresses instead of exposing RDP directly to the internet.

When should I reset my network settings to fix Remote Desktop over Wi-Fi?

If Remote Desktop still won’t connect over Wi-Fi after checking Wi-Fi profile type, firewall rules, router guest/isolated Wi-Fi, VPN configuration, and remote PC settings, then a network reset on the problem device can help. In Windows, you can reset the network stack (or use “Network reset” in Settings), which reinstalls adapters and clears old profiles that sometimes break RDP over Wi-Fi. Just make sure you have your Wi-Fi password and VPN details handy before resetting.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant
5 Tech Support Specialists are online right now.