Tutor
•
5 Messages
Issues with Rewinding with UVerse
I currently have AT&T U-Verse and I'm on the AT&T Internet 25 plan. My router is the NVG599 and I am connected to a wireless access point, 2 wireless tv receivers, 2 wired tv receivers, 2 wired Xbox One's, 2 wireless laptops, 3 phones, and a Kindle.
I posted a question last week about me having ping spikes on my Xbox One at completely random times. I was told to, "try disabling IPv6 on your Gateway and changing the Ethernet port configuration for each port on the Gateway from Auto-Detect to 100Base/Full Duplex and do a ping test." I tried doing this and while my ping spikes went away, my home's wireless UVerse boxes can't rewind at all. Everytime I try and rewind my tv completely freezes up every 5 seconds and then takes me back to live tv. I tried turning back on my IPv6 on my gateway and set my ports back to Auto-Detect but my UVerse is still broken. As always, any tips or help on how to fix this issue is greatly appreciated.
gr8sho
ACE - Professor
•
5.7K Messages
6 years ago
@Yo4777
Unless you truly know what you’re doing, your U-verse receiver equipment needs to be connected directly to the RG.
0
Yo4777
Tutor
•
5 Messages
6 years ago
@gr8sho
I have 2 receivers connected directly to my RG but I also have a WAP that wirelessly connects the other 2 receivers. Everything was completely functional before I changed the ethernet ports. The only reason why I changed them was because I was told that it would help me to stop having so many ping spikes but I now have this issue.
0
0
JefferMC
ACE - Expert
•
36K Messages
6 years ago
Then I would put them back the way they were before you changed them.
0
0
gr8sho
ACE - Professor
•
5.7K Messages
6 years ago
If you're using something like the VAP2500 for the Uverse receivers, that will take one of your 4 Ethernet ports and is fine.
If you're also using a separate data Access Point, it would be on another Ethernet port possibly connected via a switch. That switch could also be used to connect PCs and Xbox.
Any wired Uverse receivers would be on a separate Ethernet interface. Can use a dedicated switch. The important thing here is to isolate your IPTV traffic from regular computer traffic.
I'm offering this because I can't visualize how everything's connected. And this only provides a baseline. Ping spikes don't necessarily come from issues on internal network. And I'm with @JefferMC that the changes you were advised to make should be undone. If you are worried one of your devices is causing a problem, try dumbing down the network to make it as simple as possible to isolate it. I would do this in case you want to pursue the issue with AT&T to ensure your end is clean.
0
0