Apparently the TiVo Premiere doesn’t like having its NTP requests redirected to a local NTP server. With a firewall setup to redirect destination UDP port 123 the TiVo’s service call fails, complaining it can’t set the clock. This is very peculiar to me for multiple reasons: 1. Other Linux and Windows based systems on the network can successfully obtain time in this manner. I can only assume that the TiVo expects some sort of hard-coded NTP response that it isn’t getting from other NTP servers. 2. There are many old posts on various forums about how redirection is a solution to other TiVo NTP issues, although with no confirmations I can see, so I question if that advice was ever valid and if so when/why did things change? 3. The TiVo’s error message indicates that not only is UDP 123 blocked but that TCP 37 is blocked as well. This leads me to believe that the legacy Time protocol is still supported, but clearly the TiVo isn’t successfully falling back to it. The local firewall is not configured to redirect UDP 37 traffic, so everything there should pass unfettered. 4. I find it odd that the TiVo can't obtain the time from within a service call session instead of making a discrete NTP, Time, etc. request a blocking step for the service call. Is there a way get the current TiVo software to play nice with an NTP server other than the TiVo service one? Any other insights are welcome.