[Duke3K]

So... the question is: From a Whole Home perspective-should my H24 be able to see my HR24 in this setup? Apologies for the crappy diagram.

With the current configuration as shown the H24 CANNOT see /or remote play anything on the HR24 .

The H24 can see and remote play the HR34 fine.

But the new HR34 can. It remote plays just fine anything recorded on the HR24.

Background:
(1) Recently upgraded to the HR34 and before that upgrade the HR24 was located & connected exactly the way the HR34 is now. The H24 before the upgrade remote played the HR24 just fine .

(2) As part of the upgrade - I moved the HR24 to an outbuilding that has it's own seperate Dish - but from an ethernet backbone perspective is wirelessly bridged to our main house and is on the same network as all the other D* H/W.

This is really not a big deal - I'm just curious if it should work and if it's not supposed to - how come my new HR34 can remote play the HR24 just fine.

My D* installer said that none of the main house units would be able to remote play the HR24 - so I was pleasantly suprised when the HR34 could - but puzzled as to why the H24 would not.

Thx
Duke

 

[Go Beavs]

Sounds like the H24 is more sensitive to the wireless hop than the HR34. Using wireless with MRV can be very flaky. Some people have had better luck with the clients being on the wireless side of the network, ie. move the H24 to your outbuilding and swap it with the HR24.

Are you getting errors on the H24 or does it not see the HR24 at all? Also, why are you using a CCK on the HR24, why not just plug the Ethernet cable from the wireless bridge directly into the HR24?

 

[veryoldschool]

If the HR34 is seeing the HR24, then the H24 "should" too.

 

[dpeters11]

I'm with Go Beavs on this. When I had one unit wireless, I had trouble going one way with MRV, going the other way (both were DVRs) always worked. At least for testing, I'd swap the HR24 and H24 and see if there's any difference.

But even with that, it should see the list of recordings on the HR24.

 

[veryoldschool]

Sounds like the H24 is more sensitive to the wireless hop than the HR34. Using wireless with MRV can be very flaky. Some people have had better luck with the clients being on the wireless side of the network, ie. move the H24 to your outbuilding and swap it with the HR24.

Are you getting errors on the H24 or does it not see the HR24 at all? Also, why are you using a CCK on the HR24, why not just plug the Ethernet cable from the wireless bridge directly into the HR24?

I'm with Go Beavs on this. When I had one unit wireless, I had trouble going one way with MRV, going the other way (both were DVRs) always worked. At least for testing, I'd swap the HR24 and H24 and see if there's any difference.

But even with that, it should see the list of recordings on the HR24.

Since they're using DECA, the wireless hop/link "should be" the same for both the HR34 & H24.
Whether it plays recordings well or not, is another issue.

 

[dpeters11]

DVRs don't buffer MRV content at all, right?

 

[veryoldschool]

DVRs don't buffer MRV content at all, right?

They don't anymore than a receiver, which is only a few seconds worth.

 

[Go Beavs]

Since they're using DECA, the wireless hop/link "should be" the same for both the HR34 & H24.
Whether it plays recordings well or not, is another issue.

In the early days of MRV testing, I was using a wireless bridge on one of my DVRs and it would always have more trouble being a server rather than a client.

The only difference I saw (with limited testing tools) was that the latency was higher from the bridge to the access point. Latency from the access point to the bridge was less and since my troubles happened (mainly) during trickplay, I figured it was a timing issue. That's what makes me think that the HR34 may be less sensitive to timing issues than the older hardware.

 

[veryoldschool]

In the early days of MRV testing, I was using a wireless bridge on one of my DVRs and it would always have more trouble being a server rather than a client.

The only difference I saw (with limited testing tools) was that the latency was higher from the bridge to the access point. Latency from the access point to the bridge was less and since my troubles happened (mainly) during trickplay, I figured it was a timing issue. That's what makes me think that the HR34 may be less sensitive to timing issues than the older hardware.

I understand what you're saying, but playback is one thing, while "finding" other receivers should be something else.

If the wireless link was the problem, then the HR34 would be affected too.
This looks more like a problem with a switch, than the wireless hop/link, and maybe a port or MAC address issue.

 

[Go Beavs]

Agreed.

We need to find out if the OP's H24 can actually see the HR24 and is just getting an error message or if it doesn't even show up the the WHDVR status screen.

 

[Duke3K]

Additional info:

(0) Took the CCK out of the picture. the HR24 is now direct ether connected to the Wireless N repeater shown in the diagram.

(1) Rebooted all the recievers - no change.

(2) the H24 cannot even see the HR24 - i.e. if I go into - Settings->Whole Home-> Status: Under Network DVR's - only the HR34 is listed.

(3) However the same screen on the HR34 - shows the HR24. Which makes sense - since as I said - I can play just fine (no issues) recorded material sitting on the HR24.

(4) Directv2PC - running this program on my PC (from the main house ) I can see both receivers and play content off the HR24. Oddly enough tho - it is not showing me the recorded content on the HR34 - It connects to it but says their are no recorded programs. This sounds like a different problem.

(5) Directv Nomad. The Nomad shown in the diagram can only see the HR34.

(6) the HR24 can see & Play content off of the HR34.

I'm starting to think that the comments about wireless network may be the culprit. I've got a long ass ether cable and I may just temporarily direct connect the outbuilding to home network just to confirm.

the suggestions about swapping the hr24 location with the H24 - I don't really want to do - I'd like to leave the local dvr in that outbuilding.

thx for the comments so far.

 

[Duke3K]

Just for grins I just did a simple ping command from my PC in the main house to the HR24. No packet loss -and very low latency on average - however every 10 pings or so it would rise to 30ms .


Pinging 192.168.2.52 with 32 bytes of data:
Reply from 192.168.2.52: bytes=32 time=2ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=6ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=30ms TTL=64
Reply from 192.168.2.52: bytes=32 time=2ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=3ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=29ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64
Reply from 192.168.2.52: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.2.52:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 30ms, Average = 3ms