Separate names with a comma.
Discussion in 'TiVo Roamio DVRs' started by bdspilot, Oct 30, 2013.
Just got this for the first time tonight.
Me too. Must me on the tivo end
As did I. It started about 8:40PM EST, give or take.
1. Network diagnostics reports the Roamio can connect OK and that all is well.
2. I restarted the router. No resolution.
3. C133 persists as of this writing (8:50 PM EST).
Note that I did a PingPlot to "tivo.com" and it shows 100% packet loss at two hops between me and tivo.com. Perhaps this is a route issue? See attached screenshot. Is this the same domain that the Roamio goes to when it connects?
EDIT: Other than the packet loss between me and Tivo, ALL other routes I have tested are OK and I get my usual 29Mb/S speed test to all four corners of the US. Still C133 (and packet loss) as of 9:05PM.
Same error here and two different iPads timeout when trying to connect to Roamio Pro .,,annoying, but I'm sure TiVo will get it together before I wake up in the morning
Got the error tonight also. Glad its not just me. I can still make a daily call into Tivo, but have the error and no access to anything other than live tv and recordings. (no Netflix, etc).
Same here too. Roamio Plus has been C133ing for 20 minutes at least.
Rebooted the router and TiVo, no difference. I am able to force a connection and download guide data, but still get the C133 after.
Glad it's not just me.
Everything is working now. TiVo user since 2000, I love the Roamio!! We'll worth the upgrade especially if you have iOS devices (iPhone/iPad)
Thank you for reporting this. I saw this tonight for the first time on my brand new Roamio just after a router reset. I was certain that it must be a problem with my new box or network but the failure occurred at the same time as your reports.
So it must be an issue with the server. That is a relief!
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 .
Sigh. I called Tivo after the problem escalated to C501 errors trying to access the NPL. While I was waiting, it resolved. I tried to describe the C133 and C501 errors to the CSR, who insisted that I perform various troubleshooting steps until I told him three or four times that it had resolved and I was at this point trying to get some more information.
His normal troubleshooting steps were:
1. Connect to Tivo.
2. Reboot the router.
3. Reboot the Tivo.
4. Reboot the router and the modem.
5. Permanently open a range of ports.
I explained that steps 1-4 generally does not resolve it and that I continue to refuse to perform step 5, which would expose me to any passing port scanner.
What was (again) disturbing was that at no time did he acknowledge the possibility that the problem was on Tivo's end. Even after I mentioned that several people in this thread had experienced C133s at the same time. He maintained that there was no problem on their end.
I realize he is simply reading a troubleshooting flowchart, but enough is enough don'tcha think? How do we get this escalated to someone at Tivo that can actually do something other than repeat the same ineffective diagnostic steps. All indications I have indicate that there is NOT a problem with my local network. The packet loss I am (still) seeing might be part of the issue.... who knows. Tivo sure doesn't seem to want to look into it.
BTW, during our phone conversation, the CSR said that Tivo knows about the C501 errors and "has fixed it". I pointed out that I was calling because I was getting C501 errors so they did NOT appear to be fixed. At that point, the conversation got a bit convoluted and I was not able to figure out if he was referring to C133 or C501 and I finally dropped it.
Tivo Margaret, can you please weigh in here? If a C133 is indeed a TIVO server issue, can you at least get your CSRs to stop trying to get us to open ports and stop wasting time and corrupting recordings by rebooting the Roamio when it doesn't solve the issue?
Getting frustrated. I absolutely LOVE the Roamio. But if this continues, I may have to go back to our TivoHD.
Not directed directly at me, but..... I realize that is a possibility. But why is it ONLY the Roamio that has issues? Before, during and after a C133 episode, ALL other internet devices in the house can go ANYWHERE on the internet at full speed. If the problem is on our end, why can everything except the Roamio deal with it successfully? Our Roamio isn't streaming when it C133s, it is just trying to pull up previews and info. And rebooting the router does NOT always fix it.
Maybe the Roamio is desperately trying to keep hundreds of connections to different pause ad servers open? .
UPDATE: The next morning, my Roamio is operating normally (no C133s, anyway) but I am still getting 100% packet loss at two hops between me and www.tivo.com. So maybe the packet loss is not related to the issue?
I think everything was down for a few hours yesterday.
I noticed, but it really wasn't that big of a deal, just affected the suggestions and other minor functionality.
I wouldn't have even noticed if the IOS app wasn't unable to connect.
still getting the c133 error. It is intermittent. it goes away then comes back. like a bad girlfriend. still no TiVo solutions yet ?
I'm not holding my breath. Except for one post from Tivo Margaret stating that C133 WAS a Tivo issue, in every other contact I have had with Tivo about C133s the CSRs act like they are 100% convinced it is a local networking issue. That or they don't have a clue and are just guessing.
Regardless of where the issue is, it needs to be addressed. If it is a LAN issue, then Tivo needs to be able to deal with it like all the other internet devices I have that are 100% while the Roamio displays C133.
In the mean time, we all need to call Tivo EVERY time we see a C133 so they have a better handle on how prevalent it is.
It's not a big deal if you want to watch live or recorded TV. The problem is other services such as Netflix or YouTube also don't work when the Roamio is 133ing, even if the local network is working.
Luckily I have a PS3 to use as a backup for those network services, but I still wasted 20 minutes trying to figure out if it was my problem or TiVos. That's also 20 mins where my wife is scowling at me because the kids are in bed and she wants to watch Breaking Bad.
Exactly....that's why I started this thread:
I mean, you can't even delete a scheduled recording while there is a C133 error.
I sent a tweet to @tivodesign pointing Margaret to that thread because I'd like some kind of explanation from Tivo as to why these services aren't available when the Tivo can't phone home?!?! I mean, not being able to stop a recording is CRAZY!! And I see no reason why I shouldn't be able to load Netflix, Youtube or Comcast VOD during the error.
As far as the CSRs are concerned while I am sure there are good ones... Jake is the only totally competent one I've seen recently
That's because TiVo is "Big Brother" in this scenario.