Need extra help installing your Ooma Hub or Telo system? Let us know.
#14947 by wheel
Thu Aug 06, 2009 10:21 am
scottlindner wrote:
Not being able to reach the site by the domain name is different than making sure DynDNS is updated correctly.

Let's first test if DynDNS is being updated correctly. Log into your DynDNS account and go to your services to see what the current IP address is. Then go to http://www.whatismyip.com and see what your Internet IP address is. If they are the same, then you are updating fine.


The DynDNS appears to be updating correctly, http://www.whatismyip.com correcly shows what the DynDNS shows.

If you are updating fine but cannot access your locally hosted site by the domain name, that could be due to the Hub not supporting NAT loopback. I am not sure if putting your router into the DMZ will circumvent the NAT loopback limitation or not. A simple test to determine if it's a NAT loopback problem is to test your domain name from outside of your LAN. Either ask someone else to hit your site and see if it comes up, or go to a free web proxy (e.g. http://www.hidemyass.com) and see if it can bring up your site. If external users can access your site, but you cannot from within your LAN, that confirms the NAT loopback limitation of the Ooma Hub.


http://www.hidemyass.com cannot find me from outside. From inside it goes to ooma setup.


If you are having a NAT loopback problem there are multiple solutions for you to consider:
1. add the domain name and LAN IP address of your server to your hosts file


If I put the domain address (http://MYNAME.dyndns.org/) what ip address do I put in? Is this just a test to see if it finds it? Obviously it will not update on its own.

2. put your router in front of your Ooma Hub and don't plug anything into the computer port of the Ooma Hub. In this configuration you'll want to configure QoS on your router to ensure your Ooma calls get highest priority.

Scott


I guess I can rewire and use the cababilities of DD-WRT which has QOS capabilities in it.
#14952 by scottlindner
Thu Aug 06, 2009 11:23 am
wheel wrote:http://www.hidemyass.com cannot find me from outside. From inside it goes to ooma setup.


What do you mean by using that free web proxy "from inside"?

If the web proxy cannot load your site and DNS is working, you have a port forwarding problem. Are you sure you have the router in the Hub's DMZ? I don't recall if the Hub can support port forwarding or not. If it can, can you forward port 80 to your router's WAN IP and run the web proxy test again?

Scott
#14959 by wheel
Thu Aug 06, 2009 11:38 am
scottlindner wrote:
wheel wrote:http://www.hidemyass.com cannot find me from outside. From inside it goes to ooma setup.


What do you mean by using that free web proxy "from inside"?


Inside of my network

scottlindner wrote:If the web proxy cannot load your site and DNS is working, you have a port forwarding problem. Are you sure you have the router in the Hub's DMZ? I don't recall if the Hub can support port forwarding or not. If it can, can you forward port 80 to your router's WAN IP and run the web proxy test again?

Scott


I set up a rule that forwards port 80 to 172.27.35.2, my router. What does his do? I am not running a website, but only use dyndns to "find" my machine on the web for remote desktop.
#14962 by scottlindner
Thu Aug 06, 2009 11:57 am
wheel wrote:I set up a rule that forwards port 80 to 172.27.35.2, my router. What does his do? I am not running a website, but only use dyndns to "find" my machine on the web for remote desktop.


The Ooma Hub is also a router so if you have two routers connected to each other, you need to set up the port forwarding twice. However, if you put your router into the Ooma Hub's DMZ this bypasses the need to set up port forwarding on the Ooma Hub, or another way to put it, all ports are forwarded to your router.

Scott
#14963 by wheel
Thu Aug 06, 2009 11:59 am
[quote="scottlindner

The Ooma Hub is also a router so if you have two routers connected to each other, you need to set up the port forwarding twice. However, if you put your router into the Ooma Hub's DMZ this bypasses the need to set up port forwarding on the Ooma Hub, or another way to put it, all ports are forwarded to your router.

Scott[/quote]
Should the oomahuband then the router be rebooted after the change?
#14965 by scottlindner
Thu Aug 06, 2009 12:11 pm
wheel wrote:Should the oomahuband then the router be rebooted after the change?


I don't know if it's required, but it certainly is a good practice to be certain. One thing with the Ooma Hub to reset it is to press and hold the Ooma Tab in the upper left corner, unplug while still pressing the tab for 30 seconds, and then plug back in. I believe this does a reset. I don't know what makes that different than power cycling the Ooma Hub.

If this doesn't work, switching the order of things to put your router first will work as well. The only caution I have for you is that I had a lot of troubles with QoS in DD-WRT so I switched to Tomato.

Scott
#14993 by wheel
Thu Aug 06, 2009 2:11 pm
OK, I give. I rewired the setup to cablemodem - router - ooma. I can use Remote Desktop and ooma is working fine with QOS set from he router. Now the question is how do I ge to the setup page of the hub? setup.ooma.com does not work, and neither does http://172.27.35.1.
#14996 by Aveamantium
Thu Aug 06, 2009 2:34 pm
wheel wrote:OK, I give. I rewired the setup to cablemodem - router - ooma. I can use Remote Desktop and ooma is working fine with QOS set from he router. Now the question is how do I ge to the setup page of the hub? setup.ooma.com does not work, and neither does http://172.27.35.1.

You'll need to temporarily connect a computer to the HOME port on the ooma and put the 172.27.35.1 IP in ooma's DMZ. Then you can access the ooma by entering the IP that is assigned by the router (192.168.x.x). However, if you move the ooma in front of your router you need to undo this as your ooma's home page would be visible to anyone on the web.
#15006 by wheel
Thu Aug 06, 2009 3:18 pm
Aveamantium wrote:You'll need to temporarily connect a computer to the HOME port on the ooma and put the 172.27.35.1 IP in ooma's DMZ. Then you can access the ooma by entering the IP that is assigned by the router (192.168.x.x). However, if you move the ooma in front of your router you need to undo this as your ooma's home page would be visible to anyone on the web.


When I direct connect to the ooma hub, what do I use to access the web setup so I can enter 172.27.35.1 in ooma's DMZ?

Who is online

Users browsing this forum: No registered users and 6 guests