Originally Posted by bnraggie
I used a known good number in the prefix and I did get a connection, new channels, new zones, etc., but still no guide info was downloaded. The connection does drop when downloading "additional information," though. What's the next step to try?
It's the weekend, a good time to try RobMan's procedure athttp://www.avsforum.com/avs-vb/showthread.php?t=1403214
I've learned a lot from:
- enabling PTVIO, and looking at R3k, R5k console messages
- looking at those messages and Wiresharking an R3K try an update from the Replaytv servers through FREESCO (which it appears is now also broken)
- comparing all that with R3k thru FREESCO to WiRNS V2 which as previously mentioned works fine. Note that WiRNS V2 uses the Replaytv servers for data, and seems to solve the hung session when going directly from FREESCO.
Without going into a lot of detail, it appears to me that their "authentication change" has crippled DNS resolution. Here's a typical PTV messsage that happens after sitting on "connection established"
Nonfatal ERROR OCCURRED -
MODULE - DNS Module error number 0x907, parameters: 0x0, 0x0, 0x0
Task id is 0x1001c
Highest mem is 0x9c3cf22b
Task error code 0x0
But back to my orginal suggestion. The setup process goes to an 800 number. That number should be lightly loaded on the weekend. You *might* get lucky and bypass the DNS failure, and resolve "production.replaytv.net". Your replaytv will cache that IP address for some period of time, so if you do the 243 zones net connect soon after (no reboot in between), you will hopefully get a refreshed channel guide
P.S. one thing I've learned is that those "progress" messages after "Connection Established" during a long session, they just mean that the given step has timed out. Other people have mentioned this with respect to the setting clock message, but it also applies to all those percentage countdowns. This from observing the replay screen messages while observing the error messages on the PTV console, and observing the lack of any progress on a failed FREESCO wireshark.