port forwarding problems

[vriesm]

I'm not able to forward ports to my QNAP successfully. Port forwarding on my router works fine with all other devices in my house, except for the QNAP (TS-219P with 4.1.0). I checked with http://www.canyouseeme.org/ and it tells me that port 80 is closed if used with the QNAP. If i change in my router the ip address to another device with web server enabled on port 80, it is fine.

This means i cannot use the myQNAPcloud service. I used this service before with an UPNP enabled router. Lately I switched routers and now have one where the UPNP auto configuration gives errors on port 80 and 443. That is the reason I switched to forwarding ports.

To me it seems that the myQNAPcloud cannot be used without correct UPNP functionality. Can someone tell me the reason it only works with UPNP and not with forwarding ports? And forwarding ports to other devices works, except for the QNAP? Thanks in advance.

[Don]

Port forwarding works fine. Is your web server enabled on the QNAP and using port 80?


Sent from my iPad using Tapatalk HD

[vriesm]

Yes, it is. Locally my website is available on port 80. Only problem is that it seems that my router does not like my QNAP. It just won't forward any port to the QNAP. Other devices work fine for every port.

[schumaku]

On the myQNAPcloud.com AutomaticRouter config ...

Click "Rescan" to detect the router if no UPnP router is found on the local network and "Diagnostics" to check the diagnostic logs.

...click "Diagnostics" and copy/paste the output to the forum.

What router make/model/firmware?

[Don]

The router doesn't know or care what is at the other end. It will forward to whatever IP and port you tell it to. If you are using the correct IP and port it should work. Do you turn off UPNP when you forward manually?


Sent from my iPad using Tapatalk HD

[vriesm]

Yes, I do turn off UPNP. Tried different routers (TP-LINK (stock, gargoyle, etc), SiteCom (stock)), all with the same result. Can forward ports to other devices and it will work. Forwarding to the QNAP will fail always for every port.

Tried a router (TP-LINK) with UPNP working fine, at least in the router I can see ports are forwarded and the QNAP shows OK for every port. Still portchecks are failing and not possible to access QNAP remotely.

QNAP diagnostics shows errors:

------ NAT PMP Diagnostics ------
initnatpmp() returned 0 (SUCCESS)
using gateway : 192.168.0.1
sendpublicaddressrequest returned 2 (SUCCESS)
readnatpmpresponseorretry returned -7 (FAILED)
------ UPnP Diagnostics ------
upnpc : miniupnpc library test client. (c) 2006-2011 Thomas Bernard
Go to http://miniupnp.free.fr/ or http://miniupnp.tuxfamily.org/
for more information.
List of UPNP devices found on the network :
desc: http://192.168.0.1:1900/igd.xml
st: urn:schemas-upnp-org:device:InternetGatewayDevice:1

Found valid IGD : http://192.168.0.1:1900/ipc
Local LAN ip address : 192.168.0.107
Connection Type : IP_Routed
Status : Connected, uptime=0s, LastConnectionError : ERROR_NONE
Time started : Tue Jul 29 15:50:42 2014
MaxBitRateDown : 100000 bps MaxBitRateUp 100000 bps
ExternalIPAddress = XXX.XXX.XXX.XXX
0 TCP 8080->192.168.0.107:8080 'Web Admin' ''
1 TCP 443->192.168.0.107:443 'Secure Web Admin' ''
2 TCP 80->192.168.0.107:80 'Web Server/Multimedia Station' ''
3 TCP 8081->192.168.0.107:8081 'Secure Web Server' ''
GetGenericPortMappingEntry() returned 402 (Invalid Args)


Also myQNAPcloud shows a red cross. It says that all ports failed (80, 443, 8081, 8080).

If I disable myQNAPcloud and disable UPNP and just forward port 80 to the QNAP, I should get my website remotely?

[pwilson]

Yes, I do turn off UPNP. Tried different routers (TP-LINK (stock, gargoyle, etc), SiteCom (stock)), all with the same result. Can forward ports to other devices and it will work. Forwarding to the QNAP will fail always for every port.

Tried a router (TP-LINK) with UPNP working fine, at least in the router I can see ports are forwarded and the QNAP shows OK for every port. Still portchecks are failing and not possible to access QNAP remotely.

QNAP diagnostics shows errors:

