Trying to establish remote access for both WHS v1 and amahi
Posted: Tue Sep 16, 2014 11:53 am
Hi there,
After a month's worth of trepidation, I have today instated my HDA as my DHCP router. Locally, everything works fine both wifi and cabled. However, when we try to access the HDA from the internet with the xxxx.yourhda.com address, we arrive at our Windows Home Server (WHS v1) landing site https;//xxxx.homeserver.com instead.
The WHS has happily auto-negotiated its necessary forwarding of ports 80, 443 and 4125 with the "new" amahi router, and I see from the documentation that amahi uses the same standard ports for http and https 80 and 443, so I'm guessing the key to the problem is here.
Had this been my old Netgear router, then I'm pretty sure I could have made appropriate triggering or forwarding to keep both servers accessible, but when logged on to my amahi dashboard in advanced mode, I can't find anywhere to make my own decisions about port forwarding/triggering.
The goal is to have both servers running while I get used to amahi, therefore both need to be accessible from the internet. Is there an easy solution, or do I need to switch to some different ports in amahi, or how else can I accomplish this?
Coming from the Windows GUI-world, I have very little understanding of using a terminal, but I am willing to experiment if necessary... just please be gentle
Thanks for any pointers!
After a month's worth of trepidation, I have today instated my HDA as my DHCP router. Locally, everything works fine both wifi and cabled. However, when we try to access the HDA from the internet with the xxxx.yourhda.com address, we arrive at our Windows Home Server (WHS v1) landing site https;//xxxx.homeserver.com instead.
The WHS has happily auto-negotiated its necessary forwarding of ports 80, 443 and 4125 with the "new" amahi router, and I see from the documentation that amahi uses the same standard ports for http and https 80 and 443, so I'm guessing the key to the problem is here.
Had this been my old Netgear router, then I'm pretty sure I could have made appropriate triggering or forwarding to keep both servers accessible, but when logged on to my amahi dashboard in advanced mode, I can't find anywhere to make my own decisions about port forwarding/triggering.
The goal is to have both servers running while I get used to amahi, therefore both need to be accessible from the internet. Is there an easy solution, or do I need to switch to some different ports in amahi, or how else can I accomplish this?
Coming from the Windows GUI-world, I have very little understanding of using a terminal, but I am willing to experiment if necessary... just please be gentle
Thanks for any pointers!