Reading that esse ...I recall a few other.
I'm thinking we need to have specialized forum "Gadgets obituary".
I'm thinking we need to have specialized forum "Gadgets obituary".
You were on the right track. The tech guessed the problem right away. The smartcard was not fully inserted. He said he has seen this problem on several receivers. Maybe due to rough handling in transit?P Smith said:Seems to me, it's the card's culprit, perhaps it did not get proper authorization and still running on old content from previous owner and by expired authorization records.
Perhaps it was hacked with a blocker preventing the changes.
Try to convince them replace the card.
Not a DIRT member but worked for Dish in their Christiansburg, Va call center about nine years ago. Smart card resets were common back in those days but were changed due to static discharges frying smart cards. And the fact it was much easier with the front panel reset when you got the 65 year old with vision problems pulling out the card by accident and unable to find the slot to put it back in. At least that was the information passed on to the CSRS back then. Does seem like a common sense trouble shooting step for what you just described though.BillJ said:If any DIRT members read this, put the old "pull the smartcard and re-insert it" back in the tech support script, especially with new or replacement receivers. It used to be a standard troubleshooting step but I haven't heard it in so long it never occurred to me. Could have saved Dish the cost of a service call and me the frustration of no TV in the bedroom and den for several days.
Hmm, so THAT'S what happened!Frodo301 said:Not a DIRT member but worked for Dish in their Christiansburg, Va call center about nine years ago. Smart card resets were common back in those days but were changed due to static discharges frying smart cards. And the fact it was much easier with the front panel reset when you got the 65 year old with vision problems pulling out the card by accident and unable to find the slot to put it back in. At least that was the information passed on to the CSRS back then. Does seem like a common sense trouble shooting step for what you just described though.