When a Synology NAS becomes invisible on a network connected via an Ethernet switch and router, the issue usually stems from IP conflicts, VLAN isolation, or incorrect subnet configurations. This guide walks you through diagnosing connectivity issues by verifying physical links, checking DHCP assignments, and ensuring your router and switch are configured to allow traffic between the NAS and client devices.
Verify Physical Connectivity and Link Status
The first step in troubleshooting any network visibility issue is to confirm that the hardware layers are functioning correctly. A Synology NAS relies on stable physical connections to communicate with other devices. If the link lights on the Ethernet port of the NAS, the switch, or the router are off or blinking irregularly, there is a physical layer problem.
Check the Ethernet cables connecting the NAS to the switch and the switch to the router. Ensure they are firmly seated and not damaged. Most modern switches and routers have LED indicators for each port. A solid green light typically indicates a successful link at the negotiated speed (e.g., 1Gbps or 10Gbps), while amber might indicate a slower connection or duplex mismatch. If the light is off, try a different cable or a different port on the switch to rule out hardware failure.
Check IP Address Configuration and Subnets
One of the most common reasons a NAS cannot be viewed is that it resides on a different subnet than the client device attempting to access it. For example, if your router assigns IP addresses in the 192.168.1.x range, but the NAS has been manually set to 192.168.0.x, they will not see each other unless proper routing is configured.
Log into your Synology DSM interface using the known IP address. Navigate to Control Panel > Network > Network Interface. Check the IPv4 settings. It is recommended to use DHCP for simplicity, but if you use a static IP, ensure the Subnet Mask, Router (Gateway), and DNS servers match those of your local network. The gateway should be the IP address of your main router.
If you are unsure of the current IP, you can use the ping command from a computer on the same network. Open a terminal and type ping [NAS_IP_Address]. If you receive replies, the network path is open. If you get "Request timed out," there is a blocking firewall or routing issue.
Investigate Switch and Router VLAN Settings
Managed Ethernet switches often have VLAN (Virtual Local Area Network) capabilities. If VLANs are enabled on the switch ports where the NAS and the client computers are connected, they may be isolated from each other even though they are physically connected to the same switch. This is a frequent cause of "invisible" NAS devices in professional or advanced home setups.
Access your switch’s management interface. Check the port configuration for the NAS and the PC. They must be in the same VLAN ID, typically VLAN 1 (the default untagged VLAN). If the NAS port is tagged for a specific VLAN that the client ports are not part of, traffic will not pass. Similarly, check your router settings. Some routers support "Guest Networks" which isolate clients from the local LAN. Ensure your client device is not connected to a guest network while the NAS is on the main network.
Configuring a New Router with Different Networks provides additional context on how subnet mismatches can occur when adding new networking hardware, which is relevant if you recently changed your router setup.Review Firewall and Security Software
Even if the physical and network layers are correct, software firewalls can block the discovery protocols used by Synology NAS. Windows uses SMB (Server Message Block) for file sharing, which relies on specific ports such as 445 (TCP) and 137-139 (UDP). macOS and Linux also use SMB or AFP/NFS depending on the configuration.
On the Synology NAS, go to Control Panel > Security > Firewall. Create a rule that allows incoming traffic on ports 445 and 137-139 from your local subnet. By default, Synology DSM may block all incoming connections except for specific services. You can test this by temporarily disabling the firewall on the NAS to see if visibility returns. If it does, re-enable the firewall and add the necessary rules explicitly.
Additionally, check the firewall settings on your client computer. Windows Defender Firewall or third-party antivirus software might block "Network Discovery." Ensure that Network Discovery is turned on in your operating system's network settings.
Test with Direct Connection
To isolate whether the issue lies with the switch or the router, connect the NAS directly to your computer using an Ethernet cable. Bypass both the switch and the router. Set a static IP on your computer in the same subnet as the NAS. If the NAS is visible in this direct connection, the problem is definitely within the switch or router configuration, such as IGMP snooping, AP isolation, or misconfigured DHCP scopes.
If the NAS is still not visible in a direct connection, the issue likely lies with the NAS network interface card (NIC) settings or the operating system configuration on the NAS itself. In this case, consider resetting the network settings in DSM or updating the firmware of the NAS.
Frequently Asked Questions
Why can I ping my NAS but cannot access files?
Ping uses ICMP protocol, which is often allowed by firewalls even when file-sharing protocols like SMB are blocked. To access files, you must ensure that ports 445 (TCP) and 137-139 (UDP) are open in both the NAS firewall and the client device's firewall settings.
Does enabling VLANs hide my NAS from other devices?
Yes, if devices are placed in different VLANs without proper inter-VLAN routing configured on your router or managed switch, they will not be able to communicate. Ensure the NAS and your client devices are assigned to the same VLAN ID for basic visibility.
What is the difference between AP Isolation and VLANs?
AP Isolation is a Wi-Fi feature that prevents wireless clients from communicating with each other or wired devices. VLANs are a broader network segmentation tool. Both can prevent a NAS from being seen if the client is on an isolated segment and the NAS is not.
How do I find my Synology NAS IP address automatically?
You can use Synology's official "Synology Assistant" utility available for Windows and Mac. It scans the local network and lists all active Synology devices along with their IP addresses, even if they are not currently accessible via a browser.
Can a faulty Ethernet switch cause intermittent visibility?
A failing switch can cause packet loss or link flapping, leading to intermittent connectivity. While the NAS might appear online occasionally, data transmission will fail. Check the switch logs or replace the switch with a known good unit to test this hypothesis.