Many receiver problems can be fixed by restarting your receiver. To do this, press and hold the Power button for 10 seconds. This takes 5-8 minutes and will impact any DVR recordings in progress. If you have multiple receivers, reboot your wireless gateway by unplugging it from its power source. Wait a few minutes, then plug it back in.
If the receiver is not responding to the remote try this:
Check the batteries in the remote by pressing the AT&T button on the remote. If you see a red light, the batteries are still good. If you don’t see a red light or the red light is dim, replace the batteries in the remote.
Let's start with those troubleshooting steps above. If these troubleshooting recommendations do not resolve the receiver, then we will need to take a look to see what the other options are.
Constructive
Employee
•
34K Messages
1 year ago
Is it an issue with the remote?
0
0
DIRECTVhelp
Community Support
•
254.4K Messages
1 year ago
Hi there, dlbarlow. We understand that your U-Verse TV VIP2250 receiver is not responding. We can help you with that.
Let's start with a manual reboot of the receiver:
Many receiver problems can be fixed by restarting your receiver. To do this, press and hold the Power button for 10 seconds. This takes 5-8 minutes and will impact any DVR recordings in progress. If you have multiple receivers, reboot your wireless gateway by unplugging it from its power source. Wait a few minutes, then plug it back in.
If the receiver is not responding to the remote try this:
Check the batteries in the remote by pressing the AT&T button on the remote. If you see a red light, the batteries are still good. If you don’t see a red light or the red light is dim, replace the batteries in the remote.
Let's start with those troubleshooting steps above. If these troubleshooting recommendations do not resolve the receiver, then we will need to take a look to see what the other options are.
Please let us know.
Matthew, AT&T Community Specialist
0
0
dlbarlow
2 Messages
1 year ago
The set top box was replaced. No amount of reboots helped.
0
0