This document will provide some basic GTwifi troubleshooting information for Windows 8.
This example is assuming you are running Windows 8 with a working wireless adapter that is turned on.
Various users have been having issues after upgrading Windows 8 to Windows 8.1.
There are issues in the upgrade process relating to the wireless drivers. OIT Te
chnology Support Center recommends backing up your data and performing a clean i
nstall of Windows 8.1.
These are listed in order of difficulty as well as recommended starting places to diagnose where in your configuration there may be issues. You may only need to perform one or two of these in order to resolve your issues.
If you are uncomfortable making these changes or this document does not solve your problems, please visit the OIT Technology Support Center on the first floor of the GT Library.
NOTE: Certain software packages such as "McAfee Security Center - Consumer Version", "Norton Internet Defender", or other firewall/security related software
may interfere with basic network connectivity. Temporarily remove these packages, reboot, and attempt to connect again. If you find that your product is interfering
with your network connectivity, you may need to find an alternate method to your protect your system. OIT Technology Support may be able to assist you in
configuring your product or system. We always recommend having at least the OIT supported McAfeee Antivirus available
for free for all GT faculty, staff, and students.
- Turn the wireless adapter off and back on.
- Is "GTwifi" at the top of your network menu?
- Right click each network other than GTwifi and click "Forget this network".
- Is IPv4 configured for "Using DHCP" and IPv6 disabled under your network preferences?
- Right click the network icon in the Notification Area on the Desktop
- Click "Network and Sharing Center"
- Click "Change adapter settings".
- Double click your wireless connection (it is named different things depending on your installation) and click "Properties"
- Select "Internet Protocol Version 4 (TCP/IPv4) and click "Properties". Ensure "Obtain IP address automatically" and "Obtain DNS server address automatically" are checked. Click "OK".
- Uncheck "Internet Protocol Version 6 (TCP/IPv6). Click "OK".
- Reboot your PC.
- Configure your machine for "User authentication" only.
- Click on your wireless icon, right click on "GTwifi", and select "Properties"
- On the "Security" tab we are going to do a number of steps:
- Make sure "Security type:" is "WPA-Enterprise" or "WPA2-Enterprise" (best)
- Make sure the network authentication method is: "Microsoft: Protected EAP (PEAP)
- Then click the "Settings" button.
- The following box will come up. Verify all visible settings. Once verified, click "Configure..." button next to "Secured password (EAP-MSCHAP v2)".
- Make sure the checkbox on your "EAP MSCHAPv2 Properties" is UNCHECKED.
- Click "OK" on this menu box and lick "OK" to return to "GTwifi Wireless Network Properties" and the "Security" tab we were previously on.
- On the "Security" tab click the "Advanced settings" button.
- Make sure "Specify authentication mode" is checked and "User authentication" is displayed in the pull down box.
- Click "OK"
- Disable and re-enable your "GTwifi" connection.
- Can your machine connect to other available networks (GTvisitor, GTother)? If not, it could be a hardware/driver issue with your network card.
- Are you in an area where "GTwifi" is available? "GTwifi" is available at the same locations as "GTother" and "GTvisitor".
- Are you able to associate but not obtain an IP address? You can try to reset the TCP/IP network stack.
- Go to your "Start" screen, type "cmd" BUT DO NOT PRESS ENTER!
- Right click "Command Prompt"
- The system will ask if you want to "allow the program to make changes to this computer" select "Yes".
- Make sure you see "Administrator: C:\Windows\System32\cmd.exe" in the title of the resulting window.
- At the "C:\Windows\system32>" command prompt type the following:
netsh int ip reset C:\netsh.log.txt
netsh winsock reset
- Reboot after the above commands run and attempt to connect again.