App Not Connecting
Work applications like Teams, Slack, Outlook, or Zoom fail to connect
⚠ Common symptoms
- "Unable to reach servers" or "Connection failed" error in the app
- App works on your phone's data but not the office Wi-Fi
- App worked yesterday, nothing changed, now it won't connect
- The app connects partially — messages load but calls fail, or vice versa
-
1
Check if the service itself is down
Before troubleshooting your setup, check the vendor's status page: status.slack.com, status.microsoft365.com, or status.zoom.us. If they're reporting an incident, wait for them to resolve it — no amount of local troubleshooting will fix a server-side outage.
-
2
Test connectivity to the app's servers
Open Command Prompt and ping the app's primary domain:
# Test if you can reach Slack servers
ping slack.com
# Test latency to Microsoft 365
ping outlook.office365.comIf these time out, the issue is between your network and the internet — not the app itself.
-
3
Clear the app's local cache
Most apps store cached data that can become corrupted. For Teams: close the app, navigate to
%AppData%\Microsoft\Teamsin File Explorer, and delete the Cache and blob_storage folders. For Slack: Help menu → Troubleshooting → Clear Cache. Restart the app. -
4
Check if a firewall or proxy is blocking the app
On office networks, a corporate firewall or web proxy may block the specific ports an app needs. Try using the app via your phone's hotspot — if it connects instantly, the office network is the blocker. Ask your IT team to whitelist the app's required ports and domains (each vendor publishes these in their network requirements documentation).
-
5
Reinstall or update the app
Uninstall the app completely, download the latest version from the official website (not the app store — you'll get the most current build), and reinstall. Also ensure your OS is up to date, as some app updates require recent system libraries.
Quick check: If the app connects fine on your phone's hotspot but not on office Wi-Fi, you've already isolated the problem to the network — skip straight to step 4 and involve IT.