Separate names with a comma.
Discussion in 'DIRECTV Connected Home' started by heebzman, Feb 8, 2013.
The hard wired one can't see the wireless:
So it works "half way".
Should I manually change the settings in DirecTV for the wired DVR to 255.255.0.0?
On a side note, it doesn't make sense to me, but when I'm in my router settings, I can see the family room DVR (the one that isn't working), but I can't see the bedroom DVR or the bridge that is connected via wifi. It still works though.
Manually changing anything takes the receiver out of DHCP mode, so only do this when you know what you're doing.
If it isn't working, manually entering settings hasn't ever worked for me.
255.255.0.0 is for when there isn't a DHCP router and the receiver use their internal 169.xxx IP.
Depends upon where you are looking...the bridge should be listed as a connected WiFi node (assuming your router has such a status page) but won't be listed as ethernet node. It is not unusual to not see the device connected to the bridge (only some routers detect the bridged device as different from the bridge itself).
have you tried selecting "Repeat Network Setup" instead "Restore Defaults"? I have seen a receiver get "stuck" with an error status unless you go through that step.
I have a DIR-655 and had to enable multicasting in the advanced tab. I had all kinds of problems until I enabled that.
Lots of smart people responding but I thought I'd chime in since the router appears to be the most likely suspect. Hope you get it working.
VOS:"Manually changing anything takes the receiver out of DHCP mode, so only do this when you know what you're doing. If it isn't working, manually entering settings hasn't ever worked for me."
I previously had this DVR on static IP with some of the settings manually inputted working with no problem.
I will try that. I think I have done it already, but it doesn't hurt to try again.
Putty469: "I have a DIR-655 and had to enable multicasting in the advanced tab. I had all kinds of problems until I enabled that."
I do have multicasting activated.
Thank you all for the suggestions. I'm hoping to take a crack at this again later tonight or tomorrow.
If you had recently reset the router, the DVR may not have renewed the IP address. Usually, when a router boots up it will poll the network to see what IP addresses are in use, but won't list an address unless it actually issues it to a DHCP client in response to a request/renewal. If the DVR was reset after the router and still doesn't show up in the DHCP list, that could indicate a problem with the router (though, I have also seen a number of routers that were a bit flakey about DHCP lists).
I re-ran the network setup and for whatever reason, it decided to allow my DVR to see the Internet. So I no longer have the 22 error, but my family room DVR still does not see the bedroom DVR; the bedroom DVR still shows the other DVR.
"It sucks", but this is why this type of networking isn't supported by DirecTV for MRV.
"odds are" it's your router causing this.
The few times my receiver has done this a simple reset/restart has it up and running, but I'm using DECA, with a WCCK to connect to my home network .
When I have problems like this, What I do is go to the router settings under dhcp server list(aka reserved list) and refresh the list and reboot the router, Then reset the network setup to each receiver (no need to reboot the receiver) by restoring default values to each receiver. Hopes this works for you.
Sorry, perhaps I wasn't clear. Yes they need to be on the same subnet. I was asking if you have other devices using your network, and whether or not you are having any issues with those. If you are, then the router could be the problem. As VOS said, try using a switch instead of a router to see if you can isolate the problem. In most situations, it is the router that causes problems.
Silly question, but have you reset the bridge?
I will try a complete router refresh (IP addresses & reset) and then re-run network information.
I'm not having any other network issues. Even the DVR that isn't working is actually connected to the Internet, gets VOD, Pandora and I was able to set a remote recording online.
I did reset the bridge and I was happy that that DVR continued to operate and see the other.
Again, thank you to everyone for suggestions. I will let you know how it turns out with the router refresh.
So clearly, the bedroom DVR is able to open a session with Pandora's servers, DirecTV's servers and the other DVR. However, the other DVR can not open a session with the Bedroom DVR.
I am not sure how DVRs register with each other for MRV - i.e., do the DVRs send an advertisement packet to announce themselves, or does each DVR poll the network and wait for the others to respond.
In any event, it would appear that either the bedroom DVR's advertisement, or the poll/response session, is not getting through the bridge.
What is the make and model of the bridge? Does it have any configuration options regarding bridge mode? Does it have any security features?
I'm not exactly sure what I did, but the family room DVR sees the bedroom DVR. Last night I released/refreshed IPs and I think reset the router (to the best of my knowledge it didn't work). Today I unplugged Cat5 cord from the bridge (Trendnet) to the bedroom DVR and plugged it back in (I had previously done the power cord). It works now, which is nice. Whenever we get around to moving this year, I'll make sure I get DECA installed in the next house.
Thank you to all for the help and suggestions to fix this problem.