Dear ASUSmy,

I'm glad to see you here. I'm having a problem on port forwarding on an ASUS RT-N56U, firmware version 3.0.0.4.374_239, that I hope you will be able to advise a resolution.

Previously, I was using TM's D-LINK UNIFI router, and then a TP-LINK without any issues forwarding port 3389 for RDP to a Windows machine, a VPN port 1723, and many other ports. all without problem. In this previous setup, my RT-N56U was operating in AP mode only.

Now I want to use this RT-N56U to be the main gateway to UNIFI, and have been setting it up fine with Internet access and HyppTV IPTV. However, I can't get the port forwarding to work on it. It just doesn't get traffic through a specific port (e.g. 3389) to a private IP in my LAN and back to the source device in the Internet.

Are there some special configurations on RT-N56U that I need to do? I'm not sure what I need to check. Could you please advise? In the meantime I will just revert to my trusty RM150 TP-LINK router...

Thank you,
Shanyung

Hi ASUSmy, I'm using private IP 172.26.0.0/24 for my LAN. RT-N56U LAN IP address is 172.26.0.3.

Here is a screenshot of my settings. I'm keeping it simple for now.



The only ports I can access from the Internet are 80 and 8080 (redirected) because I have its admin console enabled from the WAN. For the other ports I have set up, "connection timed out" is the error. Perhaps the requests are passing through but probably not routed correctly?

The destination IP 172.26.0.6 is running and is connected to the router port 3.

Please advise.

Thank you,
Shanyung



***EDIT***
I have figured out the cause of the problem now. The gateway was still pointing to my old router on my server. This explains why the response from the server did not reach the ASUS. Thanks for your help ASUSmy.
***EDIT***

This post has been edited by shanyung: Sep 24 2013, 08:35 PM

Something isn't working after this upgrade. I had mine upgraded as well and it sometimes prompted me with username and password but it refused to accept correct password on my computer, with different browser. I then use an iPad to connect and it accepted. I restarted it and the PC could then log on to it. But this symptom will happen soon again I am sure.

One other issue is that after I shut down my PC and started it up the next morning, accessing to the WEB UI on the router doesn't challenge me with username and password anymore. It straight brings me into the main UI page.

I haven't tried reverting the firm to the previous version.