Since manually assigning IPs didn't seem to make a difference, I deleted them and got this:
Now it doesn't lease out any IPs anymore. Before I would see the computer that I am on as an automatic line. I don't understand why they randomly show up and disappear in that section.
oh, my keyboard acts up lately, number '3' went AWOL. it should readjrabbit wrote:Even if I assigned different IP addresses to the various devices?tommies wrote:My guess here is you have the colliding of ip addresses, ie. two devices on your LAN some how have the same ip. So you need to find out which device has which ip address to be sure if the problem exist.
That doesn't work for me. When I do that I immediately gettommies wrote:I would recomment that you try some thing
1) connect your pc into the HOME port of the ooma hub. If you don't have extra network cable, just disconnect it from the router temporary. Then point your browser to http://172.27.5.1/ to access the hub web interface.
There must be something wrong with the way I have things connected. Keep in mind that the Ooma itself works well, it is just the VPN that throws me out.
Code: Select all
Unable to connect Firefox can't establish a connection to the server at 172.27.5.1.
But thanks for helping!
sorry for the confusion
I think you are right. The IT guy (who did not know what Ooma was) mentioned something about a VPN bridge that the VOIP might be using, and it might interfere with the work VPN connection.Groundhound wrote:I'm beginning to think that IP conflict is not the issue. Perhaps there is a port issue with the VPN that the Ooma hub creates vs the VPN you are trying to run on your computer. Have you any information on how the VPN on your computer is set up?
He also mentioned that we are using a "plain" VPN setup, whatever that means... Meaning I don't know much about the VPN setup other than that it usually works, and is I believe something Cisco?
What I told him though is that the whole thing worked fine for about 10 days, and broke down last Friday. He thought there might be some sort of update/patch/firmware/codec that Ooma pushed to their routers that all of a sudden causes the incompatibilities.
So... what about troubleshooting port issues? Whatever that is?
In your first post, you said you were unable to get the hub to work in front of the router. Is that correct? If you set the hub in front of the router, connected directly to the modem, and not turn on any other device except the modem and the hub, does the hub work?
You guys are absolutely amazing!!!!!!!! It looks like it works now!!!!!tommies wrote: oh, my keyboard acts up lately, number '3' went AWOL. it should read
sorry for the confusion
I followed your screenshots, put in the DMZ, and set the MAC address to built-in, then added a static IP with the MAC address back into the router, and so far, success!!! I don't know how to thank you. Perhaps one day I can help some other poor bastard to figure the setting out.
Groundhound, yes, I was unable to get the hub working directly connected to the DSL modem. With the new setting now (DMZ and built-in) I will need to try again, but I am too happy and tired of plugging cables now, and if it works like that I might just leave it the way it is. Thanks to tommies now I know how to get to the Ooma web interface. I might try taking out the IP setting in the router and test if it still works just with the DMZ populated.
I'd still like to know the rhyme & reason why things sometimes do and sometimes don't show up in my router config screen, but that's not really important. Thanks so much for all your help!!!