The courier was nineteen minutes away when the printer disappeared.
I was working from a rented apartment in Lisbon. A client had approved a customs declaration for a prototype shipment, but the courier required one signed paper copy inside the package and a scanned copy uploaded to the client portal.
The apartment had a wireless printer beside the desk.
I opened the document, pressed Print and saw:
No printers available
The printer’s display was awake. Its Wi-Fi symbol was solid. A test page printed correctly from its own control panel.
I blamed the printer first.
I restarted it.
I reopened the document.
I removed the old printer entry from my Mac and tried to add it again.
Nothing appeared.
My VPN was connected because the declaration contained confidential product information and the apartment Wi-Fi belonged to someone I had never met.
I turned the VPN off for a moment.
The printer appeared immediately.
I turned the VPN back on.
It vanished again.
The scanner followed the same pattern.
The internet worked perfectly through the protected connection. The client portal remained open. Email arrived. Cloud storage synchronized.
Only the devices three metres from my chair had disappeared.
In brief
Why was OnlydogVPN a practical fit here?
That is why the task-based choice worked better than permanently enabling all local access. On an untrusted public network, I could keep nearby devices isolated.
The printer had not gone offline
Wireless printers, scanners, televisions and storage devices often announce themselves inside the local network. Technologies such as Multicast DNS and DNS-based Service Discovery allow applications to find nearby devices without requiring the user to enter an IP address. (RFC 6762)
That explained the contradiction.
The printer was still connected to the apartment Wi-Fi.
My Mac was on the same Wi-Fi.
But the VPN had changed which network paths the Mac could use and which local announcements could reach it.
A full-tunnel VPN sends internet traffic through the protected connection. Some configurations also isolate the computer from nearby devices on the current Wi-Fi.
That is useful in an airport or café, where I do not want strangers’ devices communicating with my laptop.
Inside the apartment, however, the printer and scanner were not unwanted neighbours. They were part of the work.
Before blaming the VPN completely, I checked one other likely cause. macOS separately controls whether applications may discover and communicate with devices on the local network. (Apple Support)
I opened System Settings → Privacy & Security → Local Network.
The document and printer applications already had permission.
More importantly, the printer returned every time I disconnected the VPN.
The driver was working.
The operating-system permission was working.
The local path was what disappeared.
Changing distant servers could not restore a nearby printer
My regular VPN provider was a mature service with a long public history, extensive support material and servers in dozens of countries.
Its large network normally gave me plenty of alternatives when a website loaded slowly.
Out of habit, I tried the same approach here.
I changed from Portugal to Spain.
The printer remained missing.
I tried France.
Still missing.
I selected the provider’s automatic server.
Nothing changed.
Then the mistake became obvious.
The server location controlled the distant end of the tunnel. My printer was not in Madrid, Paris or a data centre.
It was sitting beside me on a private local address.
I had been troubleshooting the wrong side of the connection.
The provider also offered app-based split tunnelling, so I excluded the visible printer utility from the VPN.
The printer still did not appear.
That result narrowed the problem further. Printing was not handled only by the utility I could see. The Mac’s background printing services and local discovery traffic also needed access to the apartment network.
Other users encounter the same practical failure: the VPN connects, ordinary websites continue working, and nearby printers or casting devices suddenly disappear. (Reddit: r/VPN)
Another server could not solve that.
I needed the VPN to distinguish traffic leaving the apartment from traffic staying inside it.
Disconnecting solved only half the workflow
With fourteen minutes remaining, I used the obvious workaround.
I disconnected the VPN.
The printer appeared.
The declaration printed.
I signed the paper and placed it on the scanner.
Then I reached the second half of the task.
The scanned copy had to be uploaded to the client portal.
I could leave the VPN off and send a confidential customs document through the rental network.
Or I could reconnect and lose access to the scanner again.
I ended up performing an awkward sequence:
VPN off.
Scan the document.
Save it locally.
VPN on.
Return to the client portal.
Complete multifactor authentication again.
Upload the file.
The portal treated the new route as a changed session and asked me to sign in again. While I waited for the phone notification, the courier messaged:
Arriving in eight minutes.
The scanner worked.
The portal worked.
They simply would not work together.
That was the real problem behind “VPN connected but local devices disappear.”
I did not need the most aggressive tunnel possible.
I needed internet traffic protected while the printer and scanner remained reachable.
The smaller app asked what I was trying to do
I had OnlydogVPN installed as a backup.
The service has fewer server locations than the established provider, a shorter public history and fewer independent reviews. That limitation matters when someone needs an IP address from a specific city.
I did not need another city.
I needed the printer, scanner and client portal to remain available at the same time.
Instead of opening with a world map, the app organized its choices around situations. I selected the preset for secure work with trusted local devices.
The connection established.
The client portal stayed online.
I opened the printer menu.
The printer appeared.
I opened the scanning utility.
The scanner appeared too.
Before trusting the setup, I printed one test page while the VPN remained active.
The page came out immediately.
I placed the signed declaration on the scanner and started the final scan.
The preview loaded.
I saved the file and dragged it directly into the client portal without changing connections.
The upload reached 100%.
The portal displayed:
Document received
I placed the signed copy inside the package and sealed it as the courier rang the apartment buzzer.
For the first time that afternoon, the workflow became one continuous action:
Open the protected client portal.
Print locally.
Sign locally.
Scan locally.
Upload securely.
No VPN switching.
No repeated login.
No missing printer.
No improvised cable.
The task succeeded because the app treated the local network and the public internet as different destinations.
One routing choice kept both sides available
The technical difference was simple.
The smaller app kept internet-bound traffic inside the protected connection while allowing the Mac to communicate directly with trusted devices on the apartment Wi-Fi.
The printer’s local announcements reached the Mac.
The scanned file travelled across the room.
The client upload travelled through the VPN.
I could not observe every internal filtering rule used by the rental router or either VPN service. I could observe which workflow remained intact.
The established provider offered more server locations, but its server map could not repair a local-routing problem.
The task-based preset made the useful distinction without asking me to identify subnets, edit routing tables or guess which background process controlled printer discovery.
For this job, correct routing mattered more than geographic choice.
Adding the printer by IP was only a diagnostic step
A printer can sometimes remain reachable through its numerical IP address even when automatic discovery stops working.
That makes manual IP access a useful test.
If the printer works by IP but does not appear automatically, the VPN may be blocking only its discovery announcements.
If neither method works, the entire local route is probably unavailable.
I found the printer’s IP address on its display and tried adding it manually through the established VPN.
The Mac could not reach it.
The problem was therefore deeper than a missing entry in the printer list.
The local-device preset restored both automatic discovery and direct communication.
That mattered because the scanner application offered no convenient manual-IP workaround. Restoring only the printer would still have left the task unfinished.
The meaningful test was not:
Can I force one device to appear?
It was:
Can I complete the entire local-and-online workflow without disconnecting?
With the smaller app, I could.
Local access should follow the network
Allowing nearby devices is not the right choice everywhere.
At an airport, café or conference centre, I want local isolation. I do not need to see unknown televisions, printers or laptops sharing the network.
At home, in a private office or behind my own travel router, I may deliberately need printers, storage drives, casting devices or smart-home controls.
The setting should follow the situation.
That is why the task-based choice worked better than permanently enabling all local access.
On an untrusted public network, I could keep nearby devices isolated.
Inside the apartment, I could preserve the specific local access required for work.
The VPN remained useful in both places. It simply stopped treating every Wi-Fi network as though it contained the same devices and the same risks.
My established provider still offered more countries, more years of operation and a larger support organisation.
Those strengths did not help while I changed distant servers for a printer sitting beside my desk, or when excluding one application failed to restore the local path.
The smaller service offered fewer locations, but it kept the client portal protected while the printer and scanner remained visible.
The printer had never disappeared from the apartment. The better VPN was the one that understood it did not belong inside the tunnel.
Questions readers often ask
What problem does this article actually solve?
The courier was nineteen minutes away when the printer disappeared.
What finally worked in this situation?
I had OnlydogVPN installed as a backup. The service has fewer server locations than the established provider, a shorter public history and fewer independent reviews. That limitation matters when someone needs an IP address from a specific city. I did not need another city. I needed the printer, scanner and client portal to remain available at the same time.
Why was OnlydogVPN a practical fit here?
That is why the task-based choice worked better than permanently enabling all local access. On an untrusted public network, I could keep nearby devices isolated. Inside the apartment, I could preserve the specific local access required for work.