For a few months now, we have been struggling with an odd issue with our home network and Tivo setup. We have a total of five TiVos, but only four are installed and running on the network. Around the beginning of the year, we started noticing that the bedroom TiVo would drop all connections to the other TiVos (but usually not lose the connection to the TiVo emulator on my desktop PC). The other TiVos, meanwhile, could usually still see and get data from that TiVo. It would usually be alright for around 48 hours, then drop to this state, and then sometimes would drop to a state where it couldn't see out and the other networked devices couldn't see in.
What made this very odd is that we have an official TiVo wireless dongle. When plugging this in, the exact same thing would happen: for approximately 48 hours it would be fine, then it would drop the outside looking connections to the other devices but they could still see (and transfer from) this device, with sometimes it dropping completely and no connectivity is allowed.
Over the last month or so, we have been steadily testing every possibility that we could conceive. First, I contacted TiVo; the support rep confirmed what I was saying by logging into the machine and looking at its error logs -- the TiVo would connect for about 48 hours and then drop. All the testing he could do from his end indicated the TiVo was working properly internally. His suggestion was either send it in for testing and fixing or buy a new one. Since buying a new one was actually cheaper, we opted to do that.
We plugged in the new TiVo and, after a few days, it started doing the exact same thing as described above. The "bad" TiVo was moved to another room, plugged in, and has worked steadily ever since without issue. So, it must be the home network, right?
My wife is in IT and she brought home some testing equipment and we tested the wires between the fiber op modem and that TiVo -- everything tested fine (no shorts, nothing to indicate bad wires). We then thought maybe it was a bad switch at our network hub; using different ports and switching with "known good" ports resulted in the same issue after about 48 hours. We have used a total of three different switches, all with the same result. Wireless still had issues.
Finally, we had our entire internet go down. Turns out we had a bad fiber op modem, and the repair guy switched it out. I noted that when he was talking to his helper by phone (the guy who was pinging and testing from the company's side), one of the first things he asked me and something he reiterated later was 'how many devices do you have connected?' Since these devices can, standard, work with upwards of 255 devices, I found this odd and worth remembering. Maybe the company in question (Bell Aliant) manually sets a device limit in the modem?
Since the new modem was installed, things have been faster and more secure online. However, our network issue with that one TiVo has remained. We had a knowledgeable friend come over and fix the downstairs jack for us. Everything tested as working, but when we plugged everything in ... nothing. The light didn't come on in the switch at our network hub and the TiVo didn't even get a DNS or IP from the network. It was not connected.
Another friend had a good idea; bypass the jacks and wires in the network and run an ethernet cable directly from the TiVo in question to the switch downstairs and see if that works. Sure enough, this morning, I did just that. The light on the switch came on very steady and the TiVo grabbed a DNS and IP and is working. It can see all three other TiVos plus my PC without issue. This seems to indicate that it is an issue with the cables or jacks between the switch and the TiVo; the cables continue to test as fine and one jack has been replaced. We may have to replace the other jack to solve this problem (it is in an awkward spot and will not be easy to get at).
So, we wait. If, after about 48 hours, this is still working, then we know somewhat what the problem is and can try fixing it via the jack replacement. Hopefully that solves the problem.
But I'm still left with the question: why does the wireless connection have the exact same issue?
"Take something you love, tell people about it, bring together people who share your love, and help make it better. Ultimately, you'll have more of whatever you love for yourself and for the world." - Julius Schwartz, DC Comics pioneer, 1915-2004
Copyright
All blog posts, unless otherwise noted, are copyrighted to the Author (that's me) and may not be used without written permission.
-
I have played both State of Decay and State of Decay 2: Juggernaut Edition , both zombie survival games, for many years and enjoy the titles...
-
Well over a week ago (probably closer to two weeks, now), I did something to cause my lower back to give me pain. Now, due to RA, I'm in...
-
Read this post. And I'll add... (Prior to the ceremony) And... (Saying the vows to each other) And... (You may kiss the bride... and I d...
Subscribe to:
Post Comments (Atom)
Outside my home, in a small access on the garage wall, are the TV cable wires. Although the house is wired for cable in every room, I didn't get it in some of the rooms, which I think is odd. What your dad determined one day is that full cable depends on how those outside wires are connected: reconnect the wires differently and I suddenly had complete access for cable. Your issue may be similar with that one room: it may be a quirky wiring problem.
ReplyDeleteAnd, I'll be you're going to hear from the cable company about the number of TiVo's you have hooked up!! I'm sure there's an extra charge for that service :-)
In this case, it is our own internal network that we (well, friends of ours) installed. And Bell Aliant cannot complain about our TiVos -- TiVo is here and we can network as many as we want together, barring any issues with IP and DNS quantities. The TiVos are owned outright by us and the cable company cannot do anything about it (and their own DVR sucks, as most cable company DVRs do when compared with a TiVo).
ReplyDeleteIt appears the cable is working; it has been over the 48 hours and all systems are still seeing and being seen by the one port in question, so we may have finally narrowed down where the issue is.