Yes, this is often normal Orbi guest-network isolation: the guest Wi‑Fi is usually kept off the main LAN, so a NAS on your private network won’t answer from a guest device. The first fix is to separate a name problem from a real reachability problem by testing the NAS by IP address first. If you need guest devices to reach only one NAS share, make the smallest Orbi and NAS change that opens just that path, not the whole LAN.
Confirm the fix
A working setup should pass all three checks in order. First, the guest device should reach the NAS by IP address. Second, the hostname should resolve if your setup depends on local DNS or name broadcasting. Third, the file share should open with the correct user account.
If the IP works but the hostname does not, the problem is name resolution or discovery, not raw connectivity. If both work but the share still fails, look at SMB permissions and the NAS firewall. If the guest device still cannot reach the IP after you changed Orbi settings, the guest isolation change did not take effect or another rule is still blocking the path.
If you want guest devices to have only limited access, stop once the one share works and do not open broader LAN access just to make the test easier. In many homes, the right answer is to keep guest isolation on and use a more controlled path, such as a dedicated NAS account or VPN, when you need access from outside the main network.
Conclusion
If the guest device still can’t reach the NAS after these checks, leave guest isolation in place and use a narrower access method instead of widening the whole guest network.
Frequently Asked Questions
Is it normal for Orbi guest Wi‑Fi to be unable to reach my NAS?
Yes. On Orbi, guest Wi‑Fi is commonly isolated from the main LAN by design, so a NAS on the private network may be unreachable from guest devices. The key is to tell expected isolation apart from a separate IP, DNS, SMB, or firewall problem.
Should I test the NAS by IP or by hostname first?
Test by IP first. A direct IP check tells you whether routing works, while a hostname check can fail because of DNS resolution or local discovery even when the NAS is reachable.