What's new

mapping synology 211 in windows

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Tekniqueman

New Around Here
my 211+ is behind the Netgear FVS336GV2 and I try to access the folders from the internet.
I have open the ports 80, 445, 137-139, 5000, 5005, both in firewall and in dmz.
I have success with login to the DSM, port 80 automatically get redirected to port 5000. I have success with mapping a internet folder (http://xxx.xxx.xxx.xxx:5005/) on an XP pc. but on a win7 home edition 64 bit it fails :( anyone that can tell me why?
what I want is to map the NAS's folders as ordinary network folder. I can map the 211 folders when I'm on the local network with no problem.
when I test port 137-139, in the same LAN as the 211, in canyouseeme.org it says they are refused?
 
PC firewall on? If off, need to give port exceptions to firewall?

Home router have port forwarding for each port to the static IP of the NAS?

Internet service provider may block ports - AT&T is notoriously bad for this.

(NAS UPnP may do some but not all router config changes - but UPnP may be disabled in router and/or NAS, or doesn't work properly)
 
Last edited:
Stevech:

The PCs are on the same LAN, so I think I have to look at win7's settings because even with the firewall down it doesn't matter, still no go :(
 
OK. Intra-LAN

when you try
http://xxx.xxx.xxx.xxx:5005

Some routers will require than the x's be the LAN address (e.g., 192.168.1.x) rather than the public IP address.
That is, a laptop using your LAN/WiFi would use the LAN address and that same laptop, when accessing from another network, would use your dyndns type public address.

Port forwarding is n/a for intra-LAN.

PC's windows firewall - off, as I read what you said.
 
more testing

OK. Intra-LAN

when you try
http://xxx.xxx.xxx.xxx:5005

Some routers will require than the x's be the LAN address (e.g., 192.168.1.x) rather than the public IP address.
That is, a laptop using your LAN/WiFi would use the LAN address and that same laptop, when accessing from another network, would use your dyndns type public address.

Port forwarding is n/a for intra-LAN.

PC's windows firewall - off, as I read what you said.

Found out that it's the ISP (Internet Service Provider) that is the problem. with an address as \\80.xxx.xxx.xxx\folder it works as a dream,
I have attached a lan folder with an external address and that's work fine with that ISP. if I try with \\89.xxx.xxx.xxx\folder which is a different ISP it doesn't work.
My conclusion is that on the same Pc, with the same model Synology NAS with the same ports open in the 2 different routers, on 2 different ISP's wan, it must be the ISP that is blocking some port.
 

Similar threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top