Separate discovery from downloading
First describe where the process stopped. Does the local address fail to open? Does the page open but joining fail? Or does joining succeed and a file transfer stop later? These are different stages, and repeating a large download will not fix an address that the computer cannot reach.
Open DeskShuttle and read the current address from the phone. Type it exactly, including the port when shown. Do not reuse an old bookmark after changing networks: the local address may change. Leave the app visible while you test.
A shared network name is only the first check
Connect the phone and computer to the same trusted network. Guest Wi-Fi and some managed networks isolate clients deliberately. The two devices can both reach the internet while being unable to reach one another. If this is a workplace or school network, ask its administrator about the intended local-device policy.
Check the iPhone’s Local Network permission for DeskShuttle in Settings. Apple provides controls for which apps can find and communicate with local devices. If permission was declined, revisit that setting and reopen the app before trying again. See Apple’s Local Network privacy guidance for the system’s current wording.
Look for a route that changed
A VPN or network security product can change the route between devices. Review its local-network settings or ask your administrator; do not blindly switch off protections to make a download work. If the connection environment is unsuitable, use another approved transfer route.
Once the page opens, follow the join code and approval flow on the phone. A page loading successfully does not prove that a transfer session has been approved. If an earlier session is no longer valid, return to the app’s current connection flow instead of endlessly retrying a stale browser tab.
Reduce the next experiment
After connecting, use one small file. Keep the phone awake with DeskShuttle open and leave both devices on the same network. If a small file succeeds but a large batch fails, record the browser, approximate file size and stage of failure. This is much more useful for support than “Wi-Fi is broken.”
Our Connection Check turns these questions into a short next-step list. It reads your selected answers only. It does not scan the network, discover devices or diagnose your router remotely. If the checklist does not resolve the issue, share the stage and symptoms with support without sending private files or access codes.