Changed internal network, 24 hours later no TV or internet

[tksintenn]

I have several clients I have setup with VPN (typically Cisco ASA ipsec).  Typically when your internal subnet matches the internal network on the VPN it can cause issues, especially with split tunneling. 

So... i say that to get to this. I changed my internal network from 192.168.1.0/24 to 192.168.3.0/24 last night. The only immediate issue i found was the DVR stopped working and I assumed it was because of the internal LAN change. I rebooted the DVR and it worked just fine. 

This morning while I was at work my wife said it seemed yahoo and facebook were having issues. she was refreshing pages manually. She ran some errands came home, and nothing worked. TV or internet.  

I called U-Verse support around 4:45pm. The guy i got on the phone tried to tell me it was because i changed the internal network? Are you serious?  I've never had U-Verse and I know the gateway device controls everything but why would the internal network be a problem.  Wouldn't the outside interface be what they communicate with?  I let him schedule a technician but I went ahead and changed my subnet back to 192.168.1.0/24 (the default setting) and wouldn't you know it the internet started working, sort of.  It still feels shaky and sluggish. 

TV is a different matter. After changing the subnet back, rebooting the gateway and the DVR plus the other two rooms i do not have a TV signal. The guide just says "Guide Data is currently unavailable". 

I have some big concerns here. If I cannot change my subnet on my internal network that's an issue for me. Secondly, is U-Verse really this shaky? So far I like the service but the tech didn't have answer and i can't get the TV back on. 

[tksintenn]

oh and on the DVR unit it says IPTV connected for a status.

[SomeJoe7777 ACE - Geek]

Sometimes I've seen the 2Wire routers freak out for no reason. I suggest you factory reset the RG and attempt to set up the internal network again to 192.168.3.1/24. After you get the RG set like this and working, reboot the DVR. After it comes back up, then reboot all other STBs.

[tksintenn]

thanks i'll try that. my next task is to get my asa 5510 running behind it. I'm having my doubts now, just seems a little flaky. 

If a client called me with these experiences I would be switching them to windstream or the local cable company. Especially after the first tech told me it was because i had changed the internal LAN that he couldn't see my 2wire and the second told me I wasn't supposed to change the internal network at all, it HAD to be 192.168.1.1/24, gateway set to .254. That's laughable if it's true.

[SomeJoe7777 ACE - Geek]

Neither of those are true. I have mine set to 10.0.0.1/24, all STBs are on that network, and I have a Cisco 2811 behind the 2Wire as the DMZ device, through which I run all my computer traffic. My Cisco has IPSec and IP6inIP4 tunnels up and running through the 2Wire with no problems.

[tksintenn]

I knew it wasn't true. Why would an ISP need an internal network set a certain way? Even Windstream managed firewall solution you pick your internal net(s) they set the interface but it doesn't matter what you choose.