OK now I'm getting upset. I stupidly deleted all the guide data on my Roamio thinking the problem was with my new lineup that just came down this morning about 2:00am. Now with the servers down I can't refresh the guide data and I'm going to miss any recordings I have scheduled for tonight.

They've got about an hour and a half to get this back online before I have to leave. If they don't I'm screwed.

The frustrating part is that it appears to render my two minis useless for watching recorded programs.

Crap if this affects the Mini my wife is going to be p*ssed when she gets home. I recently replaced an old SD only distribution system with a Mini for her treadmill TV. She exercises every day when she gets home around 5:30pm. If the Mini doesn't work I'm going to get all the blame for it.

Crap if this affects the Mini my wife is going to be p*ssed when she gets home. I recently replaced an old SD only distribution system with a Mini for her treadmill TV. She exercises every day when she gets home around 5:30pm. If the Mini doesn't work I'm going to get all the blame for it.

Knock on wood, but the minis in my house are all working OK now. Hopefully the same for your wife!

I've been seeing this thread for a while but wasn't following it too closely since I had never seen a C133 error on my Roamio.... but tonight it seems that I am in the same club with everyone else. As many others have said, I'm confident that it's not a problem on my end.

The C133 connectivity problem wouldn't be so bad if it didn't cripple so many functions that should be able to work just fine without the unit being able to 'phone home' to the TiVo mother ship.

Hopefully the TiVo folks will get this issue figured out relatively soon.

I've been seeing this thread for a while but wasn't following it too closely since I had never seen a C133 error on my Roamio.... but tonight it seems that I am in the same club with everyone else. As many others have said, I'm confident that it's not a problem on my end. The C133 connectivity problem wouldn't be so bad if it didn't cripple so many functions that should be able to work just fine without the unit being able to 'phone home' to the TiVo mother ship. Hopefully the TiVo folks will get this issue figured out relatively soon. -Joe

What did Zuckerburg say in the movie "Social Network " Facebook must never go down . Why ? Because it's critical to the survival of the business .

I purchases a Roamio Plus about two months ago and I have seen this C133 message about twice weekly . In other words about 16 times in two months .

For a service that requires server connectivity , Tivo is letting its customer base down

Hopefully this will provoke some redesign to remove needless dependencies on remote servers. (And, to separate dependencies on different servers -- e.g., there's no logical reason for my Reversi to be inaccessible right now, but it is. At least I can still reach other LAN servers and TiVos.)

__________________

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

Add me to the list of folks having the same problem in Orlando, FL on 2 Roamio Basic. It's happening right now despite all connectivity working fine. In my case this is the second time in the last week that it's happened.

Search is disabled, unable to run any apps (Netflix, etc), unable to edit/create season passes, unable to cancel recordings from My Shows (I have no clue why), unable to use the TiVo app (thus TiVo Stream), What to Watch Now disabled, etc.

I tend to believe her as well. At least that is where the evidence available to me is pointing. The problem is that the official line I get from Tivo support is that it is NOT the servers, and that leads me to believe that Tivo is NOT looking into it.

A little transparency here would go a LONG way. I'll sit back and wait a while if I know Tivo is aware of the issue and is trying to correct it. But all evidence I have so far says they are NOT. They are blaming my network 100% and totally ignoring the possibility that it is on their end.

I couldn't agree more. You have to be proactive in situations like this. I understand that a C133 error could be an issue on the customers end. However, when multiple people are reporting the same error at around the same time, you have to take a look at your infrastructure and communicate any infrastructure issues to your front line support teams so they aren't wasting time troubleshooting C133 errors when there is a known issue. The amount of time wasted on both ends is absolutely ridiculous. Put a flippin banner up when customers go to login or even a automated message advising that there is an issue when customers call in.

I run a network operations department for financial institutions and I still find it hard to believe how many C133 errors I have come across on my Tivo box. With today's technology and data center redundancy, Tivo is either behind in their infrastructure, or this is a Q&A process issue when updating servers.

Quote:

Routers that do NAT routing have to keep tables of active connections so they can figure out what goes where. It is quite common for router software to have bugs (Gasp!) that get it confused with lots of connections causing memory leaks and wot-not. That could easily explain rebooting the router fixing things. You could check and see if the router has newer firmware available (but sometimes trying to update firmware just makes things worse

All routers NAT otherwise it's simply a switch. If you have that many active connections that your NAT table gets overloaded then you will have issues with all other devices on your network.

My Troubleshooting Steps;

Can everything else connect? If yes go to Tivocommunity.com and see if the first post is related to c133. If there is, don't waste your time with support and wait for Tivo to fix their system.

Reconnect your modem and wait until it's offline. Once the modem is online connect your router. Run the tests again. If this still fails and you verified your internet connection is indeed active reboot your Tivo and run the tests again. If this continues to fail verify layer 1 (cabling). I realize this should be checked first but in home network not much changes constantly like in a datacenter. You will probably know if you moved your router and disconnected cables (or someone should know). ;-)

*side note* I hate rebooting my Tivo, waiting for it to load seems like an eternity. .