Originally Posted by giorgitd
But - why didn't the rtv dial up work for me? Tried local numbers, 800 number, numbers in CA, CT and IL - all posted here at one time or another. Multiple, multiple times, either from the setup screen or from 243 Zones. Changed the zip codes, too. The success with PercData/Laho suggests that my problems are not SS2k hardware or phone line issues. How widespread is the current failure to update/set time from rtv?
Like I said, before, and there are others who understand the details much better, it appears to be part and parcel of the DNS errors. Your unit was failing to connect on the initial DNS request. It moves on to fail to connect to the time server. Then it gets to the channel guide and may finally connect to the server and get guide data (or not if the number is no good).
From Jon's posts:
As you mentioned in a previous post, having the correct (or near correct) time is essential for getting the channel guide.
I don't remember if we discussed that even with a DNS failure session, it appears to me that a replaytv can get to a replaytv channel server. My traces and PTV console messages show that it may eventually try a session with the numeric IP address of a channel server of previous success. And, unlike a cached name resolution, this "previously successful channel server address" is preserved across replaytv reboots (note, I'm using the term "channel-server" just to differentiate from replaytv's NTP server). So, you could get to updating the channel guide in a session that couldn't set the clock, but if your clock is at 1999 I believe you will still end up with an empty channel guide.
Even with the DNS problem, there are ways a unit can connect
and get channel updates. Here is a trace of that type of connection.http://s91350486.onlinehome.us/R3kNightly.txt
Still has DNS errors but since the unit had saved a "good server" IP address, it eventually connects for registry updates and channel information. All of the "successful" nightly updates that I've traced have run in this mode. It takes an extra 7 odd minutes, but fails to set the clock. Fortunately, a functioning replaytv seems to do a good job of minimizing clock drift.
I'll also note that I have my two units connecting to two different numbers. One has a connection that, on average, takes 7 minutes longer than the other (6 min vs 13 min). This is an edited transcript of some emails I traded with Jon off the forum:
--> The first number is as reliable as the second number for "good calls" (only one attempt needed)
--> the first number actually completes "good" (last/only of the night) calls on average 7 min quicker than the second number
--> Both units have maintained 8 full days of guide info
7 minutes is the approx time wasted on "failed dns lookups".
Does it make sense that the first number would lose 7 minutes on a failed DNS lookup -- but still get a good channel guide download?
Yes. It would fall back to the "last known server raw IP address" for channel information, but it would fail to update your clock. Where people get in trouble is when that "last known server IP address" gets erased (possibly from a failed connection), and then they get no updates until a connection that starts off with successful DNS resolution. Of course, they are also in trouble when their replaytv clock is so off that it can't request a current channel guide.
My Mom's guide has never lost information, but the clock has drifted about a minute. She's using her local number. Channel update but time drift indicated to me that the DNS lookup fails, or even if the DNS lookup works, the replaytv's time server (ntp-rns.replaytv.net) is unreliable.
For me, it took several explanations from Jon before I "got" what is going on. It's a cluster-up (replace up with your favorite four letter word).
I will finally note that the 410-510-9009 number I have posted before is the one that for me completes calls in ~ 6 min.
Summing it all up, (if I understand everything Jon, Reden, and the others have been posting), once everything is copacetic (you connect successfully via DNS lookup, you have the right time, you start making regular nightly connections/guide updates), it will stay that way, unless you experience a power outage or reboot your unit -- in which case there is a danger that your unit's DNS cache will erase and you will go back to square one. I don't know if Laho sets the DNS addresses properly. My guess is that if you point your ReplayTV modem back to a known good number (like the 410-510-9009 number I've been using), it will probably update correctly until something changes (again).