AT&T U-Verse internet acts weird when upgraded

[01rangerxl]

I have AT&T U-Verse internet provided by the landlord.

Not sure exactly how U-Verse works and all, but I know lots of other business and residential customers are in the area are using the same service. The law offices next door and the bank across the street use it. AT&T is perpetually upgrading or working on this or that.

They did it again today, and my internet started acting up again today and still is. Every time they mess with something the internet acts screwy for a few days.

Basically, my computer will connect to the internet and at super fast speeds for a few minutes, then after those few minutes, only a handful or maybe just one website will work with everything else not loading at all, not even slowly. A lot of times it's BITOG that will work, maybe because that's my usual test site or a lot of it is cached, I don't know. Computers are not my thing.

Playing with the "fix the [censored] internet" features in Windows does nothing. Turning the firewall on/off does nothing. Messing with Avast antivirus does nothing. Basically nothing on the computer end changes what happens. Usually restarting the computer will get me some internet temporarily again though.

I am hoping this will just go away after a couple days like it has in the past, but it's getting irritating. How come every time AT&T sneezes, my computer hates the internet?

I have tried different CAT5 cables, that has no effect. Computer is plugged right into the wall outlet, so no router on my end.

Maintenance tried helping me out today, but couldn't figure out why it does this. They said it happens to other people too whenever AT&T plays with the internet.

Any ideas on why my computer seems to throw a fit every time AT&T screws with U-Verse? It's almost like something on the computer is blocking the internet, but I can't figure out what. Why would there be a delay between "fixes" and when the internet starts working again? It seems like when they get done with whatever they are doing, it should just work again, but I don't know what these "equipment upgrades" and such consist of.

 

[01rangerxl]

An example of the weirdness...right now I can surf BITOG no problem and it's fast, but if I click on a link to a news site, no go. Problem loading page. If I were to close the browser with BITOG right now, it would probably quit working until a restart of the computer. This stuff always correlates with a U-Verse "equipment upgrade."

[censored]?

 

[Rand]

did you reset you cable modem router etc?

 

[yonyon]

I had a similar problem a couple few years back when I was using Verizon DSL and they were doing frequent upgrades. They'd upgrade something and my Internet would disappear. To fix it I'd open a terminal window and use this command:
Code:
sudo ip addr flush dev eth0 && sudo ip link set eth0 down && sudo ip link set eth0 up && sudo /sbin/dhclient eth0
It worked.

 

[01rangerxl]

I don't have a router in my apartment. There's just wall outlets in every apartment. I'm plugged right in.

BITOG is working now. Basically nothing else is.

I think yonyon is on to something. ip addr flush sounds like a good idea whatever it is. What is a terminal window? The command prompt? I have Windows 7.

 

[yonyon]

Sorry about that. That command I gave you isn't going to work in Windows, but there should be an equivalent that you can look up in Windows Help. The idea is to flush the routing tables and restart the DHCP client so your computer sees the network nice and fresh as if you just unplugged it from one router and plugged it into another. This would be the first thing I'd try.

This won't work if the router you're actually plugged into is working with out-of-date data. In that case you will need to reset the router. If you don't have access to the router (and it looks like you don't unless your landlord is willing to give you the admin login/password for remote administration) you could achieve the same result by flipping the breaker.

 

[simple_gifts]

yonyon's advice is for linux.

you can do an ipconfig /flushdns under windoze in a command window.

FWIW; I have ATT DSL and there have been intermittent issue with my service as well over the last 2 weeks.

I use linux and would open a shell and "ping 8.8.8.8" google's DNS server. It should be about 40ms, but at times it has recorded 13000ms (13 seconds) Nothing loads. After a few minutes it clears up and I'm back to surfing. When you have an issue, open a command line and type ping -t 8.8.8.8 and see what response times you have. It may have nothing to do with your set up or connection @ home.

 

[Voltmaster]

If you have router/using wireless, it could be that ALOT of connection are around you,this will cause interfrence no matter what. Even if your using the build in wifi of Uverse.

If you have an android device, use wifi analazer to see what channels are being used alot, and set your channel manualy to one not being used alot.

Changing power output is also useful , never leave it at maximum.

192.168.1.254 is alot of uverse default IP.

Go in there and check wifi if your using the modem for wifi also.

Another thing to check to see if your getting a good connection..
go to Settings > Broadbard > status.
See your User Rate and MAx user rate. Are they close to what you should be getting?
finally check Output Power on same page. if its below -16Db, you should really have ATT come and service it.

 

[01rangerxl]

No wireless, no router. Just a CAT5E right into the wall. Nothing between the wall outlet and computer but cable.

I tried DNS flush. It did successfully do it, but internet acted the same afterwards. I think something is screwy with AT&Ts garbage equipment downstairs, which I don't have access to. If this doesn't fix itself in the next couple of days, I will pressure them to get AT&T or someone out here to look at it because it's getting really annoying.

AT&T sucks. Never had anything but problems from their internet service. Supposedly had fiber optic from AT&T at my last house...yeah right. That [censored] was slow as [censored] and just as buggy as this.