1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

C133 question

Discussion in 'TiVo Help Center' started by Malguy, Feb 18, 2014.

  1. Malguy

    Malguy New Member

    11
    0
    Dec 28, 2013
    Wa.
    Hi,

    First some background then my question to the people reading this post.

    I live in Western Washington state, in the Seattle/Tacoma area. I setup and installed my TiVo Roamio on 1/15/2014 and everything was fine for about 3 weeks. Then on or around 2/06/2014 I started receiving C133 errors almost daily, at least 4 days per week, at different times while trying to create a season pass or when selecting “What to Watch Now”. I reported this issue, via email, to TiVo support and they offered the following suggestions, 1) un-plug then plug in the TiVo box and un-plug and plug in my gateway/router/modem, after everything resets force a connection to the TiVo service, 2) verify that my TiVo is configured properly and that the recommended ports are open. I have performed both of these tasks but the problem still exists.

    My question to you is; is this error, C133, just something that I should get used to and learn to live with, or is there a solution that you found.

    I have read several posts that refer to this same issue, occurring around the same time, but the folks at TiVo support say that the issue was resolved. It appears to have been a problem on their end.
     
  2. ThAbtO

    ThAbtO TiVoholic by the bay

    6,724
    8
    Apr 6, 2000
    SF Bay Area
    Most of the time it is Tivo servers fault whenever it is down. Series 3 and earlier boxes does not use these servers so they never get this error. Premiere and Roamio use this server for things like the discovery bar on top and other things, even though Netflix and youtube does not use these servers, they get affected as well and no access.

    If you have done resets on your Tivo, router, and modem and the error C133 still remains, it is Tivo's servers fault.

    I have had a number of C133 on my Roamio and only once was my router's fault.
     
  3. dianebrat

    dianebrat I refuse to accept your reality TCF Club

    10,122
    78
    Jul 6, 2002
    boston'ish
    ^^ what ThAbtO said.
    a C133 is " I can't reach the Tivo mothership to check on things like status"
    Most recently this has been issues on the Tivo side of the equation, but it's more than possible that it's a problem on your side if you're having a network issue.
     
  4. L David Matheny

    L David Matheny Active Member

    1,588
    1
    Jan 29, 2011
    SE Ohio
    My OTA-only 4-tuner Roamio was getting C133 errors intermittently for a while last night. I didn't reset anything because I assumed it was TiVo's servers acting up. Maybe they were overloaded for some reason.

    A C133 error wouldn't bother me 95+ pct of the time IF the software would just throw the error message up into the discovery bar area and immediately continue with more important business. But incompetent programming causes everything to hang for a while until the attempted server access times out. That's irritating.
     
  5. wenfeen

    wenfeen New Member

    2
    0
    May 28, 2012
    Using a Time Capsule router directly connected to my modem which is at a distance from the Premier; when checking the signal strength it shows as "excellent".
    The Premier is set up to use the TC 5 gz setting & the N Adapter has been reset to use the 5 gz. All network names are the same.
    Prior to using the TC router I rarely had a connection issue on my Premier, but now at least once or twice a day we have a C133 message, even though our programs usually record properly.
    It seems as though I'm constantly doing hard resets on the Premier & N Adapter. All our other wifi devices are working fine. I live in MA, using Fitchburg Comcast. I've gone into Settings & "reconnected". Even have "changed the network settings" even though they are the same.
    I'm frustrated & wonder if there is something I can do at my end to fix this. Sometimes our network settings show the network connected, other times we receive a "fail" message.
    Might creating a static IP help, and how does one do that? I've tried before but seem to be doing something wrong. I hope someone has an idea.
     
  6. ThAbtO

    ThAbtO TiVoholic by the bay

    6,724
    8
    Apr 6, 2000
    SF Bay Area
    After you had done all the router, modem, Tivo resets, reconnects, re-logins and still get the C-133, then its not the fault on your end but at Tivo Servers. There is nothing else you can do. Tivo will still record and play back recordings but when it tries to get the discovery bar, it times out.
     
  7. wenfeen

    wenfeen New Member

    2
    0
    May 28, 2012
    Thanks for the quick reply. Let's hope Tivo gets it fixed. It's only happening on the Premier, not the two HD Tivo boxes.
     
  8. Mar 7, 2015 #8 of 10
    CraigThom

    CraigThom Member

    55
    0
    Sep 27, 2002
    but I think it may be more, since "My Shows" on tivo.com hasn't updated in two weeks.

    I can connect to TiVo, download guide data, and schedule recordings on the Web site, but I get C133 for the discovery bar, search, some wishlists, etc., and the YouTube, Hulu, and other apps are missing.

    I've contacted TiVo via chat, but they suggest either waiting to see if it goes away or sending in my Premiere for a replacement.

    I've tried very briefly bypassing my router and connecting directly to my cable modem to make sure no ports are being blocked.

    I've done kickstart 57 and 52 just for kicks.

    Is it definitely on their end? Will it eventually start working again? Will I get the new OS through the normal connection process, which works? Maybe installing the new OS will fix it?

    It's not as if the unit is down, but I rely heavily on wishlists.
     
  9. CraigThom

    CraigThom Member

    55
    0
    Sep 27, 2002
    Not that anyone cares, I guess, but my TiVo downloaded and installed 20.4.6a.RC1 yesterday, maybe because I called in and convinced someone that it was a real problem.

    I finally got my money's worth out of my MikroTik router by capturing packets to and from my TiVo while I rebooted it.

    I'm not a networking expert, but it appears that the problem is with the SSL connection to 208.73.181.200. If I'm reading this correctly, I think that TiVo server is rejecting the connection due to an expired certificate.

    So that's why I'm getting the C133 error. It isn't a network communication problem; it's a network protocol problem.

    I've sent an email message via TiVo's Web site. I hope it gets passed along to someone who can look into it instead of just being answered by someone telling me to reboot everything and try a wired network connection.
     
  10. CraigThom

    CraigThom Member

    55
    0
    Sep 27, 2002
    Just in case anyone is following this, my frustration level continues to rise.

    I know where the problem is. I can see it happen in the captured traffic between my TiVo and their server.

    Unless they've got a box doing this in their lab or they've got another user out there would is packet sniffing, I think it's a real possibility that they don't have this.

    All I want to do is provide the data to whoever is working on it. However, my only options for contacting support are chat, phone, and a form on the Web site.

    I keep getting told that this is a known issue, that is is being worked on, and, by the way, reboot everything and make sure the right ports are open.

    This means the person answering in the email has no idea what the problem is or what I have been able to discover.

    I fear that, because he or she doesn't understand it, he or she is not passing along the details that I am providing to the right people.

    If they know it's an SSL certificate error, then, fine, tell me they know it's an SSL certificate error they are working on. Tell me you've told them that's what I've discovered.

    But, no. All I get is that it's a known issue being worked on and they'll ask for more information if they need it. Oh, and try rebooting and bypassing any switches, and check to make sure the right ports aren't being blocked.

    [​IMG]

     

Share This Page