Confirm the network locally
Several wireless networks in a hotel or café may have similar names. Ask for the intended name and the normal sign-in method. A stronger signal does not make an unfamiliar network the correct one. Do not enter an important account's credentials into an unexpected page simply because it appeared after connecting.
A guest service may use a portal that requires confirmation before allowing internet access. Read what it asks for. Installing unfamiliar software or a certificate is different from entering a simple access code. Clarify an unusual instruction with the operator instead of accepting it as a standard requirement.
Treat the environment as shared
Use the public network context and do not make local file shares unnecessarily available. The connection is for reaching internet services, not automatically for sharing personal folders with other guests. Maintain the operating system and browser before travelling so that urgent large updates are not an improvised task immediately after checking in.
Take certificate warnings on encrypted websites seriously. Do not bypass them on the assumption that the Wi-Fi is merely slow. A VPN can be part of an intended connection arrangement, but it does not make a fraudulent login page trustworthy. Follow your organisation's requirements for work access.
Plan around inconsistent reception
Download important documents beforehand and check that they open offline. A local booking confirmation is more useful than a link first opened when reception disappears. With larger work files, deliberately finish transfers and check what is stored locally before moving to another location.
If the network cannot support a task, a previously tested personal hotspot may offer an alternative, subject to its allowance and reception. Slow guest Wi-Fi is not a reason to send confidential documents through an arbitrary file-transfer service that happens to load.
After the trip, remove saved networks that are no longer needed or disable their automatic reconnection. That prevents an unnoticed return to a similarly named service later. Also check that paused synchronisation resumes at home. Files deliberately held back while travelling should not remain indefinitely on a single device.
