IP forwarding issue


 
G

GSlay

New member
Bear with me as I am not a network expert. I love my new HM 4.1 and had everything working. I had the HM set up to use DHCP and was able to forward the HM port on my router, and I was able to see my HM from outside the network. All was good. But, I kept having the issue that maybe others have seen where the HM would not get an IP all of the time. Once I powered it off, it would take several recycles, and then finally it quit getting an Ip at all. So, I switched to a static IP HM and this has solved my issue on my internal network - always links up.

The problem is now I cannot get access to the HM from the outside. I have the router set to forward just as I had it when I was using DHCP. But, no joy. Just times out. I have ATT Uverse. This seems to related to using static vs. dynamic IP addresses? Any suggestion?

The HM is awesome. Cooked an excellent rack of ribs yesterday while I was playing golf.
 
If you have a static IP set up on your HM, be sure to update your router to route incoming requests to the new IP. One possible problem is that you have another device getting the static IP you set for your HM before your HM can get it. Your router is probably starting at something like 192.168.1.2 and giving out the IP's incrementally first come first serve to all of the devices in your house (like phones, tablets, TV set top boxes and etc). If that's the case, your router is then routing to it instead, even if you did remember to update the routing with the new static IP. Not sure what your IP range is. But, say it's in the 192.168.n.m range. Try and pick a static IP for your HM that your router is not like grab, like 192.168.1.175. Or, reserve the IP in the router that you have already selected (tell it that you always want your HM to get that IP). Or, you can do both.
 
Thx I did set the IP on the router to be fixed vs dhcp. Looking at router IP assignments does not appear any other devices are getting same IP.
 
If it works when you enter the static IP of your HM in your browser and, your port forwarding is updated with the new static IP. The next thing I'd look at is your router's outside IP address. Go to whatsmyip.org. Use that IP in a browser and see if that works.
 
OK, tried this and it times out. It was working before on DHCP, but not now on static IP. And now try as I may, and cannot get the DHCP to work with the HM. When I join the wireless network via DHCP it never gets an address.
 
I'm sorry. I'm not sure what to tell you. It's been awhile since I configured networking on my HM. So, I'm less familiar with that side of it. Maybe you can recheck these steps.
 
FIXED - OK, I have figured out my issue after much trial and error.

- For some reason my ATT Uverse router does not immediately recognize when I power off the HM . It takes about 5 minutes for the router to show the HM as inactive after power off.
- If I power up the HM while the router is in this state, the HM will not get an IP address and not connect.
- If I wait until the router shows the HM as inactive, and then power up the HM, then the HM gets an IP and everything works fine.

This explains the intermittent issues I was seeing. When I first powered up the HM after it had been idle for a while it would work. Then I would want to mess with something (like IP forwarding), and I would power it down and power it right back up, and it would not work. Then of course I would get impatient and I would keep messing with it and power it up and down and up and down, and occasionally it would work (when I just happened to power it up after I had waited long enough for the router to show it inactive).

So, this had nothing to do with IP forwarding (of course). Maybe there is a configuration I am missing in my router or HM to have it recognize the power off? But, now I can get the HM to work consistently and as I said I love the HM.
 
Glad you figured it out. I'm sure someone will be able to benefit from your effort. If there's a setting for this, I feel sure it would only exist on the router side. And, it does seem like there should be an option to control that behavior on the router side.
 
You must log in or register to reply here.

 

Back
Top