NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Ultra 4 no longer archiving Tivo files
As of 2/16, my Ultra 4 has been unable to successfully transfer any Tivo files. Nor can I via Web or Tivo Desktop. According to the Tivo Community Forums, this appears to be a widespread problem, evid...
Hi, I just thought I would pop over from the TiVo Support forums and let you know this is a known problem and that TiVo says they are working on it. There are some workarounds for TiVo's Windows software, TiVo Desktop, and several third party programs have been patched to workaround the issue too. Because of that it may be possible to workaround it here using one or more of the same techniques until TiVo gets their fix out.
The problem is caused by the TiVo expecting (or is it sending) an expired cookie when a transfer request is initiated. The expired session ID cookie causes the transfer to fail. Sadly, TiVo hard-coded the date into their software back in 2005 and then apparently forgot about it.
There are two known workaround Windows users are using, here is a link to one of the related threads on the TiVo support forums:
http://forums.tivo.com/pe/action/forums/displaythread?rootPostID=11069716&channelID=10&portalPageId=10432560
The first workaround is to the change the date and time of the device, in this case the ReadyNAS with ReadyDLNA, to a date and time earlier than the cookie expiration. Clearly that workaround will present other issues, but it does work for TiVo transfers. The second workaround works for devices using the cURL program to initiate the transfers. Essentially a permanent session ID cookie is placed in the curl.conf configuration file. Luckily the TiVo software ignores the cookie content, even though it does care about the date. This workaround was found by morac from the TiVo Community Forums. His post in the linked thread defined that fix quite nicely.
I don't know the ReadyDLNA well enough to say whether this or another workaround inspired by it would be useful, but I wanted to share with you folks in case you wanted to give it a try.
Good luck, and I hope TiVo gets the fix out soon.
Another place this is being heavily discussed is at the TiVo Community Forums, feel free to stop in over there for more ideas and discussion.
CuriousMark
The problem is caused by the TiVo expecting (or is it sending) an expired cookie when a transfer request is initiated. The expired session ID cookie causes the transfer to fail. Sadly, TiVo hard-coded the date into their software back in 2005 and then apparently forgot about it.
There are two known workaround Windows users are using, here is a link to one of the related threads on the TiVo support forums:
http://forums.tivo.com/pe/action/forums/displaythread?rootPostID=11069716&channelID=10&portalPageId=10432560
The first workaround is to the change the date and time of the device, in this case the ReadyNAS with ReadyDLNA, to a date and time earlier than the cookie expiration. Clearly that workaround will present other issues, but it does work for TiVo transfers. The second workaround works for devices using the cURL program to initiate the transfers. Essentially a permanent session ID cookie is placed in the curl.conf configuration file. Luckily the TiVo software ignores the cookie content, even though it does care about the date. This workaround was found by morac from the TiVo Community Forums. His post in the linked thread defined that fix quite nicely.
I don't know the ReadyDLNA well enough to say whether this or another workaround inspired by it would be useful, but I wanted to share with you folks in case you wanted to give it a try.
Good luck, and I hope TiVo gets the fix out soon.
Another place this is being heavily discussed is at the TiVo Community Forums, feel free to stop in over there for more ideas and discussion.
CuriousMark
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
