Separate names with a comma.
Discussion in 'DIRECTV Connected Home' started by Doug Brott, May 20, 2010.
And it's just some CSR's don't know where they have to go to enable it so they say they can't do it.
Networking is networking, why wouldn't it work?
I can't speak for anyone else but I can tell you my situation. I already had my HR21 on my wired home network. I was getting a new H24 (turned out to be an H23) and wanted MRV. When I called, directv wanted to charge $99, roll out an installer, and replace my dish because I "had to have a SWiM dish". In my case I have Cat5e throughout the house so I didn't have to buy any new equipment to turn on unsupported mode. Even if I hadn't, I would have paid for equipment to avoid a new dish, new wiring, new DECA injectors messing with existing whole-house network, etc. Of course it helped my decision that I am a network engineer and know what I am doing.
Bottom-line, there are folks out there who like to do things on their own and not deal with installers, huge appointment windows, new dishes, etc. I am just trying to present them with alternatives that I know will work.
If you're using hard wired ethernet network then yes, that would probably work just fine. I used ethernet with five HR2X's, two H21's and DirecTV2PX and didn't have any issues with network performance.
My response was your suggestion for powerline, which can be hit or miss depending on the environment. Some folks have had good luck with them, others never got a reliable MRV network due to any number of factors. Same goes for wireless networking, I was in the test group for the WGA600N support, some rooms worked OK, others nothing, even just moving the adapter a foot would make a usable connection not work.
So my point was why go out and spend $100+ dollars for a pair of wireless adapters, which might not work, or even more for another recommendation I saw which was go buy a wireless N router and wireless N adapter. Why spend that money on a solution that may not work, and won't be supported by DirecTV when you can spend $150 and get a solution which will work and will be supported by DirecTV?
To each his own I guess. Powerline networking has issues with multi-phase power and "dirty" lines, so yes there are problems. 802.11N can have interference problems just like all wifi variants. Again, just throwing options out there to avoid dealing with new dishes, new equipment, service calls, etc. To me avoiding all of that was worth it.
Another thing to think about: adding wifi to a house is something that has a lot of additional benefits beyond just getting a single DVR on the network. Paying DirecTV $150 will get the DVR on the network but it's a sunk cost.
Ended up just converting the cat5 phone line at that receiver to ethernet and added a switch to my distribution area. All three HR2Xs are now on the local network with MRV working between them.
I had MRV during the beta testing and was unable to get it to work properly. I have an HR24-500 and an HR 24-100 wired to Linksys 54G router. Everything worked except for one thing. I could not get recordings from the 24-100 but could get them from the 24-500 to the 24-100. I was bummed out and decided to forget it. Now I'm thinking of trying again. Has there been any more problems like the one I stated? Thanks for any info. Forgot, I have SWM antenna and SWM lines.
I have 8 recievers hard wire connected to my router, the MRV works perfectly but every now and then I loose complete internet access as my router and the 8 DVR's do not play nicely. It requires me to reset all 8 receivers then everything works perfectly, for this reason alone I am thinking of calling Directv to de the DECA install
What model of router are you using?
Called today as I just got another HD DVR and said "gee I didn't know when I got the second dvr I would have to pay another $150 to use Mrv?". The csr said "well I can activate the service if your dvr's are networked but remember it is not supported". I was surprised that she offered. All is working and this has to be the first time I was actually satisfied with the csr.
Sounds like you're using DHCP - Don't. Use static IP addresses, solves a lot of problems.
If you are already using static addressing, then I, too, would say it's probably your router that's not up-to-snuff.
If you have just the phone or cable company's router, there's not much you can do other than stick your own router behind it. Get yourself a good router, like one of the DLink GamerLounge or something similar with a gigabit ethernet switch built in, and then chain more gigabit switches from there if you need more ports in certain areas of the house. My setup works great with three people constantly on the internet, along with 4 DVR's, plus a whole lot of other stuff.
I went thorugh this just a couple weeks ago; They tried to do the truckroll and ding me the $99; I told them I already had hardwired ethernet and SWM installed. The CSR checked with her Supervisor and simply turned it on. It took a few minutes to get the hit, and then everything worked!
Nonsense! I have used DHCP with both DECA and Ethernet with no problems. MRV works, D*oD works and TVApps works. No UPnp, no port forwarding, no static / reserved / out-of-range / wacky IP addresses. Just a properly installed and configured system.
It is not nonsense. There appear to be some routers that are not playing nice with the DirecTV receivers. When the receivers are using DHCP addressing in these cases, some will drop off the network and do not reconnect correctly. The solution that has worked for these situations has generally been to use reserved DHCP addressing or static IP addressing.
So what routers don't work?
One that seems to give problems is the AT&T 2Wire. A few people have posted with issues with that one.
What I have seen though is that those with DD-WRT firmware on their routers do NOT seem to have these issues. Now that could be that those with DD-WRT firmware are usually a little more technically inclined, but I think it also has to do with the stability and strength of that firmware.
VOS praised the AT&T 2Wire as working perfectly with default settings; try again.
While he said it did, he then stated that he now has had some problems and another user also posted stating they had problems with it.
I'm not sure why it's difficult to believe that some people could have issues using DHCP on a correctly set up network. If a network is working fine and you plug in receivers that appear to grab their addresses correctly and then the receivers start dropping off there is a problem. When those same people have used static IP addresses, they then have no problem. If you do a search here, you will find plenty of posts where that has been suggested and has resolved the issue.
I myself used DHCP with no issues and then switched to reserved DHCP for maintenance issues.
Me neither. I had a router that did DHCP correctly about 95% of the time. But the other 5% it simply failed, and it was a big PITA to reset everything when it did fail. Once I went to static IP addresses, all the problems I had disappeared and I had solid connections.
Some consumer-grade routers also can't handle the constant heavy flow of traffic that is video streaming. They may work most of the time, but every once in a while you'll lose connectivity or have other intermittent problems.
So, for the record, what was the make and model of your router?
I used to have DHCP problems with my Netopia 3347NWG wifi router and my one wired (at the time) HR20. And while I will be the first to admit that I dont know everything, I was a network admin for 6 years and have been a programmer for 10. The configuration was fine, the HR20 would just occasionally head south and not accept the DHCP responses (as monitored by wire shark). I did eventually give it a static IP and haven't had it drop off the network since.