1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Welcome to the new DBSTalk community platform. We have recently migrated to a community platform called Xenfono and hope you will find this change to your liking. There are some differences, but for the most part, if you just post and read, that will all be the same. If you have questions, please post them in the Forum Support area. Thanks!

Directv DECA DOD NETWORK PROBLEM

Discussion in 'DIRECTV Connected Home' started by epifano83, Aug 1, 2010.

  1. Aug 1, 2010 #1 of 28
    epifano83

    epifano83 Mentor

    44
    0
    Oct 5, 2008
    Ok here's my problem, on 07/27/2010 I had a tech roll out and install MRV upgrade plus DOD through the deca to my network, I currently have HR24-100, HR23-100, HR22-100.
    My current broadband provider is WB and I have that hooked up to my netgear WPN824 wireless router.
    Well anyway when my DECA adapter is connected to my home network after 3hrs my router will hang if i put any of my wireless devices in standby and try to bring them back up on the network I cant get connected unless if I reboot the router. But if I disconnect my deca adapter it will not hang any more after I reboot the router of course.
    I tried putting a fixed ip address on each receiver but no luck, I also tried messing with some other settings but no luck on that either.
    Has anyone ran into any of the same issues? How did you resolve it?
    Or is there any suggestions or tips it would be greatly appreciated.
    Thank you all for your time!
     
  2. Aug 1, 2010 #2 of 28
    Doug Brott

    Doug Brott Lifetime Achiever DBSTalk Club

    28,939
    72
    Jul 12, 2006
    Los Angeles
    What you are describing sounds suspiciously similar to what happens when you use both Ethernet ports on the HD DVR (those that have 2 ports).

    You should have one DECA module that is connected to your SWiM network (the coax cable) and your your router with a power insert connected to the tail.

    Then you should have one DECA module for the HR22-100 and the thing you call an HR23-100 (that model doesn't exist). The Ethernet cable from that DECA will attach to the same DVR and there should be NO OTHER Ethernet cable connected to those boxes.

    If all of that is correct, then you may have some other problem.
     
  3. Aug 1, 2010 #3 of 28
    Doug Brott

    Doug Brott Lifetime Achiever DBSTalk Club

    28,939
    72
    Jul 12, 2006
    Los Angeles
    A good test is to run the system test on each machine as well to see if any problem is detected. Press & hold {INFO} and when the menu appears, select "run system test"
     
  4. Aug 1, 2010 #4 of 28
    epifano83

    epifano83 Mentor

    44
    0
    Oct 5, 2008
    I tried the system test last night but everything came back as normal, still scratching my head!
     
  5. Aug 1, 2010 #5 of 28
    veryoldschool

    veryoldschool Lifetime Achiever DBSTalk Club

    42,649
    338
    Dec 9, 2006
    Don't know enough about your router to be of much good, "but" this does sound like a router setting issue. It may be happening now because you've added all of your receivers and this [the number of devices] is what's causing this.
    What Doug described about connection to the wrong port on the receiver only did this [rebooting router required] when the receiver would stop responding during a download of firmware. Simple reboots didn't trigger this.
    Instead of using fixed IPs in the receivers, can you reserve IPs by MAC address in the router? I have done this [though not doing it now] and this keeps the IPs fixed, but the receivers are all set to auto [DHCP]. Just some thoughts.
     
  6. Aug 2, 2010 #6 of 28
    epifano83

    epifano83 Mentor

    44
    0
    Oct 5, 2008
    Opps that would be a Typo its not a HR23-100 it is a HR23-700. Thank you for pointing that out!
     
  7. Aug 2, 2010 #7 of 28
    epifano83

    epifano83 Mentor

    44
    0
    Oct 5, 2008
    I changed my IP for the receivers in my router last night and it seems to be working! FINGERS CROSSED!
    I will keep you all updated if it's still working when I get home for launch, if it is I'am assuming I should not see no more problems with this issue.
    It was driving my wife up the wall to have to constintly reboot! LOL!!!

    Thanks for your inpute :) :)
     
  8. Aug 2, 2010 #8 of 28
    epifano83

    epifano83 Mentor

    44
    0
    Oct 5, 2008
    No dice I had to reboot the router :(
     
  9. Aug 2, 2010 #9 of 28
    epifano83

    epifano83 Mentor

    44
    0
    Oct 5, 2008
    what kind of router has everyone been using for this service? What do you have connected and how has it worked out for you?
     
  10. Stuart Sweet

    Stuart Sweet The Shadow Knows!

    37,060
    287
    Jun 18, 2006
    To answer your question, I'm using a Linksys WRT310 running DDWRT.

    I think Doug Brott was on to something in post #2. Could you describe the way all of your receivers are connected to the internet? I think there's something there that's not wired right.
     
  11. epifano83

    epifano83 Mentor

    44
    0
    Oct 5, 2008
    The way as he described how it should be hooked up is the way I have it wired, I just wish I knew what setting is off or if I replace the router it would work for sure!:confused:
     
  12. Yog-Sothoth

    Yog-Sothoth Legend

    102
    0
    Apr 8, 2006
    Are you running the latest firmware for the router?
     
  13. epifano83

    epifano83 Mentor

    44
    0
    Oct 5, 2008
    I downloaded the latest version yesterday afternoon, still nothing on that.
     
  14. armchair

    armchair Hall Of Fame

    1,188
    0
    Jul 27, 2009
    There was another poster that said he enabled mulicast packets and it fixed a problem with UPL not updating. Your problem sounds more serious.

    Do you have a network switch placed in front of your router? If you'll notice the top DECA in Doug's description shows the broadband DECA connected to a network switch but the implied router is missing. http://www.dbstalk.com/showthread.php?p=2472595#post2472595
     
  15. epifano83

    epifano83 Mentor

    44
    0
    Oct 5, 2008
    I finally corrected the problem by replacing the unit with a new wireless router and every thing has been working great since then :)
     
  16. 901racer

    901racer Mentor

    46
    0
    Jan 8, 2011
    I have three wireless routers/bridges for coverage in my home. Linksys E4200 is the main router/wireless and is the one handling DHCP and connection to my cable modem.

    WRT160N and WRT610N bridged to the E4200. This is for Wireless coverage.

    I am running my BB Decca connection to the WRT160N which is bridged to the E4200 with no problems.

    I did see the receivers drop from the deca cloud when using MRV and DHCP addressing for D* equipment. Fixed IP address for everything D* has fixed any problems I had. These network devices from d* are the only ones I have seen that have DHCP lease problems. I believe it to be a problem with the Deca network or the revievers handling of DCP leases.

    If you have another router or bridge laying around you might want to try that to isolate the problem. Just FYI, I tried a WNDR3700V2, but because of general firmware issue (slowdowns, hangs) had to return it and move to the the E3200 which is working very well.
     
  17. veryoldschool

    veryoldschool Lifetime Achiever DBSTalk Club

    42,649
    338
    Dec 9, 2006
    While it can sure look like this, I think there is a bit more to it, since some routers and DECA play very well together with DHCP.
    "Generally" wireless routers and fairly active wireless networks seem to have more problems than non wireless routers.
    I think we might see a new BB DECA coming out that may address this better.
     
  18. 901racer

    901racer Mentor

    46
    0
    Jan 8, 2011
    VOS, I thought the BB Deca was just a layer 2 connection device ethernet<->COAX.

    I have run ethernet<->BB Deca<->COAX<->BB Deca<->ethernet as a bridge instead of a hardwire or PoE device and works really well without any DHCP lease issues on either end with a multitude of wireless and wired devices.

    Only issues I have seen is with the D* equipment Deca network. I believe it is something in the SWiM network or the equipments(receiver) Deca or networking firmware bug. I would assume the devices firmware is the stack requesting the DHCP lease and respond to the the DHCP server on the network.

    Has anyone done a TCPDump trace of this problem to understand who may not be requesting lease extensions or not responding?

    I can do this, but would rather not if the real :rolleyes: problem is already known and a real fix is in the works.

    Just a thought...
     
  19. veryoldschool

    veryoldschool Lifetime Achiever DBSTalk Club

    42,649
    338
    Dec 9, 2006
    Engineering has done this. It has nothing to do with the SWiM, since there is no interaction between SWiM & DECA.
    This seems to have more to do with MRV and "something" as to requests/polling the network and responses from the router. "The lease" seems to always get renewed, but some aspect of it doesn't.
    This level of networking is a bit over my head as I'm an RF guy.
    The DECA cloud basically works like a [large] switch and on my system has been very stable "until" I activated the wireless part of my router. Then I got to see what many others had been posting and changing over to static IPs, outside of the DHCP pool, stabilized everything again.
    I can't really go into what I know, but will say there are "things in the works", that should help resolve these issues.
    Until then though, static IPs for those with problems should help and with the few that it hasn't, using an old router connected to the wireless router has helped keep the receivers working for MRV while having all the wireless devices working too.
     
  20. 901racer

    901racer Mentor

    46
    0
    Jan 8, 2011
    Good glad they know what is going on and sounds like this will resolve itself over time.

    Most often in real world networking, implementing something to the specification and what has to be done in the real world is completely something else. Usually a compromise that really does not follow the specification.
     

Share This Page