I keep a travel router in a drawer, but the last time my home router failed, the little box was across town in a backpack. The useful hardware was already on my desk: a Windows 11 laptop with working Wi-Fi and Ethernet. Ten minutes later, my phone, tablet, and television were online through it.
Windows can share a connection three ways, but the menus make them look more interchangeable than they are. Mobile Hotspot is the simple answer for almost everyone. Internet Connection Sharing handles awkward wired setups. A network bridge solves a narrower problem and can make an outage worse if you choose it casually. The goal is not to memorize three procedures. It is to recognize the job and pick the least complicated one that fits.
Start by naming the connection you have and the one you need
Before opening Settings, write the situation as two short phrases: “internet comes in through Ethernet” and “devices need Wi-Fi,” for example. That distinction prevents most wrong turns.
- Ethernet in, Wi-Fi out: use Mobile Hotspot. This is the common hotel, dorm, or dead-router scenario.
- Wi-Fi in, Wi-Fi out: try Mobile Hotspot first, but expect older wireless adapters to refuse simultaneous client and hotspot duty.
- Wi-Fi or Ethernet in, Ethernet out: use Internet Connection Sharing (ICS), especially for a console, printer, television, or desktop without Wi-Fi.
- Two network segments that must behave as one: consider a network bridge only if you understand why Network Address Translation would be a problem.
NAT (Network Address Translation, the mechanism that lets several devices share one upstream address) is helpful in an emergency because it separates your temporary network from the upstream one. Mobile Hotspot and ICS provide that separation. A bridge does not. It joins two adapters at the data-link layer, so devices on either side participate in the same network.
That difference matters more than whether a menu looks newer. If all you want is internet access, NAT is usually an advantage. If you are testing discovery protocols, capturing packets, or extending an existing wired segment, a bridge may be appropriate.
Mobile Hotspot is the two-minute recovery path
Open Settings > Network & internet > Mobile hotspot. Under “Share my internet connection from,” select the adapter that is online. Under “Share over,” choose Wi-Fi. Edit the network name and password, turn the switch on, then join from the other device.
Windows supplies DHCP (Dynamic Host Configuration Protocol, the service that assigns local addresses) and NAT automatically. You should not need to choose an address range, gateway, or DNS server. On current Windows 11 builds, the panel can also show a QR code so a phone can join without typing the password.
I make four adjustments before calling the setup done:
- Use a new password, not the home Wi-Fi password. The temporary network may be visible in a hotel, office, or apartment building.
- Prefer the 5 GHz band when every device is nearby. It usually has less interference and more capacity. Use 2.4 GHz when range matters more than speed.
- Plug in the laptop. Running two wireless roles and moving traffic for several clients drains a battery faster than ordinary browsing.
- Disable the hotspot when the outage ends. A temporary access point should not become forgotten infrastructure.
If the toggle switches itself off, check the wireless driver in Device Manager and install the laptop maker’s current package. Some inexpensive or old adapters cannot remain connected to one Wi-Fi network while broadcasting another. That is a hardware or driver limitation, not a password mistake.
A second failure mode is upstream policy. Some hotels isolate clients or require every device to pass through a captive portal. Authenticate the laptop first, then enable the hotspot. If joined devices still receive no internet, the venue may block connection sharing. At that point, a phone hotspot or a dedicated travel router is the practical fallback.
Internet Connection Sharing handles the odd wired cases
ICS is useful when the outgoing side is Ethernet or when Mobile Hotspot cannot use the adapter you have. Microsoft left it in the classic Network Connections panel rather than the main Settings app.
Press Win+R, enter ncpa.cpl, and press Enter. Right-click the adapter that currently reaches the internet, open Properties, select Sharing, and enable “Allow other network users to connect through this computer’s Internet connection.” Choose the adapter that leads to the device you want online.
Windows normally assigns the shared side an address in 192.168.137.0/24 and starts DHCP there. The connected device should be set to obtain an address automatically. If it still has a static address from another network, it may show a cable connection without reaching anything.
ICS earns its place in a repair kit for situations such as these:
- A desktop has internet over Wi-Fi, while a game console beside it only has an Ethernet cable.
- A laptop reaches a phone hotspot, while an older printer needs a temporary wired connection for setup.
- A machine with two Ethernet adapters needs to share one managed connection with a small test device.
- A wireless adapter cannot create a hotspot, but a USB Ethernet adapter is available.
The dated interface is not the main drawback. ICS chooses its own local subnet and offers little control. If another adapter, VPN, or virtual machine already uses the same range, routing can become confusing. Disable the competing adapter temporarily or change that network’s range rather than stacking more manual routes on top of the problem.
A network bridge is not a stronger version of sharing
In ncpa.cpl, selecting two adapters and choosing Bridge Connections creates a virtual switch between them. That can be valuable when devices need to see broadcasts and appear directly on the upstream network. It is not the preferred way to give a second device ordinary internet access.
A bridge depends on the upstream network to hand an address to every attached device. Hotel and campus networks may allow only one registered device, so the laptop works while the television behind the bridge does not. Many Wi-Fi drivers also handle bridging poorly because normal wireless client mode does not behave exactly like an Ethernet port.
Use a bridge when all four statements are true:
- The upstream network permits multiple client addresses.
- Devices on both sides must remain in the same broadcast domain (the group that receives local discovery traffic).
- NAT would break the service you are testing or extending.
- You can recover locally if the bridge interrupts your laptop’s connection.
That last condition is important. Do not experiment with bridging on the only remote machine you can reach. Creating or removing the bridge briefly resets both adapters and can strand a headless computer.
For a simple outage, Mobile Hotspot or ICS is safer because each creates a small routed network with a clear boundary. A bridge trades that boundary for transparency. Transparency is useful for lab work, but it is unnecessary risk for streaming a film during a router reboot.
Check the temporary network instead of guessing
Once a device joins, test from the inside out. This order tells you which layer failed.
First, confirm that the client received an address. On Windows, ipconfig should show a local address, gateway, and DNS server. On a phone, inspect the connected network details. An address beginning with 169.254 means DHCP failed.
Next, open the gateway address in a browser or ping it from a computer. If the gateway answers but a public site does not load, the temporary local network works and the problem is upstream routing or DNS. Try opening https://1.1.1.1. If that responds while a named site does not, switch the client or laptop to a known DNS resolver.
Finally, test the service you actually care about. A speed test proves very little about a console login, video call, or local printer. Emergency networks often have enough bandwidth but fail because a VPN, firewall, or captive portal handles the shared traffic differently.
VPN behavior deserves its own check. Some VPN clients tunnel traffic from hotspot clients; others protect only the laptop itself. Do not assume a connected phone inherits the laptop’s VPN. Visit an IP-check site from both devices and compare the result before treating the temporary network as private.
Trade-offs
A laptop makes a capable backup router, not a permanent replacement. It consumes more power, has weaker antennas than a good access point, and stops serving everyone when Windows sleeps, reboots for an update, or closes the lid. Its firewall and sharing settings can also change after a driver or VPN update.
Mobile Hotspot prioritizes convenience over control. You do not get reservations, per-client filtering, a guest portal, or useful traffic logs. ICS exposes even fewer friendly controls and can conflict with virtual adapters. Bridging removes NAT but also removes a layer of isolation and relies on the upstream network to accept every device.
A dedicated travel router is worth carrying when you do this regularly. It stays online while the laptop sleeps, offers repeatable settings, and usually handles captive portals and VPNs more predictably. The laptop method wins when the problem is happening now and buying another box would solve tomorrow’s problem instead of tonight’s.
There is also a security cost. The laptop becomes infrastructure while still holding your files, browser sessions, and work credentials. Keep Windows Firewall enabled, use a unique network password, avoid file sharing on the temporary network, and turn the feature off when you are finished.
What I would tell past me
I used to open every network-sharing problem by digging through adapter properties. That was habit left over from older Windows versions. The modern order is shorter.
- Describe “in” and “out” before touching a menu. The two phrases usually identify the tool immediately.
- Try Mobile Hotspot before ICS. The newer panel handles the routine routing work and is easier to reverse.
- Treat bridging as a lab tool. It solves transparency problems, not ordinary internet-sharing problems.
- Test address, gateway, DNS, then the real service. Random toggling hides the layer that actually failed.
- Keep a USB Ethernet adapter nearby. One inexpensive adapter turns many awkward Wi-Fi-only or wired-only situations into a straightforward ICS setup.
When the router comes back, switch off sharing and reconnect devices to the normal network. The laptop did its job: it bought you time with hardware you already owned.