US Telco Support > AT&T > AT&T Midwest > Not getting full 12mbs

Not getting full 12mbs

If you feel the router is at fault (you posted in networking), I would suggest bypassing it to verify.

If you want to provide some additional info, we can assist further.

Who is your ISP?
What modem do you have?
What router and applicable network devices do you have?
Any idea whether neighbors are experiencing the same issue?
Has your ISP been contacted ? What did they say in response to your issue?

My isp is at&t, my internet is bypassed i'm running lan wire cat6. Not sure about my neighbors. I don't have a really good number to them.

reply to Tham121988
What is your OS too?

reply to Tham121988
Have you run the tweak test here?

»/tweaks

On XP and earlier it can really make a difference.
--
I tried to remain child-like, all I achieved was childish.

reply to Tham121988
No, I run windows 7.

reply to Tham121988
modem? brand and model?

reply to Tham121988
12mb? This has to be Uverse doesn't it?

I would generally concur...
»www.att.com/u-verse/explore/inte···ding.jsp

The max for regular dsl is 6 Meg.
»www.att.com/gen/general?pid=14400

reply to tham121988
FYI Windows 7, as well as Vista, by default enables the "Autotuning" feature on the TCP stack which enables the Window Scaling option defined in RFC 1323 to be dynamically calculated based on your bandwidth/delay product. Many webservers, load balancers, and firewalls are not fully compliant or not supporting Window scaling as it becomes more aggressive. The dynamic portion of this control was more conservative in Vista which helped in most cases. However, it appears to have gotten more aggressive in Windows 7 thus leading to more complaints and problems that are not easy to identify or diagnose. Believe me, I have seen my share just in the past few months and spent many hours debugging the issues.

I have personally witnessed several instances where this lovely new default feature actually causes a small window to be negotiated between the client and the server because the server or device in between ignores the window scale factor and thus results in very poor throughput. Of course, the higher the latency between the client and server, this problem becomes exponentially more pronounced. Unfortunately, on average, this new capability doesn't seem to play nicely on the Internet if it is too aggressive. Disabling Autotuning so the stack acts like the long supported behavior or possibly setting it to restricted mode could possibly resolve throughput problems, depending on the webserver or application you are using.

netsh interface tcp set global autotuninglevel=disabled
 

netsh interface tcp set global autotuninglevel=restricted
 

netsh interface tcp set global autotuninglevel=normal
 

netsh interface tcp show global