------ NAT PMP Diagnostics ------
initnatpmp() returned 0 (SUCCESS)
using gateway : 192.168.0.1
sendpublicaddressrequest returned 2 (SUCCESS)
readnatpmpresponseorretry returned -7 (FAILED)
------ UPnP Diagnostics ------
upnpc : miniupnpc library test client. (c) 2006-2011 Thomas Bernard
Go to http://miniupnp.free.fr/ or http://miniupnp.tuxfamily.org/
for more information.
List of UPNP devices found on the network :
desc: http://192.168.0.1:1900/igd.xml
st: urn:schemas-upnp-org:device:InternetGatewayDevice:1

Found valid IGD : http://192.168.0.1:1900/ipc
Local LAN ip address : 192.168.0.107
Connection Type : IP_Routed
Status : Connected, uptime=0s, LastConnectionError : ERROR_NONE
Time started : Tue Jul 29 15:50:42 2014
MaxBitRateDown : 100000 bps MaxBitRateUp 100000 bps
ExternalIPAddress = XXX.XXX.XXX.XXX
0 TCP 8080->192.168.0.107:8080 'Web Admin' ''
1 TCP 443->192.168.0.107:443 'Secure Web Admin' ''
2 TCP 80->192.168.0.107:80 'Web Server/Multimedia Station' ''
3 TCP 8081->192.168.0.107:8081 'Secure Web Server' ''
GetGenericPortMappingEntry() returned 402 (Invalid Args)


Also myQNAPcloud shows a red cross. It says that all ports failed (80, 443, 8081, 8080).

If I disable myQNAPcloud and disable UPNP and just forward port 80 to the QNAP, I should get my website remotely?

When I hit your external IP address on Port 80 I got:



(I have since obscured your external IP address in your last message, to protect you from Spammers/Hackers. You should never post your external IP address to public Forums).

[vriesm]

Sorry for that. I should have known that. But what you see was my Windows Machine. It proves that port forwarding is working for my Windows Machine. However, the same trick does not work for my QNAP.

I disabled myQNAPcloud, disabled UPNP and only enabled my web server currently. In my local network I can access my web server via port 80, but it is still not working remotely, despite of the port forwarding in my router to the QNAP and accessing it remotely via IP address.

I'm out of options to solve this problem. Is it possible to do a re-flash of the QNAP, and resetting everything to factory? I'm pretty sure the QNAP is the problem in this case. Maybe the RFS is damaged by some recent powers failures in my house... Yesterday after a reboot it told me via the web interface that no disks were detected? Today it is working again, making a backup of my data now.

Btw, if I enable CloudLink I can access the QNAP via the mobile apps, so it has internet connection.

[pwilson]

Sorry for that. I should have known that. But what you see was my Windows Machine. It proves that port forwarding is working for my Windows Machine. However, the same trick does not work for my QNAP.

I disabled myQNAPcloud, disabled UPNP and only enabled my web server currently. In my local network I can access my web server via port 80, but it is still not working remotely, despite of the port forwarding in my router to the QNAP and accessing it remotely via IP address.

I'm out of options to solve this problem. Is it possible to do a re-flash of the QNAP, and resetting everything to factory? I'm pretty sure the QNAP is the problem in this case. Maybe the RFS is damaged by some recent powers failures in my house... Yesterday after a reboot it told me via the web interface that no disks were detected? Today it is working again, making a backup of my data now.

Btw, if I enable CloudLink I can access the QNAP via the mobile apps, so it has internet connection.

If you can access your WebServer locally, then this is not a NAS issue at all. Check your undisclosed Router documentation and test to ensure that your undisclosed Router is in fact forwarding Port 80/TCP to 192.168.0.107:80/TCP. Get someone from "outside" your network to test it for you. (If your undisclosed Router doesn't support NAT-Loopback, (which most consumer Routers don't), you will only be able to access it remotely from your network on the external IP address.

I can't comment on CloudLink etc, as I only use the DDNS capabilities of the MyQNAPCloud Service here. I personally leave UPnP-IGN disabled on my Router, as I view UPnP-IGN as a security hole the size of Boeng 747 aircraft. I prefer to use manual port-forwarding at my Router for everything. (I do not want Viruses/Spam/Malware to be able to setup Port-Forwarding within my Router without my knowledge or consent, and without any form of security credentials provided. I am pretty good at avoiding Virus etc here, but my kids and girlfriend aren't so lucky, as they don't practice safe computing practices very well).

[schumaku]

Has the Windows machine free-ed up the port 80/TCP forwarding? Mind you the same port can be used only by one forward...

[vriesm]

