I’ve been lurking here for about a year, but finally broke down and bought myself a 4-tuner Tablo. I got it working at about midnight last night after several hours of struggle. I have a background in IT and home media systems, so I thought it would be a snap, but that was not the case.
Anyway, after who knows how many reboots of the Tablo and my laptop, it finally occurred to me that Tablo might be confused somehow by my multi-WAN router, so I disabled one of the WANs, but still no luck. I finally disabled the other of the two WANs and finally got connected to the Tablo. Wasn’t too happy about what it took to get there, but I did make it through setup and finally got to see the interface and some video on my notebook. Yay! Hooked up my Roku 3 and got that working too. Made some recordings, did some quick quality comparisons to my SageTV setup and was feeling pretty optimistic until the Roku unexpectedly rebooted itself.
After that, it wouldn’t connect anymore. Notebook still worked, so I did a hard power cycle on the Roku, and then it could connect to Tablo once again. At that point it was about 2:00 AM, so I decided to quit while I was ahead and call it a day.
When I finally got back around to it this afternoon, it was working fine from yet another PC as well as my iPhone, so I decided to try my luck with turning my primary ISP back on. After that, I couldn’t connect from any device. Max in Tablo Support said, “…our server has no way of knowing that your Tablo’s external IP has changed which is why the web app didn’t work. To fix this a reboot of the Tablo is required.”
Well, many reboots later, it still wasn’t working, and I can only assume that is because the router is intentionally trying to balance the load between the two WANs, constantly confusing the Tablo server. Honestly, I think the Tablo should just give the server a shout and tell it where it is when a client tries to connect, similar to what GoToMyPC does. I mean, with a dynamic IP address, sooner or later it’s going to change, so if Tablo’s software design assumes that it will always be the same, that if faulty logic. It virtually guarantees that the Tablo will fail multiple times because of this alone.
Putting that troubling thought aside for the moment, after reading Max’s note, I tried to configure my router with an Outbound Policy Rule (using TCP), basically attempting to make it so that all outbound traffic from Tablo would traverse the same WAN, and thus the Tablo server should be less confused by traffic from my secondary WAN IP. That got me connected via web browser (with both WANs enabled), but I still couldn’t connect via iPhone. Just a minute ago I killed the secondary WAN, and that made the iPhone start working again, so obviously my router configuration attempts did not produce the desired results.
Mind you, in all of these scenarios, the client can see “Mark’s Tablo”, and it sees the Live TV guide, but it never can connect. I have tried it via Wi-Fi on the same LAN, but no connection. I then manually opened the required ports on my router and tried it via LTE, but got the same results. It passes the port test and indicates “Your Tablo is ready for remote access.”, but I can’t access it with the iPhone anymore. Very frustrating. I’m just not getting enough feedback from Tablo to tell what’s wrong. And I have never seen it work via LTE, so not sure if that is related or not.
So I am wondering, do any of you have any experience using Tablo with multi-WAN routers? And if so, were you able to make it work? Any suggestions will be greatly appreciated because as much as I am liking the Tablo’s potential, it would not be practical to abandon an expensive business-class multi-WAN router that works great with anything and everything except for Tablo.