ybasha's profile

Tutor

 • 

4 Messages

Friday, January 1st, 2021 4:53 PM

U-verse TV keeps jumping to live TV

Hello,

This week my wired DVR receiver started showing the message "This Channel jumped to live TV to allow TV viewing or recording on the DVR receiver". This happens even if we do not have any recording going on the DVR or any other TV receiver being on.  I called the customer support line and they just restarted the receiver and made sure it got the latest update. However 5 minutes after the restart, it happened again. Please note the following:

1- The DVR is wired and not wireless (seen many threads about wireless ones).

2- Whenever it happens, I check and verify that the DVR was not recording any other show at the time. (Even if it was, we are supposed to have 4 streams going on at the same time, but that is not the case when the issue happens).

ACE - Expert

 • 

28.3K Messages

4 years ago

It could be that your DVR is starting to fail.  How old is it?  What is the model?

You can call in and ask for a replacement (swear it's not working) but you would lose all of your recordings.

Tutor

 • 

4 Messages

4 years ago

The DVR receiver I have now is a replacement to an older receiver. The replacement happened in March 2020. The DVR model is VIP 2250.

They did a line test and they said it is working fine (of course except for the issue I am having). 

ACE - Expert

 • 

28.3K Messages

4 years ago

Have you tried rebooting the gateway first and then rebooting the DVR?  

Unplug the gateway and the DVR.  Wait 30 secs.  Plug in gateway first, wait for all lights to come on and then plug in the DVR.

(edited)

ACE - Expert

 • 

36.8K Messages

4 years ago

Just to confirm:

This is happening on the receiver that is the actual DVR receiver, not an additional wired TV receiver that is not the DVR?  If so, sounds like your DVR may be failing as skeeterintexas suggested.  You can try the reboots as she suggests, and you could try a Disaster Recovery (but I don't hold out much hope that it'll fix this).  But I suspect you'll be replacing that DVR again.

The message you're getting is normally generated by a remote receiver when either (a) the DVR runs out of streams, or (b) the Receiver loses communication with the DVR.  For the DVR itself to generate that message makes little to no sense.

(edited)

Visitor

 • 

10 Messages

3 years ago

I occasionally have the same issue. In fact it has happened twice in the last 30 minutes. My laptop is wired ethernet out of the gateway and I lose internet at the same time so I think that definitely eliminates the WAP and/or DVR. I go to Menu/Options/Restart Receiver which sometimes takes 2-3 minutes. It works but is really irritating. 

ACE - Expert

 • 

36.8K Messages

3 years ago

The message indicates that your receiver and your DVR lost communication with each other.  This could be because your Gateway went off to retrain due to a line issue?  Do you have FTTP or VDSL2?

ACE - Professor

 • 

1.5K Messages

3 years ago

@tonyyprostinak 

None of that should be occurring.  I suppose I’d factory reset the gateway if I had those issues happening.  This way if you have to call back into Att support you can tell them you’ve taken that step.   

Tutor

 • 

4 Messages

3 years ago

The DVR was defective. The issue was resolved by AT&T 12 months ago. The resolution was to replace the DVR.

Thank you everyone.

Visitor

 • 

10 Messages

3 years ago

Thank you gr8sho! It's worth a shot.

Visitor

 • 

10 Messages

3 years ago

Received a replacement 5268 gateway yesterday. Lost connection twice within 10 minutes. Lost connection twice this morning. The second time had to restart 4 times before it finally connected. Was in a loop for 4 minutes. Did get a "failure to get bootstrap address" once yesterday and once today. Any ideas.  

ACE - Expert

 • 

36.8K Messages

3 years ago

@tonyyprostinak , go to http://192.168.1.254/ , look for the Broadband tab and take a screenshot of the statistics tables (sync rate, Noise Margin, Attenuation, Error counts) and post it here.

Visitor

 • 

10 Messages

3 years ago

Hello,

This week my wired DVR receiver started showing the message "This Channel jumped to live TV to allow TV viewing or recording on the DVR receiver". This happens even if we do not have any recording going on the DVR or any other TV receiver being on.  I called the customer support line and they just restarted the receiver and made sure it got the latest update. However 5 minutes after the restart, it happened again. Please note the following:

1- The DVR is wired and not wireless (seen many threads about wireless ones).

2- Whenever it happens, I check and verify that the DVR was not recording any other show at the time. (Even if it was, we are supposed to have 4 streams going on at the same time, but that is not the case when the issue happens).

Visitor

 • 

10 Messages

3 years ago

Event Log Lists
Type Date/Time Event Description
INF 2022-02-23T12:01:38-06:00 hurl
err=4 name=NO_DHCP_SERVICE clear
INF 2022-02-23T12:01:37-06:00 sys
DNS up DNS1:68.94.156.11, DNS2:68.94.157.11
INF 2022-02-23T12:01:37-06:00 sys
ipnet0: Up on br1 with 75.44.81.8/22
INF 2022-02-23T12:01:34-06:00 hurl
err=4 name=NO_DHCP_SERVICE detect
INF 2022-02-23T12:01:34-06:00 hurl
err=15 name=EAPOL_FAILED clear
INF 2022-02-23T10:16:31-06:00 sys
Node 192.168.1.71 is down
INF 2022-02-23T10:10:54-06:00 sys
Node 192.168.1.69 is up
INF 2022-02-23T10:10:54-06:00
Previous log entry repeated 2 times
INF 2022-02-23T10:10:46-06:00 sys
Node 192.168.1.71 is up
INF 2022-02-23T10:06:40-06:00 sys
Node 192.168.1.65 is up
INF 2022-02-23T10:05:40-06:00 sys
Node 192.168.1.65 is up
INF 2022-02-23T10:05:10-06:00 sys
Node 192.168.1.67 is up
INF 2022-02-23T10:04:40-06:00 sys
Node 192.168.1.65 is up
INF 2022-02-23T10:04:40-06:00
Previous log entry repeated 14 times
INF 2022-02-23T10:04:40-06:00 sys
Node 192.168.1.72 is up
INF 2022-02-23T10:04:26-06:00 sys
Node 192.168.1.64 is up
INF 2022-02-23T10:01:21-06:00 acs
bdc started.
INF 2022-02-23T09:49:10-06:00 sys
Node 192.168.1.65 is up
INF 2022-02-23T09:49:03-06:00
Previous log entry repeated 2 times
INF 2022-02-23T09:48:59-06:00 sys
Node 192.168.1.64 is up
INF 2022-02-23T09:38:27-06:00 sys
Node 192.168.1.65 is up
INF 2022-02-23T09:38:20-06:00
Previous log entry repeated 2 times
INF 2022-02-23T09:38:16-06:00 sys
Node 192.168.1.64 is up
INF 2022-02-23T09:36:59-06:00 hurl
host=signal.pod1.avatar.ext.hp.com uri=/avatar/v1/collections/signal/beuh unavailable, WAN down
INF 2022-02-23T09:36:59-06:00 hurl
err=4 name=NO_DHCP_SERVICE redirect
INF 2022-02-23T09:36:54-06:00 hurl
err=4 name=NO_DHCP_SERVICE redirect
INF 2022-02-23T09:36:54-06:00 hurl
host=signal.pod1.avatar.ext.hp.com uri=/avatar/v1/collections/signal/beuh unavailable, WAN down
INF 2022-02-23T09:36:44-06:00 hurl
host=signal.pod1.avatar.ext.hp.com uri=/avatar/v1/collections/signal/beuh unavailable, WAN down
INF 2022-02-23T09:36:44-06:00 hurl
err=4 name=NO_DHCP_SERVICE redirect
INF 2022-02-23T09:36:42-06:00 hurl
err=4 name=NO_DHCP_SERVICE detect
INF 2022-02-23T09:36:41-06:00 sys
dnstest0: connection lost, reconnecting...
INF 2022-02-23T09:11:54-06:00 hurl
err=4 name=NO_DHCP_SERVICE clear
INF 2022-02-23T09:11:53-06:00 sys
ipnet0: Up on br1 with 75.44.81.8/22
INF 2022-02-23T09:11:53-06:00 sys
DNS up DNS1:68.94.156.11, DNS2:68.94.157.11
INF 2022-02-23T09:11:49-06:00 hurl
err=15 name=EAPOL_FAILED clear
INF 2022-02-23T09:11:43-06:00 hurl
err=15 name=EAPOL_FAILED redirect
INF 2022-02-23T09:11:43-06:00 hurl
host=signal.pod1.avatar.ext.hp.com uri=/avatar/v1/collections/signal/beuh unavailable, WAN down
INF 2022-02-23T09:11:38-06:00 hurl
err=15 name=EAPOL_FAILED redirect
INF 2022-02-23T09:11:38-06:00 hurl
host=signal.pod1.avatar.ext.hp.com uri=/avatar/v1/collections/signal/beuh unavailable, WAN down
INF 2022-02-23T09:09:52-06:00 sys
dnstest0: connection lost, reconnecting...
INF 2022-02-23T09:09:47-06:00 sys
dsl0: connection lost, reconnecting...
INF 2022-02-23T08:24:41-06:00 sys
Node 192.168.1.68 is up
INF 2022-02-23T06:32:37-06:00 sys
Node 192.168.1.66 is up
INF 2022-02-23T02:03:35-06:00 sys
Node 192.168.1.66 is up
INF 2022-02-23T01:59:54-06:00 sys
Node 192.168.1.67 is up
INF 2022-02-23T01:34:01-06:00 sys
Node 192.168.1.65 is up
INF 2022-02-23T01:31:19-06:00 sys
Node 192.168.1.64 is up
INF 2022-02-23T00:17:25-06:00 sys
Node 192.168.1.72 is up

ACE - Expert

 • 

36.8K Messages

3 years ago

That's [the screenshots] the information I'm looking for, though I'm not sure you've been booted long enough to get the full picture, and the resolution makes reading it a bit difficult.  Maybe get another capture after it's been running longer.

The DVR is always wired.  You are not allowed to install a DVR with a wireless connection.  It might be connected via Coax or Ethernet on a 5268AC, but it must be connected by one or the other.

The message appears at any time the client receiver you are watching TV on looses sync with the DVR.  It doesn't matter whether or not enough streams are actually in use, it just means it's lost its stream from the DVR and assumes the reason was what it says it is (c.f. 10 fallacies of network computing).

How, exactly, is your DVR connected to the 5268AC?  coax?  Ethernet?  switches?

(edited)

Visitor

 • 

10 Messages

3 years ago

Ethernet. I have spares. I just swapped it out although my ethernet tester says it's ok.


NEED HELP?