OK, so after getting the HR44 earlier in the week, (along with a SWiM 16 upgrade) I have a question.
As for my system, right now it's the HR44/200 (2 clients, 1 live), HR24/100 (just 2 weeks old, replaced under contract), HR24/500 and H23/600 - (with DECA), and a H20/100 all live now. I know the H20 is not MRV compatible and that's fine. (It doesn't even have an Ethernet port. I just keep it in my daughters old room for when she visits.)
My question(s) are two fold. And are based solely on what the installer said during the install. If you saw my earlier post about how thrilled he was to be here in the first place (NOT) then you understand why I have questions regarding his methodology.
While I'm far from a network administrator, I have always been able to get my home networks to work. I'm not uncomfortable playing around in a router for that matter, and know what a DOS prompt is, and will do things like "run", "cmd" and "ipconfig" if needed.
With that in mind, I know that connecting via Ethernet is light years faster than wireless. With my DLink for instance, the fastest wireless I can get is 65mbps versus 1Gbps wired, (or worst case 100mbps).
This is where I am confused. The installer insisted that with the HR44 that you MUST connect it wirelessly to the router. (Even though the router actually sits ON TOP of the HR44, so cabling isn't a problem.) He said that if I try to connect it via Ethernet that MRV will not work at all. In fact he said that is WHY it has a wireless connection, so that they don't have to use the CCK and connect to it and it will use it's "built in CCK". Quote; "However if you DO try and connect a (Ethernet) wire to it the built in CCK will not work at all. The HR44 itself will be connected to the "internet" but the DECA to MoCA system will not work." (On either end as I understood it).
- My thing is, why wouldn't it?
- Wouldn't it be much faster via Ethernet?
- Did DirecTV actually cripple this unit in such a way that you are forced to use a wireless connection?
And along with those answers, I suppose I could then get to the point of assigning static IP addresses. This part I mention because after only 24 hours I needed to reboot 1 machine to get it 'playing nice' again. As well as go online and reset other receivers and make sure they were named correctly in the "system". (Had a problem with them being listed wrong in both our iPad, iPhone and Android apps.) Plus I should be able to fix that (dropping problem) with static IP addresses for everything, (like I had to with an IP addressable wireless printer that had a habit of vanishing at the worst possible times).