A UniFi guest SSID that reaches the internet but not a NAS is often behaving as designed: guest isolation usually blocks private LAN devices. The safest first move is to verify whether you’re seeing expected guest isolation or a real routing, firewall, VLAN, or NAS permission problem before you loosen anything. In practice, the fix is usually a narrow allow rule for the NAS, not turning guest protection off.
Symptom
You can join the guest Wi‑Fi, browse the web, and still fail to open the NAS by IP or by name. That usually shows up when you try to reach the NAS admin page, map a file share, or use a media app that depends on local network access.
The confusing part is that the guest network can look healthy from the outside. Internet access works, but one local target does not, so it’s easy to blame UniFi too early when the block may be coming from the guest policy, the gateway firewall, a VLAN boundary, or the NAS itself.
Before you start
Start with the least disruptive check: test the NAS directly from the guest SSID by IP address, not just by hostname. If you only test internet access, you won’t learn whether local routing is blocked or whether name resolution is the real problem.
Before changing anything, confirm these points:
- You are really connected to the guest SSID, not your main Wi‑Fi.
- You know the NAS IP address.
- You know whether the NAS and guest client are on the same subnet or on different VLANs.
- You can tell whether the failure is at the NAS web page, the file share, or both.
Stop and rethink the change if you cannot confirm the NAS IP or the network layout. Guessing at firewall rules before you know where the traffic stops usually creates a bigger mess than the original problem.
Find the layer that is blocking traffic
Work from the guest client toward the NAS and stop at the first failure.
If the guest client cannot reach any private LAN device, guest isolation or a gateway firewall rule is the first place to look. If it can reach some local devices but not the NAS, the NAS may be blocking access on its own. If the NAS sits on a different VLAN, routing or inter-VLAN firewall policy may be the thing stopping traffic even though the Wi‑Fi itself is fine.
Use the result to narrow the problem:
- Guest Wi‑Fi has internet only: that often means guest isolation is active, which is normal on many UniFi guest setups.
- Guest Wi‑Fi can reach some LAN devices but not the NAS: look at the NAS firewall, share permissions, or service settings.
- Guest Wi‑Fi cannot reach anything on the LAN and the NAS is on another VLAN: look at routing and gateway firewall rules.
- Guest Wi‑Fi reaches the NAS IP but file access still fails: the network path is open, but the NAS service or account permissions are blocking you.
Don’t rely on ping alone. Ping can be blocked while SMB or NFS still works, and ping can also succeed when the share itself is still denied. Treat ping as a hint, not proof.
UniFi settings that usually control guest-to-LAN access
In UniFi, guest access is usually controlled by a mix of the guest Wi‑Fi settings, the guest network settings, and the gateway firewall rules between subnets or VLANs. That’s why one screen rarely tells the whole story.
The settings that usually matter are:
- Guest isolation on the SSID or network.
- Network isolation or similar guest-blocking options on the guest network.
- Firewall rules on the gateway that block traffic from the guest VLAN to the LAN.
- Any explicit allow rule for one device, such as the NAS IP.
The safest pattern is to keep guest isolation in place and add a narrow exception for the NAS if you truly need guest clients to reach it. Avoid disabling guest isolation just to make one device work, because that usually opens access to the whole LAN, not just the NAS.
If your guest SSID sits on one VLAN and the NAS on another, you usually need an explicit allow rule for the NAS address or the service port you actually use. Without that, the Wi‑Fi association succeeds but the router still drops the traffic.
How to test the fix without opening the whole LAN
After any change, test the NAS directly from a guest client and then test one other LAN device that should still stay blocked. That tells you whether you fixed the right path without accidentally making the guest network trusted.
- Connect a test device to the guest SSID.
- Open the NAS by IP in a browser if it has a web interface.
- Try the file share you actually use, such as SMB in a file manager or NFS from the client.
- Try one private LAN device that should remain unreachable.
If the NAS page opens but the share still fails, the network path is probably fine and the remaining block is on the NAS. If the NAS still does not open, keep looking at UniFi guest isolation, VLAN routing, or gateway firewall rules.
The best proof is a repeatable test after a reboot or rule save: the NAS should work from guest Wi‑Fi, while the rest of the LAN stays blocked.
Which NAS-side settings can still block access
Even when UniFi allows the traffic, the NAS can still refuse it. That happens when the NAS has its own firewall, share permissions, service restrictions, or account rules that do not allow the guest client.
Check the NAS-side items that commonly block access:
- The NAS firewall allows only trusted subnets.
- SMB, NFS, or the web admin service is disabled.
- The share is not exposed to the account you are using.
- The NAS expects a different protocol than the client is trying to use.
If the NAS is reachable by IP but the share will not open, stay on the NAS side until the service works there. Changing UniFi again at that point is usually the wrong move.
How to keep guest Wi‑Fi isolated while allowing only the NAS
Keep the guest network blocked from the rest of the LAN, then add the smallest exception that solves the real use case. In most home and small-office setups, that means allowing only the NAS IP, and only the service you need, while leaving all other private devices blocked.
A clean approach is:
- Keep guest isolation on.
- Allow the guest VLAN to reach the NAS IP only.
- If possible, limit the rule to the service port you need.
- Leave all other LAN access denied.
That keeps visitors off your printers, workstations, and admin devices while still letting them reach the NAS if that’s part of your design. If you can’t make the exception that narrowly, it’s safer to leave the NAS blocked from guest Wi‑Fi.
Conclusion
Once you know whether the block is expected guest isolation or a real misconfiguration, the fix is usually obvious. Change only the layer that is actually stopping traffic, then re-test the NAS by IP from the guest SSID.
Frequently Asked Questions
Should a UniFi guest network be able to reach a NAS?
Usually not by default. Guest isolation commonly blocks private LAN devices, including a NAS, so that behavior can be expected unless you add a narrow exception for that one host or service.
Why can I ping the NAS but still not open the share?
Because ping only checks basic reachability, not the file service itself. The NAS may answer ping but still block SMB, NFS, or the web interface with its own firewall, service settings, or share permissions.
What is the safest way to let guests reach only the NAS?
Keep guest isolation on, then allow only the NAS IP and, if possible, only the service port you need. That preserves guest isolation while exposing just one device instead of the whole private network.