Contributor
•
2 Messages
Networking collision causing playback problems? (resolved)
This is just an FYI in case anyone else runs into a similar experience.
Multi-room was working great for about a week and then experienced a hiccup until last evening. My connection between the DVRs (HR22/100 and an HR23/700) was acting intermittent, I could start playing a show but it would cut out after about a minute or so and then the connection would be dropped. Sometimes the programs would show in the guide, sometimes not.
I tried all of the common suggested solutions (resetting, waiting, etc.) but none of the solutions applied -- the same behavior continued.
Yesterday, I disconnected the networking cable and started a network diagnostics which forced the HR22/100 to hit an error condition with the network. After reconnecting, and going through Network Setup again, the HR22 picked up a new IP (192.168.1.23) from DHCP. I ran all diagnostics again and then tested multi-room -- all was good.
As it turned out, this particular HD-DVR was the only one on my network that I had not assigned a reserved IP.
I suspect that the lease on the IP for the HR22/100 had expired but it was still holding on to an expired IP (192.168.1.17) and was in conflict, once the proper IP was in use, then the networking conflict was resolved.
I'm not sure if this particular networking example for DHCP assignment has been thoroughly tested with DirecTV but something to watch out for.
Multi-room was working great for about a week and then experienced a hiccup until last evening. My connection between the DVRs (HR22/100 and an HR23/700) was acting intermittent, I could start playing a show but it would cut out after about a minute or so and then the connection would be dropped. Sometimes the programs would show in the guide, sometimes not.
I tried all of the common suggested solutions (resetting, waiting, etc.) but none of the solutions applied -- the same behavior continued.
Yesterday, I disconnected the networking cable and started a network diagnostics which forced the HR22/100 to hit an error condition with the network. After reconnecting, and going through Network Setup again, the HR22 picked up a new IP (192.168.1.23) from DHCP. I ran all diagnostics again and then tested multi-room -- all was good.
As it turned out, this particular HD-DVR was the only one on my network that I had not assigned a reserved IP.
I suspect that the lease on the IP for the HR22/100 had expired but it was still holding on to an expired IP (192.168.1.17) and was in conflict, once the proper IP was in use, then the networking conflict was resolved.
I'm not sure if this particular networking example for DHCP assignment has been thoroughly tested with DirecTV but something to watch out for.
No Responses!