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

C125 error for 3 weeks -- no end in sight -- cannot connect to Tivo service

Discussion in 'TiVo Coffee House - TiVo Discussion' started by Greg Russell, Feb 25, 2018.

  1. GBL

    GBL covert opiniative

    1,887
    53
    Apr 20, 2000
    Twin Cities, MN
    Which ports/protocol is TiVo telling you to open?

    I'd suggest checking tclient.log immediately after a test call - might shed some more light on issue.
    To access log, navigate to system information screen, then press CLEAR,CLEAR,ENTER,ENTER,0, choose logs from screen.
    Here's a sample:
    IMG_2061 small.jpg
     
    Last edited: Feb 26, 2018
    ClearToLand, JoeKustra and kpeters59 like this.
  2. JoeKustra

    JoeKustra in the other Alabama TCF Club

    14,892
    2,235
    Dec 7, 2012
    Ashland, PA...
    How much do you know about the logs? Any place we can look to get some insight?
     
  3. GBL

    GBL covert opiniative

    1,887
    53
    Apr 20, 2000
    Twin Cities, MN
    Admittedly, not much: I know how to access them and examining them has helped me numerous times figuring out the problem.

    When i started out in IT many years ago, on batch only systems, examining and interpreting logs was the only way to learn why a batch job or program didn't run as expected and to figure out how to fix it. Error messages displayed to users don't always tell the whole story. "Real" programmers access the logs ;)
     
    wish_bgr, HerronScott and JoeKustra like this.
  4. Greg Russell

    Greg Russell New Member

    26
    4
    Feb 25, 2018
    Ports 37 (UDP and TCP) and 123 (UDP) -- and that's the same information the tech help at Google Wifi had in their database.

    Here are most of the logs I see. Does this help point in any direction? Stuff like this is why I decided not to become a computer programmer.
    20180226_121631.jpg 20180226_121725.jpg 20180226_121740.jpg 20180226_121817.jpg 20180226_121826.jpg
     
  5. GBL

    GBL covert opiniative

    1,887
    53
    Apr 20, 2000
    Twin Cities, MN
    Your logs have already been rotated (i.e. packed for delivery to TiVo[1] and cleared).

    You need to to the following:

    Start a TEST connection to TiVo.

    When that finishes, enter the logs and look at tclient log - you'll see the sequence of statements like I showed in my sample, especially the "HServerRqst: Setting clock" message, anything after that different than in my sample may shed some light.
    edited to add:
    In the tclient log, use ThumbsUp to go the beginning of the log, then scroll down with down arrow until you see the "Setting Clock".

    [1]You may wonder why TiVo doesn't interpret the received logs and tell you exactly what is wrong. For one, the Tier 1 Tech Support Person probably doesn't have access to the logs, two, TiVo probably receives millions of these logs every day and they may not be immediately accessible. By they time they right person looks at them, a long time may have elapsed if you ever hear back.
     
    Last edited: Feb 26, 2018
  6. JoeKustra

    JoeKustra in the other Alabama TCF Club

    14,892
    2,235
    Dec 7, 2012
    Ashland, PA...
    After doing what GBL suggests, the log titled tclient is the one that matters. Look for Setting clock. Command = "/bin/ntupdate -b 129.6.15.27 129.6.15.28 132.163.96.4 132.163.97.1"
    What follows will be the response. Any errors?
    Up/down arrows move one line. Channel up/down move more like the guide,
     
  7. Greg Russell

    Greg Russell New Member

    26
    4
    Feb 25, 2018
    Finding that line has proved to be elusive -- I'm looking again now -- I've run it several times and not seen that one go by yet. I'm failing "while negotiating" now instead of during clock setting (although that's the error I get most of the time during an internet check) -- somewhere around line 401, it goes to the end screen, where I get the 2 attached shots. Does the "failure" near the bottom of the longer script mean anything? 20180226_135316.jpg 20180226_135325.jpg
     
  8. GBL

    GBL covert opiniative

    1,887
    53
    Apr 20, 2000
    Twin Cities, MN
    Are you doing a TEST connection or a regular daily call?

    From the log it looks like a regular daily call. In that case TiVo now rotates the logs very quickly which makes it hard to study them.

    On a TEST connection, the logs stick around much longer making it easier to examine.
     
    ClearToLand likes this.
  9. DBrunetti

    DBrunetti Member

    87
    21
    Dec 6, 2016
    Connecticut
    I agree with Joe that it could prove you can access TiVos time servers. I say could because I just blocked all three addresses on my router and even though accessing them from my computer returned errors on all three I also ran a network test on my TiVo and it did not have a problem setting the time. so I do not know what is going on.
     
  10. Greg Russell

    Greg Russell New Member

    26
    4
    Feb 25, 2018
    What path should I take? I am running a full connection here -- when I go "network diagnostics" and "test internet connection", my Tivo will not allow me to back out. If I'm in the full connection, I can leave and go to the log.
     
  11. GBL

    GBL covert opiniative

    1,887
    53
    Apr 20, 2000
    Twin Cities, MN
    Do the test internet connection. Even though you'll have to wait, the log should still be there.
     
  12. NorthAlabama

    NorthAlabama tabasco rules

    8,870
    1,567
    Apr 19, 2012
    sweet home, al
    failing while negotiating is an issue that's been reported before, and while not common, it can generally be resolved with a call to tech support.

    that said, with the failure happening at what appears to be different points of the connection, i'm not sure it's related.
     
  13. Greg Russell

    Greg Russell New Member

    26
    4
    Feb 25, 2018
    Okay -- here's the error it generates. 20180226_150115.jpg
     
  14. JoeKustra

    JoeKustra in the other Alabama TCF Club

    14,892
    2,235
    Dec 7, 2012
    Ashland, PA...
    You need more patience. :) True, you must wait for it to finish, but that way you know the entries in the error logs are current. That and the time which is some time zone on Mars. But the minutes and seconds are correct (or would be).

    That said, it sure seems the time has failed (failed: code 1).
     
  15. Greg Russell

    Greg Russell New Member

    26
    4
    Feb 25, 2018
    I had it go to the end this time (the one I just posted). Previously, I was trying to capture the info in real time. That didn't work so well.
     
  16. JoeKustra

    JoeKustra in the other Alabama TCF Club

    14,892
    2,235
    Dec 7, 2012
    Ashland, PA...
    Code:
    Pinging 129.6.15.27 with 32 bytes of data:
    Reply from 129.6.15.27: bytes=32 time=34ms TTL=55
    Reply from 129.6.15.27: bytes=32 time=33ms TTL=55
    Reply from 129.6.15.27: bytes=32 time=31ms TTL=55
    Reply from 129.6.15.27: bytes=32 time=33ms TTL=55
    Ping statistics for 129.6.15.27:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    
    Pinging 129.6.15.28 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Ping statistics for 129.6.15.28:
        Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
    
    Pinging 132.163.96.4 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    
    Ping statistics for 132.163.96.4:
        Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
    
    Pinging 132.163.97.1 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Reply from 65.154.0.170: Destination net unreachable.
    Request timed out.
    
    Ping statistics for 132.163.97.1:
        Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
    
    BTW, if you want a mark, do: 777 Clear 911 Clear. Hit Clear fast. This puts a mark in the log. Do that before the diagnostic connection.
     
  17. GBL

    GBL covert opiniative

    1,887
    53
    Apr 20, 2000
    Twin Cities, MN
    The "no server suitable for synchronization found" error indicates that port 123 may be blocked somewhere upstream from your TiVo. How did you open those ports 37 and 123?
     
  18. Greg Russell

    Greg Russell New Member

    26
    4
    Feb 25, 2018
    Does this mean 3 of the 4 addresses do not work? Is there some way to work around?
     
  19. JoeKustra

    JoeKustra in the other Alabama TCF Club

    14,892
    2,235
    Dec 7, 2012
    Ashland, PA...
    Port 37 has never stopped anyone from working. I had the error for a year.
     
  20. JoeKustra

    JoeKustra in the other Alabama TCF Club

    14,892
    2,235
    Dec 7, 2012
    Ashland, PA...
    No idea, just guessing here.

    Do you have the same results?
     

Share This Page