ConnectTimeoutException on TP-Link Router

[tkpeters]

Hi!

So I've got Subsonic up and running on my LAN, but I can't access it remotely. As far as I can tell the ports are forwarding correctly (I've done it automatically and messed with setting up virtual servers), and I've tried several different ports.

However, I cannot get remote access to work, either through the custom URL or through my IP. Every time I get the connecttimeoutexeception error.

Last night, though, I was at a friend's house and I tried it on their network using their Netgear router and it worked perfectly the first try. I confirmed with my phone over data instead of wi-fi, and remote access was working perfectly. So, it would appear that the issue is at my router level, even if, to my eyes, everything is a go on my home router re: port forwarding and so on.

Anyone know of specific issues with TP-Link routers that would be causing hiccups?

[tkpeters]

Update to my issue: it's come to my attention that my issue might actually be that there are two routers on my network. The TP-Link I've been messing with, and the one in my modem provided to me by my ISP (Brighthouse). It would appear that the ports are forwarded correctly through my TP-Link, but that I may still need to forward the ports through my modem. Any advice on how to achieve that?

I've seen a few things about creating a DMZ but I'm unsure how that will impact my network security.

Thanks!

[alphawave7]

If you can pass the port test at canyousee.org for your chosen port, you are good to go for remote access. If the server Addy does not work locally, that is a router issue with DNS to LAN. I solve that with another server entry (eg. 'Home') on its own LAN Addy (eg. 10.0.0.4:4040). 'Away' server is my custom name, used when I am...away.

Sent from my Nexus 6 using Tapatalk