DIR-859 router can't find nearby public IP addresses

Skidborg

Commendable
Dec 6, 2016
1
0
1,510
So I'm setting up a file server for a summer camp. Server box (Synology DS216+II NAS) is in the main office at the top of the hill, behind a static public IP address (XXX.XXX.XXX.164). Works fine with internal network connections and most external ones around town. Firewall is autoblocking login attempts from Malaysia. Good times.

Down the hill is the main lodge where I have several computers that should back up to the office file server. The devices are behind a DIR-859 router and a separate cable internet connection (SB5120 cable modem) from the office. However, its public dynamic IP address is from the same ISP and WAN (XXX.XXX.XXX.166).

Now the problem:
Connecting via any other location/connection CAN ping and connect to my remote file server.
Plugging my laptop directly into the lodge cable modem CAN ping and connect to my remote file server.
Plugging my laptop into the DIR-859 router which is plugged into the cable modem CANNOT ping or connect to my file server but CAN ping and connect to other sftp servers across the web.

So the problem appears to be specific to the router, and specific to IP addresses which are nearby. What settings or further debug information should I be looking at to fix this?