POE filter only blocks Moca, making the modem work like it doesn't have Moca. Broadcast signals pass right through.I wouldn't have the broadcast then at all right? I have to have it to see any of my tivos. None of them are picking up the new modem
That is exactly what I thought the POE would do, thank you for confirming that. I know I need the MoCa...just not sure how to get it to function correctly with the new modem. I thought it strange that the first call numbers are 169 on the new modem but my regular numbers start 198. Am I wrong to think that's not right?POE filter only blocks Moca, making the modem work like it doesn't have Moca. Broadcast signals pass right through.
I think reconfiguring the Tivos will just open a Pandora's box.
I'm saying disable or block the modem's Moca entirely. You don't need the modem's Moca at all.That is exactly what I thought the POE would do, thank you for confirming that. I know I need the MoCa...just not sure how to get it to function correctly with the new modem. I thought it strange that the first call numbers are 169 on the new modem but my regular numbers start 198. Am I wrong to think that's not right?
The new modem has a built in MoCa previously I had an independent MoCa that allowed my Tivo mini's to work. If I want them to work I have to have that MoCa is what I understand. I think the problem lies at the 169 instead of reading 198. I don't really know anything about this darn set up like I knew my old one. I should have made sure it was configured correctly before I allowed the cable guy to leaveIf you're fully intending on not using the Built-In MoCA on the Router, just disable it in the Settings.
The Login Info is typically on a label on the side panel.
-KP
This. It's really hard to provide assistance not knowing what the original setup was. Was one of the TiVos acting as a bridge or did you have a separate moca adapter? I just went through similar turmoil myself. I too got a bum 169 ip. I can help, but need more info.I'm not super clear on the previous setup.
A diagram would be helpful.
Going back to my original suggestion, Network Setup for each TiVo is in Settings.
I'd disconnect all the MoCA devices and run through Network Setup on each one, connecting it to the Routers MoCA Bridge. Then unplug that TiVo/MoCA Device and repeat on the next devices.
If there was a previous Bridge, you won't need that anymore.
-KP
I appreciate everything anyone tried to help me with, cable guys were here today it took 3 of them to resolve the issues with it and i was right the biggest issue was that bum 169 ip address. Took then and 1 to figure out what was going on. Thank you all again and I will make this as resolved.This. It's really hard to provide assistance not knowing what the original setup was. Was one of the TiVos acting as a bridge or did you have a separate moca adapter? I just went through similar turmoil myself. I too got a bum 169 ip. I can help, but need more info.
So what was the final fix? even remotely?This issue was resolved thank you to all that tried to help!
Denise
I totally understand and I watched the techs but honestly they were scratching their heads as well, they called in another guy and he made my livingroom Tivo a Bridge so the modem could allow the MoCa to communicate is what I understand. I never had to do that before because I had the independant MoCa box and there was no "Bridge". They changed something in the modem to make it read the 192 not the 198 i said before when it was reading 169. I'm very sorry I can't give more details if I totally understood it I would have had it fixed myself. Now that I do know a couple more things if I run across something like that again i'll be able to handle it. So the ultimate answer besides making the modem communicate was the Bridge he had to open.So what was the final fix? even remotely?
You had a pretty easy to fix problem, but folks kept asking for details and didn't get them thus making anything we offered as just a guess.
TCF folks are far more knowledgeable and nice than CableCo techs, but you need to help us help you.
Also for those mentioning the 169.254.x.x IP addresses, those are the automatic addresses many devices will automatically assign themselves when they can't reach the right resources like a DHCP server on the network, they're not "bum addresses" they're your device saying " help I can't talk to anyone else"