[olguy]

After nearly a year they stopped this past few days. And they were connecting after 6.14. I have tried resetting the broadband connection, front panel reset and pulling the plug. I use the Homeplug to a Netgear wall wart. I can see both receivers on the router list of connected devices. When I unplug them, they disappear from the router. When I plug them back in, they reappear on the router. When I reset the connection I see the IP address, Subnet mask, Primary DNS and MAC address. The secondary DNS is all zeros but that is no change from when I first set them up for broadband connection. The CSR didn't seem concerned with the secondary and scheduled a tech to come out next week. In the meantime any ideas will be appreciated.

 

[srrobinson2]

After nearly a year they stopped this past few days. And they were connecting after 6.14. I have tried resetting the broadband connection, front panel reset and pulling the plug. I use the Homeplug to a Netgear wall wart. I can see both receivers on the router list of connected devices. When I unplug them, they disappear from the router. When I plug them back in, they reappear on the router. When I reset the connection I see the IP address, Subnet mask, Primary DNS and MAC address. The secondary DNS is all zeros but that is no change from when I first set them up for broadband connection. The CSR didn't seem concerned with the secondary and scheduled a tech to come out next week. In the meantime any ideas will be appreciated.

I have exactly the same issue. Just spent 20 mins on phone with level 1 tech, who finally transferred me to another level 1 who transferred me to level 2, where I got a recording saying to call back later.

 

[Sandman]

No ideas, I am having the same issues with my 722 connected directly to the router and like olguy I can see both receivers on the router list of connected devices. When I unplug them, they disappear from the router. When I plug them back in, they reappear on the router

Bob

 

[phrelin]

Same problem here on both my 722 and my 612. Unplugged my 722 from my network and reset it to get it to show 0.0.0.0 then plugged back in to network and got a valid IP address. Reports not connected! Computers are just fine.

EDIT: The only thing irritating about this is that I had the nasty warning on my 722 about not being connected will cost me money. So I plugged my phone back in.

 

[phrelin]

I sent the following email to Dish Technical Support with a cc: to Dish Quality and [email protected]:

I turned my ViP722 on this morning and had the nasty warning that I had no connection to phone or internet and that could cost me money. Went to the setup screen, IP address info was all correct as if the internet was connected, but at the bottom it showed not connected. Reset, stayed the same. Unplugged the network connection, reset to get the IP address of 0.0.0.0 then plugged it back in to the network, reset, got IP address etc., but still showed not connected. Computers are working fine.

Checked my ViP612. Same situation with the connection.

Went to DBSTalk.com and there's a new thread this morning: Neither 622 Will Connect to the Internet started by someone else with a few posts by other Dish customers confirming the problem.

I assume this is some temporary problem on your end that isn't responding to a hit from our boxes. But I also want it on record so no one with a ViP622/722 box inadvertently gets charged for not being connected.

 

[Todd Nicholson]

I just turned mine on to check and low and behold the same message about not being connected and the exact same issue. Even my homplug in the wall shows that it's connected and in the DishComm menu, it says the connection is okay, however in the broadband setup menu is say's not connected.

 

[ChuckA]

From all the symptoms, everyone's home network is working just fine. If you are getting the leased IP address and DNS address from the router and it shows up in the router list, your equipment is doing what it should. It just sounds like the receiver can not establish a connection with a Dish server somewhere.

 

[Todd Nicholson]

I just sent an email to tech support and CEO as well.

 

[phrelin]

From the L6.14 software sticky thread:

I reported the problem with Dish and they confirmed a problem. The said a fix would come soon.

 

[ChuckA]

Do you really think a down server needs to be reported to the office of the CEO? They are really going to know what to do! Or do you expect them to micro manage all customer issues?

 

[phrelin]

Do you really think a down server needs to be reported to the office of the CEO? They are really going to know what to do! Or do you expect them to micro manage all customer issues?

No, not micromange. But....

I do expect them to be aware of anything that might result in a billing snafu so that CSR's in wherever are not telling someone over and over: "Our records show you weren't connected, that is why you were charged the $5.00."

By assuring awareness throughout the organization of day-to-day tehnical occurrences related to billing, the executive office can avoid having to micromanage. But if there's a problem like this one that tech support doesn't get fixed for a day or two or three, and then they fix it without giving much thought to the billing problems created by this technical glitch....

We all know this lack of communications couldn't happen at Dish.

EDIT: I am careful to use the cc: as I don't expect a reponse from the Executive Office on issues like this one.

 

[Stewart Vernon]

For you guys (and perhaps gals) using HomePlug... what version of HomePlug adapters are you using?

I did some swapping around and found that only the older HomePlug1.0 would work in any kind of reliable way. Newer HomePlug adapters (even ones made by Sling, which is now a part of Dish) that are supposed to be backwards compatible give very sketchy results.

In my case, I was getting IP address most of the time, but actual connection speeds were so slow sometimes as to be unmeasurable. I had to go back and dig out older/slower HomePlug1.0 adapters to get reliable connections.

 

[Todd Nicholson]

My receiver seems back to normal now. It displays as connected.

 

[phrelin]

Mine receiver seems back to normal now. It displays as connected.

Mine too.

 

[olguy]

Well ain't that weird. I read this thread and saw some were coming back so I checked mine. One did and one didn't. I reset the connection and now it's good. I guess they got the server rebooted, huh? And I'm givin' phrelin's email the credit for gettin' the job done. :grin:

 

[phrelin]

Thanks, but receiving a number of reports is what causes things to come to the surface rapidly. Here's the reply I received:

Dear valued customer,

Thank you for your email. We experienced an outage with our service for these models of receivers. We apologize for the issue but it should have been restored at this point. If you test your equipment & find you are still experiencing the issue, please bypass your router & attempt to connect to the receiver directly. If this again fails to correct your issue, please reply to this email & let us know. We may request additional information to provide to our engineering department about the ongoing issue.

Your business is greatly appreciated and we thank you for allowing us to be of assistance to you. If you have further questions you can respond to this e-mail or access our online technical support at the following link: http://tech.dishnetwork.com/departmental_content/techportal/index.shtml

A Technical Service Representative is available via live chat 24 hours a day, 7 days per week regarding your concerns. Please click the following link to use this option. http://tech.dishnetwork.com/departm...al/content/tech/techchatadvcustformrf23.shtml

Thank you,

 

[DJ Lon]

My receiver seems back to normal now. It displays as connected.

Same here (after message and "not connected" this AM).