Dish's solution to this for everyone seems to be just sending the person a new receiver. This really shows they don't understand the problem.
I've noticed that connecting with the windows app or an iphone will usually allow the website to connect.
I spoke with a CSR a while back about this issue. During the conversation I mentioned my problem connections were on dish7.sling.com and he stated that was the address the majority of folks he helped reported and said he would write it up. There was no offer of a new box and I did not expect one. Even before my 922 I had problems connecting to Dish Remote Access to schedule timers on both 622s.
A few days later I noticed I'm now on dish4.sling.com. I still have the problems but not as often as on dish7. Sometimes I log on and the 922 is the only box reported on line. Sometimes one of the 622s is. Sometimes all 3 are. Sometimes if I wait a few minutes one or the other will show up.
The big problem I think is that the Dish Remote Access resides on Sling servers but Sling CSRs won't talk to you. Dish CSRs say Sling set it up and they don't know anything about it. So here we set twiddling our thumbs, logging on with our smart phones or something else and no progress is made on this problem.
I wish they would let us hardcode the IP address on the 922, that would make things a lot more stable and easier to troubleshoot.
Would a hard coded IP on the 922 be of more use than a dedicated IP on your router? I've been thinking about assigning all my stuff it's own IP but with 3 dish boxes, 3 BD players, 6 computers, 2 wireless printers, an iPad, an iPod Touch and a smart phone that might take an old man a while.
