Troubleshooting ScreenTask: Fixing Connection Refused, Port Conflicts & IP Errors

If you launch ScreenTask, click “Start Server”, and discover that client devices cannot load the stream in their browser—or you receive a “Connection Refused” or “This site can’t be reached” error—do not panic.

Because ScreenTask runs a direct, local HTTP web server on your Windows machine, 99% of connection issues stem from one of four common network configuration traps: selecting a virtual adapter IP, port collision with another app, router AP client isolation, or Windows Firewall dropping inbound packets.

This diagnostic checklist will help you identify the root cause and restore offline screen sharing in minutes.

---

The Quick 10-Second Test: Does Localhost Work?

Before troubleshooting client devices, test whether ScreenTask’s embedded HTTP server is actually running on your host computer:

1. Open your browser on the same computer hosting ScreenTask (Chrome, Edge, Firefox).
2. Navigate to:

   http://127.0.0.1:7070

   (Or replace 7070 with whichever port you configured in ScreenTask).

What the Localhost Test Tells You:

• If the screen loads on localhost: ScreenTask is functioning perfectly. The problem lies entirely in your local network routing, Windows Firewall, or router Wi-Fi isolation (proceed to Issue 1, 3, and 4).
• If localhost fails to load: ScreenTask was unable to bind to the port, or the server was stopped (proceed to Issue 2).

---

Issue 1: Wrong IP Interface Selected (Virtual Adapter Trap)

ScreenTask provides a dropdown of all network interfaces detected on your machine. If you have installed VirtualBox, VMware, Docker Desktop, WSL (Windows Subsystem for Linux), or a VPN client (NordVPN, ProtonVPN, OpenVPN), Windows creates virtual network adapters with their own IP subnets.

If ScreenTask accidentally binds to a virtual adapter, external phones and laptops will not be able to reach that IP address.

How to Fix:

1. Open Command Prompt (cmd) and type:

   ipconfig

2. Locate your active physical connection:
   • For Wi-Fi: Look under Wireless LAN adapter Wi-Fi for IPv4 Address (e.g., 192.168.1.45 or 10.0.0.22).
   • For Ethernet: Look under Ethernet adapter Ethernet.
3. Stop ScreenTask if it is running.
4. In ScreenTask’s IP dropdown, explicitly select the IP address matching your physical Wi-Fi or Ethernet adapter from Step 2.
5. Click Start Server and verify using that exact IP on client devices.

❌ Common Mistake: Selecting 192.168.56.1 (VirtualBox Host-Only Adapter)
❌ Common Mistake: Selecting 172.28.0.1 (WSL vEthernet Adapter)
✅ Correct Choice:  192.168.1.45 (Physical Home/Office Wi-Fi Router)

---

Issue 2: Port Conflict (“Address Already in Use” or Server Fails to Start)

ScreenTask defaults to port 7070 or 9000. If another program on your PC (such as a torrent client, a local web development server, or a background service) is already listening on that port, ScreenTask will fail to bind.

How to Fix:

1. In ScreenTask, change the Port field to an unused high port number, such as:
   • 8088
   • 9090
   • 9999
2. Click Start Server.
3. On client browsers, remember to update the URL with the new port:

   http://192.168.1.45:9090

To inspect which application is using port 7070 via PowerShell:

Get-NetTCPConnection -LocalPort 7070 -ErrorAction SilentlyContinue

---

Issue 3: Router AP Client Isolation (Guest Wi-Fi)

Many modern Wi-Fi routers and guest networks feature AP Isolation (also called Client Isolation or Station Isolation). When enabled, wireless devices can connect to the internet, but the router deliberately blocks devices from communicating with each other on the local network.

Signs of AP Client Isolation:

• Both PC and smartphone are connected to the same Wi-Fi SSID.
• The phone can browse Google, but cannot ping or open http://<PC-IP>:7070.

How to Fix:

1. Move off the Guest Network: Ensure both the host PC and viewing devices are connected to your primary home or office Wi-Fi network, not the “Guest” network.
2. Disable AP Isolation in Router Settings: Log in to your router gateway (192.168.1.1 or 192.168.0.1), navigate to Wireless Settings $\rightarrow$ Advanced, and toggle AP Isolation to Disabled.
3. Alternative (Zero-Router): If you cannot modify router settings (e.g. at a hotel, school, or cafe), turn on Windows Mobile Hotspot and connect your devices directly to your PC’s hotspot.

---

Issue 4: Windows Defender Firewall Dropping Incoming Traffic

Windows Firewall is designed to block unprompted incoming requests. If ScreenTask wasn’t granted permission upon first launch, incoming requests from other devices will silently time out.

How to Fix:

Open PowerShell as Administrator and execute:

# Open inbound rule for ScreenTask on port 7070
New-NetFirewallRule -DisplayName "ScreenTask Troubleshooting Rule" -Direction Inbound -LocalPort 7070 -Protocol TCP -Action Allow -Profile Any

Also ensure that your Windows network connection is set to Private, not Public:

• Windows 11: Settings $\rightarrow$ Network & internet $\rightarrow$ Wi-Fi $\rightarrow$ Your Network $\rightarrow$ Select Private network.
• Windows 10: Settings $\rightarrow$ Network & Internet $\rightarrow$ Status $\rightarrow$ Properties $\rightarrow$ Select Private.

---

Diagnostic Summary Matrix

Symptom	Probable Cause	Actionable Solution
127.0.0.1:7070 fails on host	Port in use or app error	Change port to 9090 in ScreenTask
Host works, client shows Timeout	Windows Firewall or Public Profile	Change profile to Private & add inbound firewall rule
Host works, client shows No Route	Wrong IP interface in dropdown	Select physical Wi-Fi IP from ipconfig, not VirtualBox/VPN
Connected to Guest Wi-Fi, cannot load	Router AP Client Isolation	Move to primary Wi-Fi or switch to Mobile Hotspot

---

Related Guides & Resources

• Windows 11 Setup, SmartScreen & Firewall Guide
• Windows 10 Offline Setup & Firewall Configuration
• How to Share PC Screen Over Wi-Fi Without Internet
• Download Latest ScreenTask Release