Hi, I've correctly set up the myQnapCloud service, and the nas control panel seems all right. The domain xxx.myqnapcloud.com works in LAN, but doesn't work in WAN.
Where should be the problem?
Thanks in advance to everyone!
---------
Lorenzo
http://www.lorenzobarbagli.net
cannot access my nas from remote
-
- New here
- Posts: 3
- Joined: Thu Jun 05, 2014 3:39 am
- Location: Milan
- Contact:
cannot access my nas from remote
Last edited by lorebarba on Thu Jun 05, 2014 3:14 pm, edited 1 time in total.
- pwilson
- Guru
- Posts: 22533
- Joined: Fri Mar 06, 2009 11:20 am
- Location: Victoria, BC, Canada (UTC-08:00)
Re: cannot access my nas from remote
First off, I would strongly recommend editing your original message to remove your FQDN (Fully Qualified Domain Name) from your original message. Publishing this information to a Public forum is a bad idea, as it is an invitation to Hackers/Spammers to attack you.lorebarba wrote:Hi, I've correctly set up the myQnapCloud service, and the nas control panel seems all right. The domain http://XxXxXxXxXxXxX.myqnapcloud.com/ works in LAN, but doesn't work in WAN.
Where should be the problem?
Thanks in advance to everyone!
---------
Lorenzo
http://www.lorenzobarbagli.net
Your "myqnapcloud.com" address is successfully found via "nslookup XxXxXxXxXxXxX.myqnapcloud.com":
Code: Select all
nslookup XxXxXxXxXxXxX.myqnapcloud.com
Server: 10.77.13.1
Address: 10.77.13.1#53
Non-authoritative answer:
Name: XxXxXxXxXxXxX.myqnapcloud.com
Address: NN.NN.NNN.NNN
You can use this command from the command line of any operating system. (Works from Windows, OS X, Linux & Android).
This suggests that your "MyQNAPCloud" configuration (DDNS) entry is correct. It shows an Italian IP address.
My guess is that your Port-Forwarding is not setup correctly in your Router. You can test this with the CanYouSeeMe.org - Open Port Check Tool.
Simply test the ports normally used to access your NAS. If using standard ports you will probably want to check 22, 80, 433, 8080, and 8081.
You should probably check your "Auto Router Configuration" under MyQNAPCloud in the control panel:
Click on the Diagnostics button.
Note: Despite what this screen capture says my Router does actually support UPnP-IGN. I have it deliberately disabled, as I believe UPnP-IGN is a Security issue. I do not want software running on devices inside my network being able to setup "Port-Forwards" in my Router. (My kids and girlfriend do not have safe practices re: viruses/malware). As I have this Router feature deliberately disabled, I have to manually setup all Port-Forwarding in my Router.
Consult this chart if you need to setup your Port-Forwarding manually:
Do not forward 13131, as Telnet is insecure (plaintext passwords), so it should not be used outside your network, and preferably not used inside it either.
Patrick M. Wilson
Victoria, BC Canada
QNAP TS-470 Pro w/ 4 * Western Digital WD30EFRX WD Reds (RAID5) - - Single 8.1TB Storage Pool FW: QTS 4.2.0 Build 20151023 - Kali Linux v1.06 (64bit)
Forums: View My Profile - Search My Posts - View My Photo - View My Location - Top Community Posters
QNAP: Turbo NAS User Manual - QNAP Wiki - QNAP Tutorials - QNAP FAQs
Please review: When you're asking a question, please include the following.
-
- New here
- Posts: 3
- Joined: Thu Jun 05, 2014 3:39 am
- Location: Milan
- Contact:
Re: cannot access my nas from remote
Thank you very much for your answer. I put there the domain name because a thought it would be easier for you to diagnostic the problem, now I've removed it.
I've used auto port router configuration and it seemed all right, but probably there's something in my router that didn't work, it's a fastweb router/hub so it's very closed and difficult to manage.
I'll try later to forward the ports manually
---------
Lorenzo
http://www.lorenzobarbagli.net/
I've used auto port router configuration and it seemed all right, but probably there's something in my router that didn't work, it's a fastweb router/hub so it's very closed and difficult to manage.
I'll try later to forward the ports manually
---------
Lorenzo
http://www.lorenzobarbagli.net/
- pwilson
- Guru
- Posts: 22533
- Joined: Fri Mar 06, 2009 11:20 am
- Location: Victoria, BC, Canada (UTC-08:00)
Re: cannot access my nas from remote
You can test this with the CanYouSeeMe.org - Open Port Check Tool. Seriously, it's a free tool. Use it to test your Port Forwarding.lorebarba wrote:Thank you very much for your answer. I put there the domain name because a thought it would be easier for you to diagnostic the problem, now I've removed it.
I've used auto port router configuration and it seemed all right, but probably there's something in my router that didn't work, it's a fastweb router/hub so it's very closed and difficult to manage.
I'll try later to forward the ports manually
Patrick M. Wilson
Victoria, BC Canada
QNAP TS-470 Pro w/ 4 * Western Digital WD30EFRX WD Reds (RAID5) - - Single 8.1TB Storage Pool FW: QTS 4.2.0 Build 20151023 - Kali Linux v1.06 (64bit)
Forums: View My Profile - Search My Posts - View My Photo - View My Location - Top Community Posters
QNAP: Turbo NAS User Manual - QNAP Wiki - QNAP Tutorials - QNAP FAQs
Please review: When you're asking a question, please include the following.
-
- New here
- Posts: 3
- Joined: Thu Jun 05, 2014 3:39 am
- Location: Milan
- Contact:
Re: cannot access my nas from remote
Hi, I've tried again but it doesn't work. I've opened ports number 8080, 80, 22 and 21, I want to use it remotely with the web file manager.
The diagnostic in NAS control panel says this:
EDIT: canyouseeme.org service reports a connection timeout with 8080 port, but this is probably because I can forward the ports only for a device attached, not for the whole router.
The diagnostic in NAS control panel says this:
Code: Select all
------ NAT PMP Diagnostics ------
initnatpmp() returned 0 (SUCCESS)
using gateway : 192.168.1.254
sendpublicaddressrequest returned 2 (SUCCESS)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
readnatpmpresponseorretry returned -100 (TRY AGAIN)
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.1.254:8000/4g878tidbxh/IGD/upnp/IGD.xml
st: urn:schemas-upnp-org:device:InternetGatewayDevice:1
Found valid IGD : http://192.168.1.254:8000/4g878tidbxh/IGD/upnp/control/igd/wanipc_1_1_1
Local LAN ip address : 192.168.1.65
Connection Type : IP_Routed
Status : Connected, uptime=457900s, LastConnectionError : ERROR_NONE
Time started : Sat May 31 14:20:35 2014
MaxBitRateDown : 20068000 bps MaxBitRateUp 1221000 bps
ExternalIPAddress = 10.17.207.68
0 UDP 42044->192.168.1.68:42044 'Skype UDP at 192.168.1.68:42044 (2700)' ''
1 TCP 42044->192.168.1.68:42044 'Skype TCP at 192.168.1.68:42044 (2700)' ''
2 TCP 56188->192.168.1.81:56188 'uTorrent (TCP)' ''
3 UDP 56188->192.168.1.81:56188 'uTorrent (UDP)' ''
4 UDP 56547->192.168.1.84:56547 'Teredo' ''
5 UDP 42045->192.168.1.78:42044 'Skype UDP at 192.168.1.78:42044 (2705)' ''
6 UDP 57074->192.168.1.80:57074 'Teredo' ''
7 UDP 50526->192.168.1.82:50526 'Teredo' ''
8 TCP 23159->192.168.1.92:23159 'uTorrent (TCP)' ''
9 UDP 23159->192.168.1.92:23159 'uTorrent (UDP)' ''
10 UDP 55371->192.168.1.64:55371 'Skype UDP at 192.168.1.64:55371 (2709)' ''
11 TCP 55371->192.168.1.64:55371 'Skype TCP at 192.168.1.64:55371 (2709)' ''
12 TCP 23160->192.168.1.93:23159 'uTorrent (TCP)' ''
13 UDP 23160->192.168.1.93:23159 'uTorrent (UDP)' ''
14 TCP 8080->192.168.1.65:8080 'Web Admin' ''
15 TCP 443->192.168.1.65:443 'Secure Web Admin' ''
16 TCP 20->192.168.1.65:20 'FTP/FTPS' ''
17 TCP 21->192.168.1.65:21 'FTP/FTPS' ''
18 TCP 13131->192.168.1.65:13131 'Telnet Server' ''
19 TCP 22->192.168.1.65:22 'SSH/SFTP' ''
20 TCP 80->192.168.1.65:80 'Web Server/Multimedia Station' ''
21 TCP 8081->192.168.1.65:8081 'Secure Web Server' ''
22 TCP 873->192.168.1.65:873 'Remote Replication' ''
23 TCP 8899->192.168.1.65:8899 'Remote Replication' ''
24 TCP 1723->192.168.1.65:1723 'PPTP' ''
25 UDP 1194->192.168.1.65:1194 'Open VPN' ''
GetGenericPortMappingEntry() returned 501 (Action Failed)
- pwilson
- Guru
- Posts: 22533
- Joined: Fri Mar 06, 2009 11:20 am
- Location: Victoria, BC, Canada (UTC-08:00)
Re: cannot access my nas from remote
This output suggests a less than UPnP-IGN-compliant Router. Use manual Port-Forwarding instead. (It's far safer anyway ).lorebarba wrote:Hi, I've tried again but it doesn't work. I've opened ports number 8080, 80, 22 and 21, I want to use it remotely with the web file manager.
The diagnostic in NAS control panel says this:
EDIT: canyouseeme.org service reports a connection timeout with 8080 port, but this is probably because I can forward the ports only for a device attached, not for the whole router.Code: Select all
------ NAT PMP Diagnostics ------ initnatpmp() returned 0 (SUCCESS) using gateway : 192.168.1.254 sendpublicaddressrequest returned 2 (SUCCESS) readnatpmpresponseorretry returned -100 (TRY AGAIN) readnatpmpresponseorretry returned -100 (TRY AGAIN) readnatpmpresponseorretry returned -7 (FAILED)
Patrick M. Wilson
Victoria, BC Canada
QNAP TS-470 Pro w/ 4 * Western Digital WD30EFRX WD Reds (RAID5) - - Single 8.1TB Storage Pool FW: QTS 4.2.0 Build 20151023 - Kali Linux v1.06 (64bit)
Forums: View My Profile - Search My Posts - View My Photo - View My Location - Top Community Posters
QNAP: Turbo NAS User Manual - QNAP Wiki - QNAP Tutorials - QNAP FAQs
Please review: When you're asking a question, please include the following.
-
- New here
- Posts: 5
- Joined: Sun Feb 09, 2014 6:12 pm
Re: cannot access my nas from remote
I want to access folders shared in File Station thru a browser and it has been a frustrating experience.
I have a 212p running fw 4.1. I'm using ie11 on win 8.1 with a single port.
1. Upnp is now turned off and Manual port forwarding is set up on my router with 8080, 80, 445 and 445 all directed to my qnap's internal lan ip address.
2. Corresponding firewall rules give these ports wan to lan access to all ips. Lan to wan defaults to permit all ports.(btw, I also tested by turning off my router's firewall and it made no difference)
3. Myqnapcloud ddns is turned on but does not test correctly - it spins endlessly
4. I can access a shared folder from my lan using http://xxxxx.myqnapcloud.com:8080/share.cgi?ssid=xxxx but cannot get to this URL when accessing from another connection (e.g a coffee shop)
5. I can ping my wan ip address.
6. The canyouseeme port check tool appears to find 80, 8080 and other forwarded ports on my Wan ip address but times out.
Arrgghh!!! Any thoughts??
Btw, thanks for your earlier tip to disable remote mgmt of my router. It was hogging port 8080 and I could therefore not manually forward 8080 to the qnap.
I have a 212p running fw 4.1. I'm using ie11 on win 8.1 with a single port.
1. Upnp is now turned off and Manual port forwarding is set up on my router with 8080, 80, 445 and 445 all directed to my qnap's internal lan ip address.
2. Corresponding firewall rules give these ports wan to lan access to all ips. Lan to wan defaults to permit all ports.(btw, I also tested by turning off my router's firewall and it made no difference)
3. Myqnapcloud ddns is turned on but does not test correctly - it spins endlessly
4. I can access a shared folder from my lan using http://xxxxx.myqnapcloud.com:8080/share.cgi?ssid=xxxx but cannot get to this URL when accessing from another connection (e.g a coffee shop)
5. I can ping my wan ip address.
6. The canyouseeme port check tool appears to find 80, 8080 and other forwarded ports on my Wan ip address but times out.
Arrgghh!!! Any thoughts??
Btw, thanks for your earlier tip to disable remote mgmt of my router. It was hogging port 8080 and I could therefore not manually forward 8080 to the qnap.
- schumaku
- Guru
- Posts: 43578
- Joined: Mon Jan 21, 2008 4:41 pm
- Location: Kloten (Zurich), Switzerland -- Skype: schumaku
- Contact:
Re: cannot access my nas from remote
With 8080/TCP resp. 443/TCP forwarded you should be able to reach the QTS Web UI on http://xxxxx.myqnapcloud.com:8080/ resp. https://xxxxx.myqnapcloud.com/
If this does not work, double check the port forwarding, double check no router services are occupying these service ports (several vendor products are reporting UPnP IGD config success!), and last but not least check if your ISP does not block the common ports used for Web services. Some crazy ISP started to block these ports to avoid their customer routers (CPE) because many have never changed the password to the "formal" reason was to protect customer security, but this has changed to a business model to sell "business" class internet connections with less restrictions.
If this does not work, double check the port forwarding, double check no router services are occupying these service ports (several vendor products are reporting UPnP IGD config success!), and last but not least check if your ISP does not block the common ports used for Web services. Some crazy ISP started to block these ports to avoid their customer routers (CPE) because many have never changed the password to the "formal" reason was to protect customer security, but this has changed to a business model to sell "business" class internet connections with less restrictions.