If your ASUS guest Wi‑Fi can reach the internet but not a NAS, the usual cause is guest isolation on the router, not a broken NAS. Start by testing the NAS by IP from the guest network before changing any settings; if IP works but the name does not, you’re looking at name resolution, not a total network failure. The safest fix is to open only the one path you need, not the whole LAN.
What this failure usually looks like
On the guest network, the problem usually shows up in one of four ways: ping fails, SMB or NFS access fails, the NAS web UI will not open, or the NAS name never resolves even though the IP address might still work.
Those are different failures. If nothing replies at all, the guest network may be blocked from the LAN, the NAS may be filtering traffic, or both. If the IP works but SMB, NFS, or the web UI does not, the connection exists and the failure is more likely on the NAS side. If the IP works but the name does not, the issue is usually DNS or local discovery rather than raw connectivity.
A quick decision table helps separate the branches:
| Guest test | What it usually means |
|---|---|
| IP fails | Router isolation, bridge/VLAN separation, firewall rule, or NAS filtering |
| IP works, SMB/NFS fails | NAS permissions or share service settings |
| IP works, name fails | DNS name resolution or discovery issue |
| NAS web UI works but shares do not | Service-specific NAS permissions |
Before you start
Use a device on the guest SSID and the NAS’s IP address for the first check. That one test tells you whether the guest network can reach the NAS at all, without changing anything yet.
Keep these boundaries in mind:
- ASUS guest networks are normally set to block access to the private LAN.
- ASUS says
Access Intranetis off by default, and when it is off, guest devices cannot access private-network devices or services such as NAS devices and shared folders. - ASUS also says
Access Intranetonly works in Wireless router mode; it is not available in AP mode, and management in AP mode is handled by the front router or modem. - On supported Guest Network Pro models, ASUS provides profile-level advanced settings, including DNS assignment from the guest network profile.
Stop and check the upstream router instead of forcing changes on the ASUS unit if the ASUS device is in AP mode. Also stop if you only need one NAS service and you can already tell the router change would expose printers, cameras, admin pages, or other LAN devices you do not want guests to see.
Why ASUS guest Wi‑Fi usually can’t see the NAS
On an ASUS router, guest Wi‑Fi is often designed to keep guests off the wired LAN. That is why a phone or laptop can connect to the SSID, get internet access, and still be unable to reach a NAS sitting on the private network.
The common router-side blockers are:
- Guest isolation itself, which is the default guest-network behavior.
Access Intranet, which controls whether guest clients can reach private-network devices.- AP mode or bridge separation, where the ASUS router is not the device making the guest-policy decision.
- AiMesh or guest-network separation, where guest features may be handled differently on a node or not offered in the same way as on the main router.
- Firewall rules, bridge rules, or guest VLAN separation that keep guest clients off the LAN even when Wi‑Fi looks normal.
I would not treat full internet access as proof that the router is open to the NAS. In practice, the guest SSID can be working exactly as intended while every local service remains blocked.
How to open only what guests actually need
Start with the smallest change that matches your goal. If you want guests to reach one NAS service, do not turn off guest isolation for the whole LAN unless you really mean to open the rest of the network too.
- Test the NAS by IP from the guest device. Open the NAS’s IP address from the guest network before touching any router setting. If the IP responds, the path exists and the next question is name resolution or service permission, not basic connectivity.
- If the IP works but the name does not, fix name resolution first. That usually means the guest network is not using a DNS server that knows the NAS name, or local discovery is being blocked. On supported Guest Network Pro models, ASUS exposes advanced settings where you can assign DNS for a guest network profile. If your model does not expose that option, check the current ASUS interface for the exact menu names on your firmware, because labels vary by model.
- If the IP works but the service fails, check NAS permissions next. A share can still be blocked by the NAS even when the router is open enough. SMB permissions, NFS export rules, web app access controls, and guest account permissions can all block access. If the NAS offers per-service or per-user permissions, that is the narrowest place to make the exception.
- Only if you truly want guest devices to reach private LAN devices, enable
Access Intranet. ASUS says that setting allows guest devices to access private-network devices and services such as NAS shares. That is the broad fix, not the narrow one, so use it only when you are comfortable with guests reaching other LAN resources too.
If your router is in AP mode, do not keep looking for Access Intranet on the ASUS page. ASUS says that option does not exist in AP mode because the front router or modem owns that control. In that case, adjust the upstream router’s guest or VLAN policy instead.
If you are using AiMesh, check whether the guest network is being managed on the main router or whether the node has its own limitations. A setting that exists on the main unit may not behave the same way on a node, so check the current ASUS interface for your model rather than assuming every mesh node exposes the same controls.
How to confirm the fix and when to stop
Verify the fix from the guest device itself, not from a wired LAN computer. First open the NAS by IP. If that works, try the NAS name. Then open only the exact service you intended, such as the SMB share, NFS share, or NAS web page.
The fix is good enough when the guest device can reach the one NAS service you allowed and still cannot reach other LAN devices. Try a different shared folder, a printer, or the router admin page from the guest network. Those should stay blocked if you meant to keep guest isolation in place.
If guests can now reach more of the LAN than you wanted, roll the change back and move the exception to the NAS side or the DNS side instead. That keeps the guest network useful without turning it into a second trusted LAN.
Frequently Asked Questions
Why does the NAS work by IP but not by name on guest Wi‑Fi?
That usually points to DNS name resolution or local discovery, not a broken connection. If the guest device can reach the NAS by IP, keep guest isolation in place and check whether the guest network is using a DNS server that knows the NAS hostname.
Should I turn on ASUS `Access Intranet` to fix this?
Only if you want the guest network to reach private LAN devices more broadly. ASUS says `Access Intranet` is off by default and blocks access to devices such as NAS shares, so it is a broad fix, not the safest first one.