Unable to ping or connect to Synology NAS DSM-918
Hello --
Network topology was:
ONT -> Untangle (DHCP) -> 4-port Linksys Switch --> Deco Main Unit (1 of 3) in Access Point Mode
Switch -> Synology DSM-918 (hardwire)
Everything worked great.
Network topology is now:
ONT -> Deco Main Unit in Router Mode -> Synology (hardwire)
Untangle failed me and have removed it from the topology.
In the current configuration, Synology is not accessible through Ping or Website.
Both ports on Synology WERE DHCP, have changed them to be static so that I could work on the device without constant rewiring.
On Synology Port 1 = 192.168.68.15, 255.255.255.0, 192.168.68.1
On Synology Port 2 = 192.168.1.15, 255.255.255.0, 192.168.1.1
Deco is also configured to 255.255.255.0, instead of 255.255.252.0
I have a laptop which is connected hardwire to Synology port 2 with a static IP Address of 192.168.1.26, 255.255.255.0, 192.168.1.1. Wireless is also on and is 192.168.68.100, 255.255.255.0, 192.168.68.1. On this laptop, Synology is reachable via browser and ping at 192.168.1.15. Pinging 192.168.68.15 from ANY device in the subnet fails, and of course, the website is unavailable. Deco will register the device on the network in the client list, but the Synology remains stubbornly unavailable.
Anyone have any thoughts on why Synology is inaccessible when Deco is in Router Mode?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@David-TP --
After bashing my head against the wall, I finally remembered that the Synology was firewalled to specific internal sub-nets as it was internet facing at one time. It came to light when I realized that the synology was able to reach the internet and so pointed to a block on the device itself. When I chased the firewall settings, I saw my blunder.
Thank you for your patience and for walking me through this.
Very much appreciate it.
Best Regards...
- Copy Link
- Report Inappropriate Content
Deco mesh does not like devices with static IP addresses configured on them.
I'll tell you how I configured my Synology NAS, and it runs just fine since the beginning. You decide if you just follow my steps and have it easy, or not.
----------
Both ports on my Synology NAS are configured as "Get network configuration automatically (DHCP)" .
I am using only Port 1 (LAN 1). Port 2 (LAN 2) is not connected.
Port 1 is wired directly to the router (Main Deco).
I verified I can ping NAS and access its Web interface using its current IP address (Deco app will report NAS IP address).
Having all above steps completed successfully, I configured reserved IP address for NAS on router: How to configure Address Reservation on a Deco
- Copy Link
- Report Inappropriate Content
@Alexandre. No issues with address reservation. DHCP works fine. The Synology remains inaccessible with either static or dynamic IP
- Copy Link
- Report Inappropriate Content
Hi, Thank you very much for the feedback.
I find an older thread about the main purpose of 2 LANs on the NAS discussion.
https://community.synology.com/enu/forum/17/post/112791
Since you have manually configured different IP addresses of these two ports, I think you might want to establish "a redundancy of connectivity". Or is there any specific reason for the following setup?
Is the 192.168.1.xxx/24 subnet used to be the IP subnet of the previous Untangle router (DHCP).
I wonder if we temporarily disconnect the LAN connection from port 2, are you able to ping and access NAS via 192.168.68.15?
Thank you very much and wait for your reply.
Best regards.
- Copy Link
- Report Inappropriate Content
@David-TP --
Thanks for the reply. :)
The current setup is just for debugging purposes. While the Deco does offer DHCP to the NAS, no communication between the devices has worked regardless of configuration after that initial handshake. Changing the NAS ports to static IP was just to remove variables from the equation in case it was some sort of DHCP parameter or configuration causing me grief. This one has me truly puzzled.
- Copy Link
- Report Inappropriate Content
Hi, thanks for getting back to me.
So the result was the same.
Whether the LAN 2 Ethernet cable is connected or not, the NAS is unreachable via 192.168.68.15 through the Deco network, right?
If yes, I would like to follow up on your case email and ask the senior engineers for further advice.
Wait for your reply and best regards.
- Copy Link
- Report Inappropriate Content
I had one last thought: I had docker running with Portainer with a MAC Vlan. I thought maybe Deco objected (even though I can't imagine why). I have since shut down Portainer to remove that from equation. Can't really remove Docker, but it is what it is. There are no other port consuming services running on the device.
At this point, as I have access, I can move the data to another machine or even cloud based storage, but would seriously like to understand why I cannot connect through Deco. Truly bizarre.
- Copy Link
- Report Inappropriate Content
@David-TP --
After bashing my head against the wall, I finally remembered that the Synology was firewalled to specific internal sub-nets as it was internet facing at one time. It came to light when I realized that the synology was able to reach the internet and so pointed to a block on the device itself. When I chased the firewall settings, I saw my blunder.
Thank you for your patience and for walking me through this.
Very much appreciate it.
Best Regards...
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 867
Replies: 7