Beruflich Dokumente
Kultur Dokumente
No internet access
So brief.
So rude.
So limited.
By the way, yes my Wi-Fi network is actually called friedchicken and yes I am African American
but no - all African Americans dont like Fried Chicken but I sure do!
Anyway
The limited connectivity issue is a vexing problem partially because the error is so freggin nebulous
and also because you can easily waste an entire day trying to fix it. Whats even more confounding
is that sometimes youll see this error even though you have five bars of signal strength (just
like me in the above graphic)
Usually most people try disconnecting and reconnecting and a few audacious neophytes try
uninstalling the network adapter.
You actually dont need to go to such bold lengths
Here are four tricks that will almost certainly fix this problem:
1. Use netsh.exe
There are a few things you can do to fix this problem but the easiest and most common solution is to
usenetsh to reset the TCP/IP stack to its default configuration.
The NetShell utility (netsh.exe) is a highly versatile tool that lets power users manage a myriad of
computer processes right from the command line. Heres how to put the tool to work for you:
Press the Windows Key + x + a to launch the Command Prompt with administrator rights.
Then reboot the computer and retry the internet connection. It should connect fine now.
Click on the name of your Wi-Fi network and choose the Properties button in the lower left corner
under.
Then pick the last tab called Power Management and youll see this option:
Uncheck it, click OK and then login to your computer again to confirm the fix.
metered connections
When the Devices screen flips onto the screen, toggle the knob to On then logout and login to
your computer to apply the change.
Keep in mind you should try this even if you know for sure that you arent using a metered
connection. I know that sounds inane but for some reason turning this on fixes the problem.
The first netsh command disables the scaling window in TCP after the second re-transmission of a
SYN packet. The details are kind of abstruse so Ill spare them but the bottom line is that
sometimes Windows seems to arbitrarily change the way the TCP buffers are sized.
Executing the above netsh commands changes the TCP Window size to 65,535 and enforces the
change which precludes Windows 8 from flubbing with it again.
Update 08/18/2014
Lenovo Yogo users should use the sets above with caution. At least one user (See
Austin in the comments below) discovered using netsh.exe crashed rtwlanu.exe.
Update 08/22/2014
One of my readers, Erik, had this issue on his Dell Venue 11i Pro. He couldnt connect to Wi-fi on
battery power. He ended up fixing it by changing the power options for the Wifi card from high
energy savings to low.