Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Results 1 to 4 of 4
  1. #1

    Question Forwarded ports not accessible over the internet on TD-W8960N

    Model :

    Hardware Version :

    Firmware Version :

    ISP : [/COLOR]

    Hello everyone,

    I have two routers, A and B (TL-WR841N). A is where my ADSL is configured and B is bridged to A, repeating its wireless signal. I have a NAS connected to B via ethernet with DDNS setup so I can access some NAS apps on the go. After forwarding the ports on A I was able to access my NAS apps on the go from anywhere thanks to DDNS but I replaced my old router A with a TD-W8960N and even though both routers in my setup are tplink now port forwarding is not working as it should. I have setup virtual servers under nat for all the ports I need but for some reason I'm not able to see the apps outside of my local network. The weird thing is that 'service' ports for skype, bt, etc are being forwarded as expected some even automatically thanks to UPnP but I'm not able to connect to the app themselves from the internet. Not even the SSH ports are shown. When I go to my ddns url it seems that a barebone router UI is shown (http://i.imgur.com/RSVuobW.png) asking me to log in but once I enter my credentials it shows a lot of unavailable resources instead of the admin UI (http://i.imgur.com/3SNQC9A.png). It seems the router is not sending any kind of app data over the net but I don't know why if I'm forwarding the ports correctly. What is the problem? Any help would be appreciated.

  2. #2
    Interesting, it seems that the port forwarding does work from outside my network using the ddns url but not while I'm inside of it (this does work using the local net addresses though). If I try to access the forwarded ports from my phone's internet service using the ddns url I do get the expected response but that isn't the case from inside my network, inside my network I have to use the local address. This didn't use to be the case with the old router, what could be the issue?

  3. #3
    Hi

    Today I faced exactly the very same issue here, I configured the virtual service (into NAT menu) to map the external 1234 port to the 22 port of an machine which is inside my network and I couldn't connect to it. I try both the ddns address and the IP which this ddns resolves to, It didn't work. I will try reconfigure It tomorrow and try to access but from the outside. If I can confirm this behavior, It is ok, but It is odd nevertheless.

    Thanks for the tip.

  4. #4
    Quote Originally Posted by mtruchado View Post
    Hi

    Today I faced exactly the very same issue here, I configured the virtual service (into NAT menu) to map the external 1234 port to the 22 port of an machine which is inside my network and I couldn't connect to it. I try both the ddns address and the IP which this ddns resolves to, It didn't work. I will try reconfigure It tomorrow and try to access but from the outside. If I can confirm this behavior, It is ok, but It is odd nevertheless.

    Thanks for the tip.
    If you have the same router and the same hardware version that I have (v4) then you will be out of luck. After several days of back and forth with tech support they told me that this is not possible on it because the nat loopback wasn't implemented for PPPoA. This router is also no longer supported so they couldn't do anything about it. More info here: http://forum.tp-link.com/showthread....l=1#post179343


 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright 1996-2017 TP-LINK Technologies Co., Ltd. All rights reserved.