AiCloud and Windows Home Server Now Work Together

[Mick Mickle]

I just want to point out that with the newest firmware versions, AiCloud no longer monopolizes port 443, so remote web access for the WHS family of servers can coexist out of the box. All you need to do is change the AiCloud Web access port (say to 444) in the Settings tab of the AiCloud tab and also change it on your Android app (or other remote client) settings. Then, the required port forward settings for WHS (443 and 80) are free for its use. I hadn't noticed anything in the change logs or the forums that specifically addressed this issue, so perhaps this posting will help the Google searchers.

(However, I found that uPnP is still a problem for WHS2011 and port forwarding still has to be set manually. Supposedly, the reason is that the Tomato firmware, upon which Asus bases theirs, doesn't allow uPnP to ports below 1024. I put in the following commands which were supposed to fix that:

nvram set upnp_min_port_int=80
nvram set upnp_max_port_int=65535
nvram set upnp_min_port_ext=80
nvram set upnp_max_port_ext=65535
nvram commit

but for me, WHS still complains in its Dashboard if you try to have WHS set the router.)

 

[RMerlin]

I just want to point out that with the newest firmware versions, AiCloud no longer monopolizes port 443, so remote web access for the WHS family of servers can coexist out of the box. All you need to do is change the AiCloud Web access port (say to 444) in the Settings tab of the AiCloud tab and also change it on your Android app (or other remote client) settings. Then, the required port forward settings for WHS (443 and 80) are free for its use. I hadn't noticed anything in the change logs or the forums that specifically addressed this issue, so perhaps this posting will help the Google searchers.

(However, I found that uPnP is still a problem for WHS2011 and port forwarding still has to be set manually. Supposedly, the reason is that the Tomato firmware, upon which Asus bases theirs, doesn't allow uPnP to ports below 1024. I put in the following commands which were supposed to fix that:

nvram set upnp_min_port_int=80
nvram set upnp_max_port_int=65535
nvram set upnp_min_port_ext=80
nvram set upnp_max_port_ext=65535
nvram commit

but for me, WHS still complains in its Dashboard if you try to have WHS set the router.)

miniupnpd will need to be restarted after to do that change for it to pickup the new values. Simplest method is to reboot your router, then see if WHS has better luck in forwarding its ports.

Reserved ports (1-1023) aren't forward able by default probably for security reasons (otherwise a rogue upnp application could easily hijack traffic destined to an internal server). I might eventually add an option to the webui to make it easier for people to change this, but in the mean time manually changing the nvram values is the way to go.

 

[Mick Mickle]

miniupnpd will need to be restarted after to do that change for it to pickup the new values. Simplest method is to reboot your router, then see if WHS has better luck in forwarding its ports.

Reserved ports (1-1023) aren't forward able by default probably for security reasons (otherwise a rogue upnp application could easily hijack traffic destined to an internal server). I might eventually add an option to the webui to make it easier for people to change this, but in the mean time manually changing the nvram values is the way to go.

Yes, perfect! Thanks, RMerlin -- I forgot to reboot the router after changing the values for allowable ports that can be forwarded. WHS was 100% happy for the first time with this router. (And I can use AiCloud as well.)