I just got off of the phone with "technical" support. We tried every "trick" that she had to get the receiver connected to the internet to no avail. Of course I tried everything that she suggested before I even called but no dice. I'm connecting via ethernet, she insisted that I needed to buy a cinema connection kit (note that it was connected a week ago, the last time that I used the receiver's DOD services.)

I tried setting static IP address, setting the correct subnet, correct DNS, correct gateway, resetting the receiver...still nothing. The dhcp client in the receiver returns a 169.254.8.1/16 (255.255.0.0) with no fields set in the DNS or gateway settings. I unplugged the ethernet (while on the phone) from the receiver and plugged into my laptop, connection was present with no problem. I'm starting to believe that the receiver itself has some issues since it's the only component having issues connecting.

The connection is directly coming from my AT&T Uverse Modem (Motorola NVG 510) via ethernet. I tried to port forward the receiver's ports that it uses, but the profile that I created for the receiver cannot be assigned to the receiver because it isn't connecting even to my local, private network.

Try Peds48's instructions with one twist. "MENU ➜ SETTINGS & HELP ➜ SETTINGS ➜ NETWORK SET UP ➜ RESTORE DEFAULTS (stop at this point and do to your router/modem and disconnect AC power. Wait a couple of minutes and plug it back in. When all the lights settle down, do back to the DVR and proceed) ➜ CONNECT NOW ➜ GET CONNECTED

Did you in fact try a different Ethernet cable as previously discussed? I only ask because as we pursue a solution for you, it's imperative that we don't simply blow past a suggestion you may feel has no merit. The 169 IP address indicates that the DVR is set to a self generated address and is getting nothing from the router. Is the router set for DHCP?

Yes, I've tried 3 different ethernet cables, the one that came with the receiver, and two others from devices that are connecting correctly via DHCP. But yes, DHCP is enabled on my router and I have also tried to assign a static address to the receiver, neither worked unfortunately.

There are no individual port/interface lights on the NVG510, just a single one. It is lit however. The NIC on the back of the receiver also indicates connectivity with an orange and yellow light. I did just do a reset on my modem/router, but it still came back with the same errors/behavior.

There are two other devices connected to this same modem that are having no issues. The modem's DHCP server is assigning each of them an IP, Subnet Mask, DNS, and Gateway address, just as a DHCP server should. Just for testing purposes, I had an extra NVG510 (new, out of box), connected it and still had the same issue. On this new modem/router, the same problem persisted.

Call DirecTV to request a replacement Receiver/DVR. It's free if you have their Equipment Protection Plan, or within 90-days of installation. Otherwise ~$20 for shipping. Or ~$50 to have a tech come replace it for you.

I am so unhappy with direct tv right now it's not funny. I am a new customer on ly 6 weeks. I have no signal yet again and they told me the earliest apt is Weds. So not tv for 5 days. I'm willing to pay the early termination fee and go back to comcast. It cost a little more but in the long run it will be worth it. You would think they could send a tech out faster than 4 to 5 days. I live in a large town/citiy it's not like we are in the boon docks lol

By the way, do you know what the early termination fee is? After calling their tech support and getting a less than helpful CSR, I think that may be my next step if I cannot get a resolution for this issue.

Multiple ethernet cables, two modems.....there's not much else on the private network side I can do. I suppose I can try to setup a DHCP server on my Mac to see if it recognizes the connection to the receiver. If not, it's all the receiver, without even a local connection to the private network a network analysis cannot even be performed via packet sniffing.

according to what they told me with a 2 yrs contract it's 20 per month that you have left in the contract. My old cable company is giving me a 200.00 gift debit card just for going back as a new customer. They now have competitive packages to direct tv with all 3 services thru them unlike I have to get internet and phone from Verizon to get the bundle package that I have. So I'm just going to downgrade to the 29.99 package and keep paying it for a few months but I won't be using the service. then once I get the debit gift card from Comcast I will use it to pay towards the rest of the early termination fee. I get the card after 90 days so that way my termination fee will have gone done by $60.00 to also help with the cost. I can't believe 5 days for a tech to come out . That's just ridiculous!!

I really just want my cable to be working. They tried everything from the office and Had me to do a few things also . I was told that they had to come out due to the second error code that came up when they had me to run the test.

I was wondering if there was a firewall issue blocking the ports the receiver from connecting. One of the things I talked about with an in-home visit from a tech yesterday (different issue for me) was that certain company's modem/routers block the required ports. He said a different customer had to contact his ISP (Centurylink) to get the specific ports DirecTV uses unblocked. The other customer got a similar read-out that you did with an IP and SubNet, but no Gateway or DNS. I don't have experience with the ATT Uverse router/modem so I can't help with specifics, but without getting a Gateway and DNS it seems that the receiver connects to the modem/router, but can't get "outside" the LAN to connect to DirecTV.

"Create New Post" button on the main forum page. Your problem may very well be different from the original poster's. With a new thread you can provide more information about your equipment (model numbers), location, and troubleshooting you've tried so far. And this forum software makes it difficult to track or respond to folks that add onto someone else's thread. Thank you.

Responding the first question on this forum, i have had Directv for over 5 years on Comcast w/o a problem. I needed to lower my bills so i switched back to AT&T. Here is where everyone's problems starts. I am not a computer genis in any manner but this is what i know. If you have on Demand Cinema, you do not want to concect your cat5 cable to the back of the Genie. It has to be plugged into your swim unit they call it. When i switched over i had internet connection, but only got half of what i was suppost to get. (Missing Pandora,Utube, and could not access Movies thru channel 1100. I have had the main unit replaced now for the third times and i dont believe that the Genie unit is the problem. The problem is AT&T. My receiver said that it was connect to the internet, yet Directv's web site said that i wasn't. I'am going after AT&T now so it i get a final solution i will post it here for you. I know how maddening this can be. My wife and kids remind me everyday. LOL.

So you can definitely connect a HR34-700 directly to an AT&T gateway via an ethernet cable? I had my direct tv installed before my internet was set up and the direct tv installer told me that I would probably have problems if I tried doing that. I just got my internet setup last night and I called direct tv and asked them if that was indeed the case. The CSR said yes and that they would send me a cinema connection kit. I have been reading all sorts of posts on this issue with people having absolutely no problems hard wiring the HR 34 to the gateway and other posts where people have problems doing it that way. I'd love to try and plug the ethernet cable in to the HR34, but I don't want to screw something up. Can anyone advise?

It isn't going to change some type of setting or assign a wrong IP address or something like that? The problems that I've read about are that the other two genie minies end up not working or none of the boxes work at all because of IP address problems.