Backups & Storage
NAS not showing on network
Find a home NAS on the network when it disappears — usually offline, on a changed IP, blocked by discovery, or waiting on storage and network health checks.
Problem summary
A NAS that disappears is usually offline, on a changed IP, blocked by discovery, or waiting on storage/network health checks.
Check NAS power, link lights, and drive/activity state.
Router admin app > clients/DHCP leases > NAS hostname or MAC
The NAS is powered, has Ethernet link, and is not in obvious fault or rebuild state.
Stop before reset, initialize, format, or disk removal.
Layer path
Step-by-step runbook
Start here. Do each check in order, compare it to the expected result, and stop when the evidence explains the failure or the safe stop point applies.
Check physical and storage status first
Check: Confirm power, link light, and whether the NAS is reporting disk, volume, or rebuild activity.
Expected result: The NAS is powered and not asking for risky storage action.
If not: Do not repeatedly reboot or pull drives; inspect the vendor status path.
Safe stop: Stop before reset, initialize, format, or disk removal.
Find the NAS by router lease
Check: Open the router client list and find the NAS hostname or MAC address.
Expected result: You get the current local IP.
If not: Try known-good Ethernet and switch ports before changing NAS settings.
Use direct IP before discovery
Check: Open the NAS admin page by IP, then test the share by IP.
Expected result: Direct IP separates discovery from reachability.
If not: Check subnet, VPN, guest Wi-Fi, and NAS firewall.
Test the actual service
Check: Test SMB port 445 or the backup service you need, not only ping.
Expected result: The required service responds.
If not: Check NAS SMB/NFS service and account settings.
Verify storage before backup trust
Check: Review pool, volume, disk health, snapshots, and latest backup status.
Expected result: Storage health and restore path are credible.
If not: Treat this as storage-risk work, not just network discovery.
Decision tree
If: Router client list does not show the NAS.
Then: Power, cable, switch, port, VLAN, or IP configuration is likely first.
Action: Check link lights, try a known-good cable/switch port, and inspect NAS display/app before resets.
If: Admin UI by IP works but Windows Network view does not.
Then: Discovery is weak, but the NAS is reachable.
Action: Use a stable IP/hostname and check SMB service or Windows credentials.
If: Admin UI works but SMB port 445 fails.
Then: File service is stopped, blocked, or disabled.
Action: Check NAS SMB/NFS service settings and firewall before Windows-side changes.
If: Shares open but backup jobs fail.
Then: Destination path, backup account, or write permissions are the active layer.
Action: Test with the backup account and create one harmless file.
If: NAS reports degraded pool, disk errors, or rebuild.
Then: Storage health is the priority.
Action: Stop network tinkering and protect data.
Safe stop: Stop before reset, initialize, format, or disk removal.
Evidence table
| Symptom | Evidence to collect | Likely layer | Next action |
|---|---|---|---|
| NAS absent from Windows Network. | Direct IP admin page works. | Discovery or SMB browsing | Map by stable IP and check SMB service. |
| NAS absent from router client list. | No hostname/MAC lease, no link light, or switch port dark. | Power, cable, switch, or IP | Fix physical/network identity before share permissions. |
| Ping works, share fails. | Ping NAS-IP passes but Test-NetConnection NAS-IP -Port 445 fails. | SMB service or firewall | Check NAS file-service settings and Windows firewall path. |
| Backup app cannot write. | User can browse but cannot create a harmless test file. | Share permissions or backup account | Fix the narrow NAS user/group permission. |
| NAS appears but backup reliability is unknown. | Storage pool warnings, full volume, SMART errors, or failed snapshots. | Storage health | Verify storage health and restore path before trusting jobs. |
Commands and settings paths
Router lease check
Router admin app > clients/DHCP leases > NAS hostname or MAC
Where: In the home router or gateway admin UI.
Expected: The NAS has a current local IP on the expected subnet.
Failure means: The NAS may be offline, on a different network, or using a bad static IP.
Safe next step: Check cable/switch/port and NAS network settings before reset.
Direct admin test
https://NAS-IP or http://NAS-IP
Where: In a browser from a device on the same trusted LAN.
Expected: The NAS login or status page opens.
Failure means: The NAS is not reachable at the network/admin layer.
Safe next step: Check router lease, power, link, and subnet before SMB.
SMB port test
Test-NetConnection NAS-IP -Port 445
Where: PowerShell on a Windows client.
Expected: TcpTestSucceeded is True.
Failure means: File sharing service or firewall path is not open to this client.
Safe next step: Check NAS SMB service and client network profile.
Storage health check
NAS admin UI > Storage Manager or equivalent > pool, volume, disk health, SMART
Where: In the NAS vendor admin UI.
Expected: Pool, volume, and disks are healthy enough for reads/writes.
Failure means: The NAS may be visible but unsafe as a backup target.
Safe next step: Preserve data and follow vendor recovery documentation.
Hardware and platform boundary
Change only when
- Replace network hardware only after power, cable, switch, DHCP lease, and service checks prove the path is unstable.
- Replace or expand NAS storage only after storage health, backup age, and restore requirements show the current box is a risk.
Evidence that matters
- Reliable Ethernet, supported SMB/NFS services, alerting, storage-health visibility, snapshots, backup tooling, and UPS integration.
- For backup NAS use, restore workflow and alerting matter more than app count.
Evidence that does not matter
- Discovery branding or app convenience does not matter if direct IP and services are unstable.
- Extra CPU does not fix a missing DHCP lease or failed disk.
Avoid
- Avoid factory reset as an early discovery fix.
- Avoid exposing NAS admin or file services to the internet.
Related tool/checklist
Use the linked tool when you need a guided plan from your exact symptoms instead of a static checklist.
Backup plan builderRelated problems
Last reviewed
2026-05-07 · Reviewed by HomeTechOps. Reviewed for router lease checks, direct-IP diagnosis, SMB service isolation, storage-health stop points, and backup safety.
Sources/assumptions
- Assumes a consumer NAS used as one part of a home backup/storage plan.
- Detailed NAS storage repair is outside this quick network-reachability runbook; vendor storage health guidance wins.
Source-backed checks
HomeTechOps turns official docs and conservative safety rules into a shorter runbook. These links are the source trail for the page direction.