Finally solved my problem. The reason that port forwarding was failing to the QNAP was because of the fact I blocked everything not coming form the LAN in security settings. My previous router routed all traffic with a local IP address to the QNAP, so this was working. With the new router the WAN ip address is used and now it works also fine again

[schumaku]

Great! Routers showing the source of an Internet connection being a LAN IP (or the router WAN IP) instead of the real originating IP address .... tsk tsk tsk... clear mistake in the router NAT configuration

[bill.couper]

@schumaku, I don't think you understand. The problem was not vriesm's router making a mistake.

I also had this same error and google brought me here.
Sure enough, when I look in the QNAP under "System Settings -> Security" it is restricting access to the router from the local LAN only.
So anything with a source address of 'the internet' was not being accepted by the NAS.
I probably turned that on the first day I plugged in the NAS, thinking it sounded like a good idea at the time. Hindsight is always 20/20.

@vriesm thanks for sharing your answer

[tiagondelgado]

Someone can help?

i have TPlink archer2600 and already try open ports. After that, qnap says 443 and 8081 are open and 80 and 8080 are close.

I check canyouseeme.org and 80 are close and 8080 are open. I dont understand:

1- Why 80 dont open?
2- why 8080 says close bur canyouseeme says opened.


Diagnostics

------ NAT PMP Diagnostics ------
initnatpmp() returned 0 (SUCCESS)
using gateway : 192.168.0.1
sendpublicaddressrequest returned 2 (SUCCESS)
readnatpmpresponseorretry returned 0 (OK)
Public IP address : 81.193.33.143
epoch = 74563785
closenatpmp() returned 0 (SUCCESS)
------ UPnP Diagnostics ------
upnpc : miniupnpc library test client. (c) 2006-2011 Thomas Bernard
Go to http://miniupnp.free.fr/ or http://miniupnp.tuxfamily.org/
for more information.
List of UPNP devices found on the network :
desc: http://192.168.0.1:1900/rootDesc.xml
st: urn:schemas-upnp-org:device:InternetGatewayDevice:1

Found valid IGD : http://192.168.0.1:1900/ctl/IPConn
Local LAN ip address : 192.168.0.143
Connection Type : IP_Routed
Status : Connected, uptime=74563787s, LastConnectionError : ERROR_NONE
Time started : Thu Jan 1 00:00:10 2015
MaxBitRateDown : 8388608 bps MaxBitRateUp 4194304 bps
ExternalIPAddress = 81.193.33.143
0 TCP 17166->192.168.0.143:32400 'Plex Media Server' ''
1 UDP 4521->192.168.0.120:4500 'NAT-PMP 4521 udp' ''
2 UDP 5374->192.168.0.120:5353 'NAT-PMP 5374 udp' ''
3 TCP 8080->192.168.0.143:8080 '0ee53e8ce4740f9bd2e16ead0af8d2b8-Web Admin' ''
4 TCP 8081->192.168.0.143:8081 '0ee53e8ce4740f9bd2e16ead0af8d2b8-Secure Web Serve' ''
5 TCP 6889->192.168.0.143:6889 'NAT-PMP 6889 tcp' ''
6 TCP 4433->192.168.0.143:4433 'NAT-PMP 4433 tcp' ''
7 UDP 6889->192.168.0.143:6889 'NAT-PMP 6889 udp' ''
8 TCP 6942->192.168.0.120:6942 'NAT-PMP 6942 tcp' ''
GetGenericPortMappingEntry() returned 713 (SpecifiedArrayIndexInvalid)


Screens

[schumaku]

Appears you mix (and overload) the router config with both UPnP PNP as well as with static port forwardings (in "Virtual Server"). Strongly suggest to avoid - to start with, I would suggest to use the statically configured pot forwardings, and disable the services/ports on the NAS Automatic Router Configuration.

80/TCP looks correctly forwarded to the NAS LAN IP address static port forwardings (in "Virtual Server").

8081/TCP is duplicated forwarded static and by UPnP.

443/TCP is manually forwarded in "Virtual Server".

Hard to say what can be blocking - the ISP might not allow using 80/TCP or the router does make use of 80 and/or 8081/TCP for it's own usage.

Curious if the Web Server service is enabled and configured for 80/TCP resp. 8081/TCP.

Any dedicated firewall rules to be configured?

@schumaku, I don't think you understand. The problem was not vriesm's router making a mistake.

Of course I do - my srcasm was pointing to a NAT issue on @vriesm previous router...