Separate names with a comma.
Discussion in 'DIRECTV Connected Home' started by DanDigital, Jun 20, 2010.
Wonder which one it will look like:
It'll be the one on the right .. I'm 99.999% sure of it.
So what you're really trying to say is "there is a chance". :lol:
there might be a reason its being sent from dtv. the lady who sent it said she wanted to be sure i got it in time for saturday's install and didn't think any of the contractors would have it in stock.
and if its the one on the left.........?
slide it right to make Doug right.....
Ok I unplugged the cat5 cord from the DECA and rebooted both receivers and everything works fine now (of course no ondemad/apps/remote programing) I gather the issue is with my router, I think it is set to obtain all the ip's from comcast (instead of internal 192.168.1.1) so it may have something to do with that. My plan is to plug another small switch into the existing router and plug the deca into that so it will give out internal ip's to the decivces on the deca system. I will let you know if that works. It baffels me why we can't just use the network connection in the back of the hr-24 for internet connection and have it keep its internal IP address and deca service for communicating mrv thru coax. I don't even see any purpose of having internet on the h24 since you only watch ondeman from the hr-24dvr its really the only box that needs internet.Why not let it have 2 concurent functioning network adapters??? How silly its supposed to be the lastest and greatest!
The reason is that the SWiM/DECA setup addresses the needs of the Ethernet/network connectivity, making the Ethernet port redundant (unless you use the HR24 in a non-DECA setup).
I'm not sure you could even do this and furthermore I'd think if you could this would cause even more problems.
Those that are having issues with MRV dropping out every 24 hours, sure seems like a router issue/problem.
As for using a receiver to do the bridging from DECA to ethernet, this simply would load the CPU up more, since the receivers don't have a network controller chip, so the CPU has to manage the traffic.
The H2x receiver currently use the internet access for TVApps. There may be other things now or in the future too.
[back to the router] I'm not sure if this is why I don't have any of these issues with my setup or not, "but" I reserve IPs for each receiver in my router by their MAC address. This keeps each receiver having the same IP address and have each receiver set to auto/DHCP, so anytime they reboot they always are assigned the same IP. Maybe this also keeps them on the same one when the router's 24 hour lease expires and it re-issues IPs. :shrug:
I wonder if it's an issue with DHCP renewal at 24 hours and the renewed address being different then what was assigned previously?
The more this gets kicked around, the more this [or something like it] seems to be it.
Maybe that or DHCP is only set to assign 5 addresses, but there are 6 devices. When the leases are renewed every 24 hours, one device is left out in the cold.
okay, just spent close to an hour with someone in ellen filipiak's office. it appears the lady in tech support i spoke with sunday night gave me false info....surprise. dtv will absolutely support the deca plus p1 installation. and i will probably get the wrong piece from fedex. i should get a call back in a little more than an hour after the rep does research and talks to experts.
at least, we are finally talking the same stuff and she admited the broadband deca looks like a router. whew.
I don't disagree with the tentative conclusion about IP address renewal issues, but requiring fixed IP addresses for DVR's would be a tech support nightmare.
All the more reason I use fixed IP addresses on all HD DVR and HD receiver devices within the IP range supported by my router. Never see any problems like those reported here.
+1 here as well;
I set my IP address range for DHCP to between 192.168.1.120 and above to the maximum the router will allow of 192.168.1.219. And all below this excepting the router's IP of 192.168.1.1 of course are reserved for static IPs to which the HD-DVRs, a network printer and some computers are all assigned.
Don't even use my ISP's DNS addresses either for the DVRs which the router uses, but one of the "Open DNS" standard of 188.8.131.52 or 184.108.40.206.
No connectivity problems so far with MRV or connections to the internet/home network cloud for DoD, TVapps, or Media Share.
While it should generally work the other way too...perhaps using fixed IP is a solid "lesson learned" alternative.
I agree with using fixed LAN addresses for those who know what they are doing, but think about the difficulty of DirecTV trying to provide tech support for all the possible router setups if fixed addresses are required to make MRV dependable.
Actually...having done it both ways at one time or another...fixed IP addresses seemed to simplify the process.
Once you know the range of IPs your router supports, simply assign IPs for each device in its network setup section/menu.
Then reboot the router.
So to see if this was making my setup work [or not], I've just changed them all back to being simply picked from the private pool.
I'll see in the next day or two whether this has any affect [or not].