UPNP and Windows Home Server issue

[rlcronin]

I just got a new RT66U to replace an older Dlink router. I updated firmware to Merlin's latest (18b). Everything is working great so far except one minor issue. I have a Windows Home Server (v1) box that uses UPNP to configure the router to enable incoming http and https traffic to be forwarded to the WHS box without me having to do any manual port forwarding. That has worked with my previous routers. With the RT66U it did not work. I ended up having to manually add port forwarding rules and now all is well. So, its not a huge issue, but it would sure be nice if it could be fixed. How can I help gather information to assist with the debugging?
--
bc

 

[Chriscic]

I just got a new RT66U to replace an older Dlink router. I updated firmware to Merlin's latest (18b). Everything is working great so far except one minor issue. I have a Windows Home Server (v1) box that uses UPNP to configure the router to enable incoming http and https traffic to be forwarded to the WHS box without me having to do any manual port forwarding. That has worked with my previous routers. With the RT66U it did not work. I ended up having to manually add port forwarding rules and now all is well. So, its not a huge issue, but it would sure be nice if it could be fixed. How can I help gather information to assist with the debugging?
--
bc

I just got the RT-N66U tonight and am also running WHS v1. I'll let you know if I have any trouble with this issue.

Update: UPNP Port forwarding appears to be working just fine. I have Port Forwarding under WAN, VPN/Port Forwarding turned off (Enable Port Forwarding = NO) which is the default and confused me a bit. But when I go to system log port forwarding I can see the ports that have been forwarded via UPNP.

So while I haven't tried to access everything outside of the network yet (SageTV webserver, AirVideo, Qloud) should be set up to work properly.

 

[rlcronin]

I just got the RT-N66U tonight and am also running WHS v1. I'll let you know if I have any trouble with this issue.

Update: UPNP Port forwarding appears to be working just fine. I have Port Forwarding under WAN, VPN/Port Forwarding turned off (Enable Port Forwarding = NO) which is the default and confused me a bit. But when I go to system log port forwarding I can see the ports that have been forwarded via UPNP.

So while I haven't tried to access everything outside of the network yet (SageTV webserver, AirVideo, Qloud) should be set up to work properly.

I discovered that by default, the uPnP support in this router refuses to allow port numbers lower than 1000 to be opened. You can telnet to the router and use nvram commands to manually remove that restriction (which I did and now all is well). Here's a link to the info I found:

http://www.linksysinfo.org/index.ph...-still-complains-about-port-forwarding.33553/

The info there talks about Tomato, but as AsusWRT and Tomato have a common heritage, it is applicable to the n66u as well.

If you're the least bit worried about the fact these nvram commands make it possible to open up alot of other ports besides 80 and 443, then don't do this and stick with manually entering port forwarding in the router setup.
--
bc