Welcome to DBSTalk

Welcome to DBSTalk. Our community covers all aspects of video delivery solutions including: Direct Broadcast Satellite (DBS), Cable Television, and Internet Protocol Television (IPTV). We also have forums to discuss popular television programs, home theater equipment, and internet streaming service providers. Members of our community include experts who can help you solve technical problems, industry professionals, company representatives, and novices who are here to learn.

Like most online communities you must register to view or post in our community. Sign-up is a free and simple process that requires minimal information. Be a part of our community by signing in or creating an account. The Digital Bit Stream starts here!

I'm going crazy with having to reboot my router every night to have access to Nomad and DirecTV2PC. I have read numerous fixes involving using static IP, but how do I set that up? For once, I'd like to come home and find both the Nomad and DirecTV2PC working on its own. I should note that when this happens, my PC can see the DVRs and the nomad can see the DVRs, but it can't access them.

As far as I know, there is no way to set a static IP address directly on the nomad. What you can do though is assign an IP address to the nomad via your router. On the router side, you have two options. You can set up DHCP Reservations, which just has the DHCP server on the router assign the same IP address every time the DHCP lease needs to be renewed. The second option is to use the MAC address of the nomad to have the router assign a static IP address to the nomad. This would be an IP address outside of the DHCP range.

The only reason I have had to use static IPs is when I was using a WRT160N router and the DHCP server would sometimes stop working or when I wanted to forward a specific port on a router to a specific client.

To me that sounds like an issue with the router. You might try flashing with DD-WRT or other third party firmware.

I'd second that.

I've switched all my routers over to DD-WRT and use DHCP Reservations for all my network devices. I've never had a problem with a device dropping off the network and have never had an issue with MRV, for which DHCP Reservations/Static IP Addresses is a solution for when people have receivers dropping off the network.

To me that sounds like an issue with the router. You might try flashing with DD-WRT or other third party firmware.

This will probably void your warranty if you brick it somehow. Try setting a static ip first. You want to change the DHCP range to start at an address higher than what it is now. Figure out what your DNS addresses are and choose an address that comes before your dhcp range. Your subnet is probably 255.255.255.0.

I'm not familiar with the nomad but try opening network explorer to see if its host name is listed in there. If it is listed try opening that in your browser like so http://hostnameofyournomad. If it brings up a log in dialog or page then you should be able to set up a static ip for it with the information you gathered from above. You'll just need to figure out what the username and password is.

This will probably void your warranty if you brick it somehow. Try setting a static ip first. You want to change the DHCP range to start at an address higher than what it is now. Figure out what your DNS addresses are and choose an address that comes before your dhcp range. Your subnet is probably 255.255.255.0.

I'm not familiar with the nomad but try opening network explorer to see if its host name is listed in there. If it is listed try opening that in your browser like so http://hostnameofyournomad. If it brings up a log in dialog or page then you should be able to set up a static ip for it with the information you gathered from above. You'll just need to figure out what the username and password is.

There is no user interface on nomad. The closest thing you can do is set a reservation in DHCP.

With DD-WRT you can easily set that reservation outside of your normal DHCP range.

dd-wrt is now pretty foolproof. . . they even have loads to reload your original firmware if you need to go back. It will probably solve this and lots of other problems if your router supports it.

I've switched all my routers over to DD-WRT and use DHCP Reservations for all my network devices. I've never had a problem with a device dropping off the network and have never had an issue with MRV, for which DHCP Reservations/Static IP Addresses is a solution for when people have receivers dropping off the network.

- Merg

Like me

Have to use static IP here. DHCP is not reliable for the networked DIRECTV boxes on my router, a old Linksys WRT330N "Gaming Router." One or more receivers were seemingly always dropping off the network.

And can't install DD-WRT firmware on the router either. It uses an "Ubicom" processor with a strictly proprietary instruction set. A third party Linux firmware like DD-WRT is not compatible with it.

But static IP is working fine except for the HR34 which while increasingly rare, still drops off the net from time to time even with a static IP.

The only reason I have had to use static IPs is when I was using a WRT160N router and the DHCP server would sometimes stop working or when I wanted to forward a specific port on a router to a specific client.

Ya. If and when Nomad ever allows streaming outside the home, one way to facilitate this is to fix Nomad's IP address with a router reservation and then set up port forwarding in your router for that address, so Nomad can get out to the internet.

The other way is if Nomad and your router are fully UPnP compliant, in which case it wouldn't matter what Nomad's IP address was, because the router could simply forward ports on demand, based on whatever LAN IP the UPnP request came from. We'll have to see how well that works, tho, if that's the plan.

I should note that when this happens, my PC can see the DVRs and the nomad can see the DVRs, but it can't access them.

As far as the OP, I'm not sure what's going on there. If Nomad can see the DVRs, then it's not an IP address issue. Could be a permissions issue on the HRs. If you haven't already checked, first place I'd look is under "settings, whole home, external device", to make sure access is allowed.

Ya. If and when Nomad ever allows streaming outside the home, one way to facilitate this is to fix Nomad's IP address with a router reservation and then set up port forwarding in your router for that address, so Nomad can get out to the internet.

The other way is if Nomad and your router are fully UPnP compliant, in which case it wouldn't matter what Nomad's IP address was, because the router could simply forward ports on demand, based on whatever LAN IP the UPnP request came from. We'll have to see how well that works, tho, if that's the plan.

As far as the OP, I'm not sure what's going on there. If Nomad can see the DVRs, then it's not an IP address issue. Could be a permissions issue on the HRs. If you haven't already checked, first place I'd look is under "settings, whole home, external device", to make sure access is allowed.

Access is allowed. I have noticed that while the app will show me both DVRs, I cannot "hide" either of them when this is going on. I can only "hide" a dvr in the app when it is fully functioning with the Nomad.

To me that sounds like an issue with the router. You might try flashing with DD-WRT or other third party firmware.

I am concerned with screwing up the rest of my network. I have 7PCs, four iPhones, three tablets, a Blu Ray, an XBOX, all working perfectly on the network. The only thing that I have problems with are the DVRs and Nomad.

Access is allowed. I have noticed that while the app will show me both DVRs, I cannot "hide" either of them when this is going on. I can only "hide" a dvr in the app when it is fully functioning with the Nomad.

Sounds like a handshake issue between Nomad and your DVRs. Have you tried a 30-second reboot of the Nomad? If you haven't already done it, press and hold the front-panel red reset button for about 35 seconds. You won't lose any transcoded content, and that might just fix it for you.