Home » CloudZat UK » Synology not showing on the network: find the NAS without resetting it

Synology not showing on the network: find the NAS without resetting it

NAS SETUP, MAINTENANCE & RECOVERY

A Synology missing from Windows Network is not necessarily offline. Discovery, the NAS address, DSM access and SMB file sharing are separate parts of the connection. Work out which one has failed before pressing Reset or accepting an installation prompt. The aim is to find the existing system while preserving its storage and settings.

Editorial review: 15 November 2026 · UK

Quick answer

Check that the NAS has completed startup and that the client is on the intended local network. Find its current address in the router or with Synology Assistant or Web Assistant, then test DSM and the exact SMB share separately. If direct access works but discovery does not, investigate naming and discovery settings. Never initialise a NAS containing wanted data just because it reappears with an unexpected status.

Steps to follow

  1. Confirm power, link and network placement

    Observe the NAS power and status indicators and compare them with the exact model's guide. A device still booting needs different attention from one with a steady running state. Check the Ethernet connection and try a known working cable or switch port if the link is absent. Record recent router, switch or NAS changes before altering several settings at once.

    Connect the computer to the same intended local network for the first test. Guest Wi-Fi, client isolation and separate VLANs can prevent discovery or access by design. A VPN on the computer can also change routing. Do not disable the entire network firewall; identify whether the client and NAS are meant to communicate and examine the relevant path only.

  2. Locate the current NAS address

    Check the router's client or DHCP list for the known NAS name or hardware address, if you administer that router. Compare the address with any saved bookmark. A router replacement or expired reservation can move the NAS to a different address. Use Synology Assistant or the documented Web Assistant route on the trusted local network as another supported discovery method.

    Confirm the device identity before signing in. If the discovery result reports Not installed, Migratable or another unexpected condition on a machine that previously held data, stop and consult the matching Synology recovery guidance. Discovery success does not authorise a clean installation. Preserve the message and any storage details rather than clicking through a wizard simply to make the warning disappear.

  3. Test administration and files independently

    Open the known DSM management address using the protocol and port configured for that installation. If it responds, the NAS is reachable even if Windows Network does not list it. Then test the exact SMB share path in File Explorer, using the intended ordinary NAS account. A browser login and an SMB session are different tests with potentially different identities.

    If the IP address works but the server name fails, investigate name resolution. If DSM works but the share does not, inspect the file service, account and permissions. Keep the exact error message. A credential rejection should not lead to reconfiguring the router, while a missing network path should not immediately lead to changing every folder ACL.

  4. Fix the narrow cause and verify after reconnecting

    Correct the identified address, naming, service or credential issue using the installed DSM and client documentation. Reconnect with a normal user and open a harmless file. If writing is required, create and reopen a test item. Check the result after the client signs out or restarts, at a time when doing so will not interrupt work.

    If the fix involves a stable addressing plan, record the reservation or supported configuration and update the relevant bookmarks and mappings. Do not assign a static address that conflicts with another device or an unmanaged DHCP range. Keep local console or supported recovery information available before changing networking remotely. A successful immediate test should survive the next ordinary reconnection.

Detailed guidance

Discovery is a convenience, not the only access path

Windows Network and a direct share path can behave differently because browsing relies on discovery services in addition to ordinary connectivity. If a verified direct path works, use that observation to narrow the problem. Do not enable obsolete SMB1 or unauthenticated guest access simply because an old guide links those settings to browsing.

Current Windows security requirements and NAS firmware support need to agree. Check the edition and release when access changes after a Windows update, and use supported authentication and SMB settings. A visible device icon is less important than a reliable, correctly protected connection to the required files. Treat discovery repair separately from weakening the connection itself.

Multiple network interfaces can make the symptom confusing

A NAS with several Ethernet ports can have more than one address or an arrangement such as a bond or VLAN. Record the interface and subnet used for management before moving cables. A computer on one network may not be allowed to reach the address attached to another. Avoid connecting extra ports randomly in the hope that discovery will improve.

If a direct temporary connection is part of a vendor-supported diagnostic, follow the addressing instructions and preserve the original settings. Do not assume that plugging two devices together automatically gives them compatible addresses. Restore the intended network layout after testing and verify that ordinary users still reach the correct share through the documented path.

Recovery prompts deserve a pause

An inaccessible NAS can still contain intact data. Reset, reinstall and initialise options have different consequences, and their wording varies with the device state. Read the exact model and DSM guidance before choosing one. Keep independent backups and encryption material available, and ask support to interpret an unexpected recovery status if the next step is unclear.

Provide useful evidence: the model, LED state, discovered address, exact message, whether DSM opens and whether a direct SMB path works. This lets support distinguish a network problem from a storage or boot issue. Avoid sharing passwords or full configuration archives in public discussions. Preserve the existing system until the cause and recovery procedure are established.

Compare the options

Situation Recommended action Check before continuing
DSM opens by IP but not by name Investigate naming or DNS Storage is not proved faulty by a discovery issue
DSM works but SMB share fails Check file service, account and folder permissions Use the intended ordinary user
Neither discovery nor direct access works Check boot state, cable and network placement Guest networks may block access deliberately
Discovery offers unexpected installation Preserve the state and consult recovery guidance Do not initialise disks containing wanted files

Synology NAS options on Amazon

Use a Synology DiskStation for the Synology steps in this guide. Check support for the exact DSM package and model; another brand does not run Hyper Backup or Synology Drive. Manufacturer compatibility information.

Checking current Amazon listings…

Browse NAS on Amazon

As an Amazon Associate, we earn from qualifying purchases. Prices and availability can change; Amazon’s checkout price applies.

Frequently asked questions

Do I need to reset the NAS if Windows cannot see it?

Not automatically. Check the current address and direct DSM and SMB access first. Discovery can fail while the NAS and files remain available. Use a reset only for a defined problem with the model-specific consequences understood.

Why did access fail after changing the router?

The NAS may have received a different address, a reservation may be missing, or the new network may separate clients differently. Compare the current address and subnet with the previous mapping, then verify the intended local route before changing storage settings.

Official documentation

This guide combines current official documentation with practical recovery checks. It does not claim hands-on testing of your installation. Menu labels and supported procedures can vary by release; follow the documentation for your installed version.

Scroll to Top