Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[flasher]

Hello,
recently I bought Synology NAS and I'm trying to make it available from outside of my network. First of all I let Synology to configure my router automatically. All ports used by Synology are accessible from the Internet except ports 80 and 443. When using NMAP, all used ports are marked as "open" while 80 and 443 are marked as "filtered". So I disabled UPnP on the router and tried to configured the forwarding rules manually (tried both Virtual Server and Port Forwarding). The result is the same, 80 and 443 not available, others working fine.

Afterwards I contacted my ISP to ask whether these ports are blocked in their side - answer is no.

I alsi tried to check these ports on the Synology directly in my internal network and both ports are open on the device. So my assumption is that the port forwarding for these 2 ports does not work for some reason. Very strange is that I have an issue just with these 2 ports.

I tried to change configuration which might affect blocking of those ports (I have no application rules, no QoS engine enabled, no network filter, no access control, no IPv6, ...), but no success. Adding the Synology to DMZ has also no effect, 80 and 443 not visible there using NMAP, other ports are fine.

So conclusion is: I'm sure that both ports are open and available within my internal network on the Synology, but from outside (Internet), these ports are not forwarded.

I use D-Link DIR-868L with FW 1.09 and HW version A1.

Do you have any ideas what might be wrong?  I'm really out of options.

Thanks!

[FurryNutz]

Link>Welcome!

• What region are you located?

Router and Wired Configurations

• Turn on or off DNS Relay under Setup/Networking. Link>Finding Faster DNS Addresses using Name Bench and input new DNS addresses under Setup/Internet/Manual.
• Setup DHCP reserved IP addresses for all devices ON the router. Setup/Networking. This ensures each devices gets its own IP address when turned on and connected, eliminates IP address conflicts and helps in troubleshooting and maintain consistency for applications that need to connect as well as mapped drives.
• Ensure devices are set to auto obtain an IP address.
• If IPv6 is an option on the router, select Local Connection Only under Setup/IPv6.
• Set Firewall settings to Endpoint Independent for TCP and UDP under Advanced/Firewall. Enable or Disable SPI to test.
• Enable uPnP and Multi-cast Streaming under Advanced/Networking. Disable uPnP for testing Port Forwarding rules.

Please post a picture of your Port Forwarding configuration:
Adding Screenshots In A Post

[flasher]

I'm located in Europe (Czech Republic).

DNS Relay - no effect
Reserved IP addresses - done, no effect
All devices set to obtain an IP address - done, no effect
IPv6 Local Connection Only set - no effect
Firewall settings to Endpoint Independent - no such option in the configuration page
SPI enabled / disabled - no effect
uPnP and Multi-cast Streaming enabled / disabled - no effect

I tried to set the forwarding rules via uPnP and also manually with uPnP disabled but the result is the same.

192.168.0.101 is reserved address for my Synology



Is there any way how to find out which rules were set by uPnP?

[FurryNutz]

Try using a different private port number, like 50117? I believe that with using Virtual Server, uPnP should be enabled and use a virtual port number that isn't the same as the public port number...

Is the 868L getting a public IP address on the WAN port? ##.##.###.###

Might try v1.10 update as well...

[flasher]

Using different private port number does not work either, the 80 an 443 are simply not accessible from outside. The forwarding works for other ports so I don't think this is general forwarding problem.

Yes, I have public IP on WAN interface.

Isn't the port blocked by the router administration UI for some strange reason? It also runs on port 80 (and optionally 443 with HTTPS), rigth?

Where can I find the v1.10 update?

Thanks

[FurryNutz]

Check with your regional D-Link support site. I believe it's there. If it still fails, then there maybe a FW issue and I would recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. We find that phone contact has better immediate results over using email.
Let us know how it goes please.

[FurryNutz]

Any status on this? 

Using different private port number does not work either, the 80 an 443 are simply not accessible from outside. The forwarding works for other ports so I don't think this is general forwarding problem.

Yes, I have public IP on WAN interface.

Isn't the port blocked by the router administration UI for some strange reason? It also runs on port 80 (and optionally 443 with HTTPS), rigth?

Where can I find the v1.10 update?

Thanks

[cagemaster]

I have the exact same issue. The ports 80/443 just won't forward. Please advice.

DIR-842   HW:B1   FW:2.02

[cagemaster]

I resolved the issue. Instead of port forwarding, I used the virtual server feature. I choose HTTP and HTTPS and the ports 80/443 auto-filled. Now I'm running my web server through port 80.

Too bad this is not advertised properly. Seems like only port forwarding (port 80) doesn't work since the router web server is running through that port.

[FurryNutz]

Thanks for letting us know. Glad you got it working. Yes Virtual Server is a good feature of this model router and should be used over using PF configurations.

Also if you use any PF configurations, you have to disable uPnP first.

Enjoy.

I resolved the issue. Instead of port forwarding, I used the virtual server feature. I choose HTTP and HTTPS and the ports 80/443 auto-filled. Now I'm running my web server through port 80.

Too bad this is not advertised properly. Seems like only port forwarding (port 80) doesn't work since the router web server is running through that port.