can't connect from outside local network

[jharreman]

Built a website at work that is supposed to run on our QNAP NAS, on the local network everything runs fune, but we can't connect to the outside world. I have no access to our (cisco) router, but our IT-guy says port 80 is open/forwarded correctly so the problem should be in our NAS settings. Unfortunately he doesn't know anything about those... Any suggestions?


------ UPnP Diagnostics ------
List of UPNP devices found on the network :
desc: http://10.104.9.108:49153/gatedesc.xml
st: upnp:rootdevice

UPnP device found. Is it an IGD ? : http://10.104.9.108:49153/
Trying to continue anyway
Local LAN ip address : 10.104.9.108
GetConnectionTypeInfo failed.
Status : , uptime=3214139232s, LastConnectionError :
Time started : Mon Jun 27 21:28:55 1910
MaxBitRateDown : 6 bps MaxBitRateUp 0 bps
GetExternalIPAddress() returned -3
GetExternalIPAddress failed.
Bytes: Sent: 4294967293 Recv: 4294967293
Packets: Sent: 4294967293 Recv: 4294967293

------ NAT PMP Diagnostics ------
initnatpmp() returned 0 (SUCCESS)
using gateway : 10.104.9.254
sendpublicaddressrequest returned 2 (SUCCESS)
readnatpmpresponseorretry returned -7 (FAILED)

[schumaku]

Can the NAS reach the Internet at all? Check if the default gateway is selected to be the interface connected to the TCP/IP subnetwork with the Internet router...

I assume your IT-guy is talking on a manually forwarded port - your router does not seem to be compatible to the Automatic Router Configuration by UPnP.

[jharreman]

I dont think it connects to the internet at all. is there another way to check this than just looking if the RSS-feeds show up? (they don't)

[schumaku]

In general, an appropriate network config simply works. Start with a login to the NAS'Linux shell. Check

[~]# ping www.google.com
...
[~]# traceroute www.google.com
...

As well, post the output of

[~]# ifconfig
...
[~]# route
...
[~]# cat /etc/resolv.conf
...

[jharreman]

Start with a login to the NAS'Linux shell.


How do I do that?

[schumaku]

Sorry, as you mentioned you have an IT-guy there I asumed he can give you a hand...

First ensure the ssh is enabled on your NAS (Home >> Network Services >> Telnet/SSH).

On OS X, open the Terminal app, and do
$ ssh admin@[NAS-IP-address]
_Password: .....

On Windows, grab and install PuTTY, create a new ssh connection, and login as admin.

Both will lead you to the NAS Linux shell prompt# (with the current directory in sharp barckets [~]), ready to enter the commands:

[~] #

[jharreman]

ping.jpg

[jharreman]

ifconfig.jpg

rioute.jpg

cat etc.jpg

traceroute1.jpg

[schumaku]

So the NAS is able to reach the Intenet - and the packets are finding te way back. Excellent.

Intentionally connected both interfaces to two different LANs? One seems tho have Internet access (the 192.168.11.x), while the NAS detects an UPnP router on the 10.104.9.x network. Only _one_ can work.

Just copy-paste the text would be much better to read. Vaguely recognize the tracroute does go out to the 192.168.11.xx network - as that one is configured to be the defautl gateway.

Now, either you configure the incoming traffic over the router with the 192.168.11.1 LAN IP, and do the port forwarding to the 192.168.11.34, or you re-configure the default gateway to the other intrface, and do the portforwarding on the other with the 10.104.9, to the 10.104.9.108.x (i any at all...the impression comes up you "see" the NAS itself there.

[jharreman]

I give up, the interface is just too complicated for me. I'll stick to doing the fancy stuff on my Synology DS and use this one just as a data backup.

[schumaku]

Well - do you have the same common ports also forwarded to another NAS?