Separate names with a comma.
Discussion in 'DIRECTV Connected Home' started by The Merg, Oct 23, 2010.
Yes, I thought that was what I said but if it wasn't then it was what I meant to say!!! :lol:
Nice to see fellow DBSTalkers helping each other out at every turn.
I agree that in the end...static IP, especially with the router in control of always assigning a particular IP address, results in very stable network performance and reliability. That's been the case here for quite some time.
Static IPs are the way to go. Been that way from day one and never had a problem since.
Just one note, not all routers have the ability to reserve an IP to a MAC address. The Actiontec Q1000 from Qwest does not have this capability. It's Static IP form the device or full DHCP.
watch for this as I have seen it listed as static even when not, I had 2 hr20 I had to actually reboot to clear this.
OK, I'm totally perplexed as my MRV has never worked flawlessly through two different routers (the current one I'm using has been mentioned here as working flawlessly, DIR825 by D-Link). I have three HR21s and an H21. One HR21 is hardwired to my DIR825, on HR21 is bridged using an older Buffalo G-Router and WWDRT firmware (or whatever it's called). The other HR21 and the H21 are bridged using the common Linksys gaming adapter that is recommended by DirecTV. All devices have worked with OnDemand, TVApps and even PlayOn. I'm using unsupported (via ethernet) MRV. They symptoms I usually see is either I don't see ANY devices, or, I see the other devices for a short period of time, but they usually disconnect fairly quickly. The setup I had before reading this thread was using DHCP but having the router assign the same address to each device when the lease was up. And in advanced setup on the D* boxes I typed in the IP. As a security precaution I always change the router's default IP. In this case, the router's IP is now 192.168.0.100, and DHCP range was 192.168.0.101 - 192.168.0.200 (a range of 100 IPs). After reading this thread last night I changed the DHCP range down to .150 and assigned the boxes to out of range IPs in sequence from .151 using the advanced network setup on each box. The boxes all accepted the IPs and all other networking functions work correctly, but MRV is still a no go. Any suggestion? As an aside, I have various networked devices connected to the router via DHCP (assigned addresses via MAC) that work flawlessly including a Vonage adaptor, Sony networked BD player and various computers both hardwired and wireless. Right now, I'm paying the MRV fee for basically a useless service.
Other notes, when MRV does work, FF a show tends to cause it to lose connection. I THINK (but I forget) that I have have uPnP ordered so that the Vonage box gets priority and then the HRs get the next level of priority. Anyone have luck with setting it up that way?
This all underscores why DirecTv offers a SWiM/DECA delivery and does NOT support other network configurations. There are simply too many potential configuration and connectivity variables when compared to the DECA delivery that is virtually plus-and-play. While some have had success, others have not...using the non-supported network setups.
So your suggestion is to get the supported version and DECA? Seems from reading here, that there are all kinds of issues with that as well. I don't want to invest the money (and have to change my heritage programming plan) if this won't work flawlessly.
Can anyone point me to the prices for doing DECA?
SWiM has been working here for almost 2 years...and DECA since it was in beta testing...no problems whatsoever.
Here's the best answers around how to do WHDS/MRV:
Hmmmmm...isn't this thread about problems?
Anyway, thanks for the info.
Its an FAQ thread.
The only "problems" I have seen relate to early installations where some sites had improper setups done or training was too new and errors made. Once this got rolled out mainstream...proper installations have been quite solid.
I set up this thread as a discussion for those with issues with Whole Home and how static IP addresses can help to resolve that issue. It was meant for those that have supported MRV.
In your situation, you state that you have unsupported MRV (ethernet). I would gather that most of your issues are stemming from the fact that you are connecting almost all of your receivers wirelessly. The Linksys adapters you have, while good, were initially sold by DirecTV to allow a user to connect their receiver to their network for DOD purposes. The intent was not to use them for MRV.
If you can, try to hardwire your receivers and see if the issue persists. If it doesn't I would gather that the issue is stemming from your wireless connections. If you can't hardwire the receivers, that is all the more reason to switch to a DECA setup as one of the benefits is that you get a hardwired setup without having to run CAT5 throughout your house.
A Static IP Address technically is one that Never Changes and even though I am telling the DHCP Server to Always Assign the Same Address if it doesn't change then it is Static even though we know it is not what we would technically refer to as a "True Static Address" than once it is Assigned it Never has to be Reassigned.
I refer to it as being a Quasi Static IP Address!!!
*Duct tape not included
Thanks. My only concern is that since this thread is about the supported MRV that there ARE issues. I just don't want to invest the money (which I probably will do, as I'm at my wits end with this now), and still run into similar issues. The initial outlay of $150 is a bit steep so that's why I'm trying to get things working without it. Unfortunately, hard wiring is not an option as the work involved in doing it isn't worth it, and at that point, might as well just do DECA.
Isn't DECA and supported MRV one in the same?
SWiM and DECA are part of the Whole Home DVR Service (WHDS) - also known as MRV - solution. I suspect you'd find that 99% of implimentations are working quite well at this time. There were some "launch hiccups" for some early installs.
While there do seem to be some quirks with Supported MRV (DECA), it is a very stable setup. This thread and the sticky FAQ on static IP addresses really address the main issue. Plus, once set up with static IP addresses, I don't believe there has been anyone that has had an issue at that point.
Since I've been using DECA for over a year, it has been basically "bulletproof", and most/all issues have been with the internet/router connection, since there isn't a "standard" router.
DHCP has worked for some and for those with problems, static IPs have resolved this if they're outside of the DHCP pool. "Maybe one user" hasn't had this resolved by using static, but even with that one, they simply added a second old router they had and connected it to their wireless router for the DECA network. This resolve their problems.
If hard wiring isn't a good option, then DECA is the only way to go.
Are your wireless adapters G or N? See if your router shows signal strength. You may have sufficient bandwidth for TVapps or VOD but not for MRV. But generally they should show up but just have 'no packets' type of error unless there's something else going on on the net.
I had two HR2x on wireless N before DECA with no problems, but I went to DECA when I added an additional HR that put me over 8 tuners and required a SWiM 16.
You need a DECA module for each H or HR and one with a PI (power supply) -also known as Internet Connection Kit or Cinema Connection Kit. Probably < $100 on eBay or $149 or $200 (recent quotes) installed from D. This also assums you have SWiM. If not the D price becomes more attractive.
my adapters and the router are both N.
So based on your prices, would that mean I'd need to buy a DECA module for each HR (and H) which means 4 altogether? (actually I have one "off network H21, so I'd probably do 5). At even $100 a pop, that's a lot of mullah to lay out. It was my understanding that it was $99 plus $49 for installation for the "whole home solution". Is that not correct?