N11, occasionally N13 connection issues can't connect for a week

Advertisements

So - I have a Series 3, an HD, and a Series 2, all Lifetime subscriptions. Series 3 and HD both have 2 cablecards each.

I tired to download a movie last night via Amazon on my Series 3 and I was told the service wasn't available. This happened to me about a month ago, and I figured out the problem was that the TiVo hadn't connected in a few days for some reason. I forced a connection and everything went through. Hurrah.

But this time, I got an N11 error while on step 3 - Retrieving data/Downloading.

So I tried again. And again. And again.

I have FIOS, the newer Actiontec router, central NJ. Series 3 and HD are connected via ethernet/powerline. Series 2 via wireless G.

I checked the Series2 - connected fine via wireless.

I checked the HD - hadn't connected either, since a day after the Series 3 last daily attempt. Forced connection - same thing, N11.

Troubleshooting;
- rebooted everything (router, TiVo) first one at a time, tried to reconnect, then both at the same time
- Tried using the wireless. Rebooted everything again with wireless on the Series 3. No dice.
- on wireless and ethernet configs, pinged S3 Tivo from multiple computers, both wired and wireless. No problems. Typed IP address into browser, connected fine.
- started messing with router features, created rule with all the TCP and UDP ports; added the Series 3 TiVo. No dice.

Note this setup has been running for years without interruption.

Tried the TiVo chat guy and he was no help whatsoever. Still saying ports must not be opened.

The HD box, I forced connection with and it worked, went through, downloaded and loaded. Yippie.

Series 3 is still failing, though. I've gone through the 10-12 or so previous posts here and elsewhere quoting N11 or N13 issues.. most seem pretty old, and not much help.

Help me, TiVo Community, you're my only hope!

 

Already tried that as well - static IP, assign IP, wireless, not wireless. It actually connected yesterday after about 50 forced tries, though. But it still doesn't make sense why it goes N11 or N13. Those errors are not very descriptive, and you would think TiVo would be able to give a better idea of what causes it to happen.