Separate names with a comma.
Discussion in 'DIRECTV Connected Home' started by E91, Sep 28, 2010.
What are the & > buttons?
Press the Guide button and the right arrow button on the front of the DVR at the same time.
Another little "tidbit" is that when receivers lose connection [gets interrupted] it can leave the receivers in a strange network state. I just had to go to each receiver and either reboot it or run the network test [or both depending on the order of which receiver had what done to it] to clear out some glitches. We've seen this before in the early days of MRV, when the network hangs and leaves a receiver hung up.
Looks like this:
0 Upstairs: N/A
1 Node001xxxx: 25
2: Downstairs: 25
Dropped Sessions: 3
With exception of the dropped sessions; those values are good. It will take time to clear the dropped sessions to zero if the problem is resolved.
You still need to run the bit-rate test. Click the Phy rate mesh tab.; return values s/b GT 215 but I'd suspect higher (max is about 253).
You guys rock.
You can also run coax diagnostics on the other HR24 to determine the node loss of the node that returned the N/A value of the HR24 from your first test.
I was having intermittent problems until I did what I should have done lone ago, get the modem and router on different IP ranges.
Using ATT DSL
Att modem is 192.168.0.1
Router is 192.168.1.1
NOTE: The third number needs to be different...
If need be, when I get home I can lay out my entire setup...
IIRC the router is handling DHCP, with the exception of a couple of wireless items (printers, DSi) which I gave static IP's to, outside the DHCP range.
The likely culprit for me was the modem and router fighting for certain chores. As I remember it, by changing the third number they became separate networks (so to speak) and no longer have any conflict issues.
I found the clues by searching for information on using a DSL modem with a second router. I did not want to use bridged mode since I would like to be able to plug computer directly into modem if need be, so the different IP ranges was the easiest option.
Yeah, the above posters basically got me doing something similar. I have the HR24s on Static IPs that are outside the 2Wire's DHCP range. Things seem to be working better now, but we'll see how it goes over the next few days.
Interestingly, D*'s position is that ICK and DECA are completely unrelated.
In any case, I got more information from one afternoon at this site then I have gotten after days of call D*.
My conclusion is it is not a D issue at all.
Modem, Router, Deca - getting two of the three to play nice is easy. Adding a third playmate (or more) is the problem.
We read here Deca creates a separate "cloud" for MRV. I will go with that term for (I hope) clarity.
In your setup (and mine at present):
Modem needs to connect to internet.
Router needs to connect to modem and create and manage "cloud" for local internet usage (computers, receivers, etc.)
Deca creates and manages "cloud" for MRV, and can connect to router for VOD.
The missing piece was to make sure modem and router were not sharing the same "cloud"... they should not share the first three parts of their IP address. It avoids conflicts with data transfer (speed) and "addressing" (if DHCP is not perfectly handled).
What you are saying makes sense, but that is no what D* will say if you call to describe MRV problems. Their position is that the internet connection and DECA are unrelated.
And technically, DirecTV is correct. The DECA Cloud is independent of the rest of your network in the sense of how MRV works, however, the IP address the receivers receive comes from your router and allows you access to the rest of your network and the Internet.
So while, the receivers might depend on the ICK and your router for the IP address if you want access to the Internet, DECA (and MRV) itself don't need the router as the receiver can assign it's own IP address if the ICK is not connected. In that sense, DECA maintains itself.
Just to let you know, it seems what you are calling a Modem in your setup is actually a Modem/Router combination. You may already know that, but just wanted to state it for clarity of others that may review this thread. (It is possible to have a modem without a router built in.)
The problem in your setup was with the router part of the modem/router. Having more than 1 router in your home network can be problematic if you don't know what you are doing. (As you have found out.) Creating different subnets as you have done (changing the 3rd position of the IP address) is a good solution.
Those that don't have a router built into the modem, or otherwise have more than one router, shouldn't have your problem.
Thanks DogLover. I was wondering if that what the issue was there as I couldn't think of how a modem was getting it's own IP address on the local network. And then even if it was a modem/router, I still couldn't think how that was working. A second router... Aaahhhh.... I need to get more sleep.
My setup actually has two routers, which is probably part of the problem. I have a DSL Modem/Router in my home officer that passes signal through my home's internal wiring. It hits a router upstairs in the entertainment center. There, I have signal going to my TV, Roku box, PS3, and HR24.
So, Merg's comments above make good sense to me.
OK. That will be a complicated setup then, especially if both of them are set up to give out DHCP addresses. Setting up separate subnets is a not for the networking faint of heart.
Life would be sooooo much easier if you simply used a switch upstairs.
That's what I was thinking.
Another option w/b to use the router upstairs as a switch. Turn off DHCP server and use LAN ports only. Some routers will allow the WAN to be re-assigned as a LAN port.
Yup. Make sure only one of the routers is being used as a DHCP server. That will usually resolve most issues.
ATT's calls them DSL modems for the non-wireless, or Wireless Gateway for their wireless box.
Good point about writing for prosperity...
Whether we like it or not, anyone with more than a direct connection eventually becomes their own network admin!