Uverse Router problematic

I'm also going to call ATT about this, but I'd rather actually understand what's happening too, and this is the place for that.

1 Uverse setup; 4 laptops
- 1 XP
- 1 netbook-style XP
- 1 Win 7 (home)
- 1 Win 7 (work, belongs to company)

In the past, all of the computers except for the home Win 7 PC have had rock-solid connections. The Win 7 home PC has always been problematic, dropping periodically, but since my son had the same problem when he visited for a week, I figured it was early Win 7, and just put up with it.

All of a sudden, the Win 7 machine is rock solid, and none of hte others will connect at all -- they all get "limited or no connectvity" connections, and I get a "network did not assign a network address" message when I run the diagnostics. The Win7 machine was particularly awful the other day, and was all of a sudden connecting via a neighbor's linksys (I'd forgotten that I'd been using the PC at my cousin's, who also has a generic linksys); I kept forcing it back to mine, then running diagnostics when it wouldn't connect (which it wouldn't most of hte time that day). Then, all of a sudden, it's golden.

My understanding of PC networks is very, very limited -- I'm hoping to improve it, ergo the question, rather than just calling someone to come out and apply some magic. What should I be looking for?

What the heck did I break, and how?
thanks

 

Have you rebooted the RG? Have you downloaded Uverse Realtime from http://uvrealtime.com/ As for anything else, you may want to post over in utalk.att.com/utalk regarding. If I had to guess, I would have to say that if you made any changes to the wifi settings, if that is how all are connecting, that can be a problem. If connecting via ethernet, and you have a switch in the mix, that can also be a problem, along with bad ethernet connections.

Post over at the utalk.att/com/utalk link with screenshots from Uverse Realtime, of the IP/Profile, Error Table, BitLoading tabs, and with a description of the problems you are getting, if you have not done so.

 

thanks; as it happens, after a couple of less-than-helpful contacts with ATT, I finally got a real person to call me when someone kicked me off the chat by mistake. It took renaming the network, then me resetting the router. They'd already tried some other reconfiguration (they prefer us to think it's all magic), and resetting it remotely.

The ATT guy who kept calling me back (since it's Uverse, and I was on my land line, resetting the router meant losing the phone call) was really, really persistent in all the right ways, and obviously he knew what he was about.

Apparently repeated drops and reconnections can corrupt something in the router; the Win7 machine that had been bad (and which was the only one working Friday) had definitely repeatedly dropped and reconnected.

Now they all work.

Wendy P.

 

No, repeated drops do not corrupt anything in the router. You need to download the tool that I posted the link to, and post the info stated to be screen captured, over on the utalk.att.com forum for Residential Gateway. There are those that would be better to help you with this over there.

If the router is rebooting, you have a problem with your line, and need to do the steps that I stated.