Kneo wrote:Hello all,
I am new to OOMA. Just installed it on Sunday and so far we are loving it. I have OOMA hooked directly to my cable modem and my DLink DGL-4500 Router hooked to OOMA. One of the devices I have wired into the DGL-4500 router is a Windows Home Server Box.
Ever since I hooked up OOMA I have not been abled to remote access the home server. I can still access it through internally however.
Can anyone tell me what may be causing this and suggest a fix?
I'm not sure if your question is still unanswered, but I have a WHS that I was able to get back out to the Internet through the Ooma hub. Here's how you do it. First, go into the router's set up and write down the three ports you are forwarding through the router to get to the WHS. It's 80, 443, and one other if I remember correctly. Disregard the IP address for the WHS. You don't need that info to configure the ooma. Second, find the router's WAN IP address in the general settings and write it down as well. Third, go to the ooma setup menu and forward all three ports, one by one, to the WAN IP address for the router. What you are essentially doing is telling the ooma hub to forward the three ports to the router's doorstep. Then the router will forward the same three ports to the IP address for the WHS. What was screwing things up is that you were probably trying to forward the ports directly from the ooma to the IP address for the WHS, and the ooma will not recognize that IP address. You'll get an out of range error.
You can use the same procedure for configuring a Slingbox, for example, as well. Just forward the necessary port to the router's WAN IP address, and then let the router take it from there. As long as you did not change any of the port forwarding information in the router itself, it should work just as it did before putting the ooma between the modem and the router.
Hope this helps.