01-28-2013 6:13 AM
I have a 2-wire 802.11b/g gateway connected to a wired u-verse DVR and a u-verse WAP for the wireless receivers. I then have 2 wireless receivers. One of the receivers I use wirelessly, but the other is connected via ethernet because its primary location is very far from the WAP. Both receivers are paired with the WAP, but only one is actually running wirelessly.
This setup worked fine until this weekend, when the wireless receiver that was connected via ethernet started acting up. I rebooted that receiver, and it booted back up into update mode (gear with progress bar, then 2 gears with progress bar, then a few more reboots. then back up). Now, when I plug ethernet into that wireless receiver, it causing packet loss across my entire WAN. When I plug that receiver into the LAN, my other two receivers will start to show really gittery picture/audio, and a ping to Google's DNS (184.108.40.206) will start to have 50-60% packet loss. The second I unplug the ethernet from the wireless receiver, the problem stops.
I called tech support and the said they found a problem outside and were going to send an outside tech, but my service works fine as long as this one receiver isn't connected to ethernet. I've only seen packet loss like this before when two devices on the same LAN have the same MAC address.
Is it possible this could be because the wireless receiver is paired with the WAP and connected to the LAN at the same time? Doesn't seem likely, but the only other thing I can come up with is that the NIC on the receiver is shot. Either way, it feels like AT&T may be wasting my time investigating outside, unless there is actually another problem in addition to this one.
Solved by: Go to Solution.
01-28-2013 4:13 PM
You can disaster recover any of the recievers, press and hold OK and Down arrow on the box, keeping them held presse and hold Power till it turns off, still holding OK and Down, press power to turn it back on, when you see the spinning wheel, release Power and OK. It should go through a software update
01-29-2013 5:04 AM
You may plug a reciever into a switch. You can plug multiple recievers into a switch.
You may not plug a wireless access point (other than the one that broadcasts to wireless recievers, that one is special in that it handles the multicast IPTV traffic better) into the same switch as an STB/DVR.
I'm making the assumption that the Wireless Receiver is smart enough not to attempt to broadcast the traffic it gets on its wired port out on the wireless antenna (i.e. itself act as an access point), but I do not know this for a fact.
01-29-2013 6:14 AM
OK, everyone - I have a bit of an update.
I took the problematic receiver and connected it directly to the RG. So, the RG had WAP on port 1, Wireless receiver on port 2, computer on port 3, ethernet run downstairs to my DVR on port 4, and a second wireless receiver connected to the WAP. Immediately after powering up the wireless receiver I started seeing packetloss. The packet loss stoped when I unplugged the ethernet cable from the receiver. I called tier 2 support and they said that, although they don't have any technical documentation on the wireless receiver, the believe it is not meant to work when connected to ethernet. I didn't accept that solution.
Tier 2 advised me to unplug power from the WAP, then connect the problematic wireless receiver to power and ethernet, and leave the other wireless receiver alone. I did this, and it worked - no packet loss! Then I plugged power back into the WAP and the packetloss came back. So, the tier-2 tech decided that i just couldn't have it the way I wanted. I asked him if it was possible to un-pair the wireless receiver from the WAP, to which he said no. I argued with him, saying that since it was unpaired when I got it, there must be a way to do a factory reset and unpair it again. He walked me through doing a disaster recovery on the problematic wireless receiver, with it plugged into ethernet and power removed from the WAP. This worked! Next, we restored power to the WAP and rebooted the other wireless receiver that used the WAP - success! I then checked the network quality and it looked good! So I moved the problematic wireless receiver back downstairs to my bedroom, plugged it in to ethernet and power, and it was all jacked up again. I determined that the way to get it back online was to remove power from the WAP, power up the ethernet-connected receiver and let it boot all the way to live tv, then power up the WAP, then reboot the other wireless receiver. It seems that the wireless receiver prefers to connect to the WAP when it can, and anytime it had both connections it would tear down the network.
Having service trouble? There is an app for that! Use our troubleshooting tool or text myATT to 8758 to download the app on your device.It allows you to troubleshoot in the palm of your hand - quickly and easily!You will also find some helpful articles below.