1. Home
  2. Knowledge Base
  3. Featured Articles
  4. No Internet Access When Connected (Affects Ethernet AND/OR Wi-Fi)
  1. Home
  2. Knowledge Base
  3. Wi-Fi and Bluetooth Troubleshooting
  4. No Internet Access When Connected (Affects Ethernet AND/OR Wi-Fi)
  1. Home
  2. Knowledge Base
  3. Ethernet Troubleshooting
  4. No Internet Access When Connected (Affects Ethernet AND/OR Wi-Fi)

No Internet Access When Connected (Affects Ethernet AND/OR Wi-Fi)

Some users may encounter an issue where they are unable to use the Internet even though they appear to be connected through either Wi-Fi or Ethernet. Restarting the computer will, in some cases, fix the problem temporarily.

Before troubleshooting this issue with the suggestions below, make sure you have clean-installed the latest Killer Control Center and device drivers. You can do this by following our clean-install guide.

Click here for the guide to clean-install the Killer Control Center and device drivers.

Click here to jump to the registry fix.

Update February 8, 2019

Microsoft may have corrected this issue in the latest patch for Windows 10 1809. You can read the change notes here – https://support.microsoft.com/en-us/help/4476976/windows-10-update-kb4476976. You may now be able to resolve this issue by manually checking for updates. You can do this by clicking Start, then type Update and click Check for Updates then click the Check for Updates button. If your machine has updates, they should then download and install. If the updates have not resolved the issue, restart your machine and check for updates again. Do this until there are no new updates after a fresh restart to make sure you have all available Windows Updates. If this does not help, proceed to the registry fix below.

Update January 11, 2019

With machines running Windows 10 1809, the fix detailed below may or may not resolve the issue. There seems to be a completely different issue with 1809, which is a bug that Microsoft has yet to address. You can find out which version of Windows 10 that you are running by clicking Start, then type winver and press Enter. You will see “Version” followed by your Windows 10 version number. If you are using Windows 10 1809, the only potential fixes, at this time, seem to be enabling IPV6, and setting your network connection to “Public” instead of “Private.” This a Windows 10 issue and not an issue with any specific network adapter or brand. You can find information about the issue, as well as Microsoft’s suggested fixes, by clicking here. Although the post specifically mentions Microsoft Store applications, most users who experience this problem are experiencing it with multiple applications from multiple sources.

If your Windows version is 1803 or earlier, the registry below fix often resolves this problem. It may also resolve the issue on some Windows 10 1809 machines, but that seems to be more hit-or-miss.

The Registry Fix

Another problem has been confirmed to be an issue with Windows 10’s port management, which has surfaced with recent updates. This issue is a reoccurrence of a problem that affected Windows 8.1, but the fix remains the same. These updates have removed entries from the Windows 10 registry which instructed the operating system to release used ports when all ports are exhausted. Ports are a list of finite virtual numbers that are necessary for any network connection. If all ports are open and not released, this creates the effect of being connected to an Internet connection without the operating system having the ability to open new ports. Applications and services that were already connected may or may not continue to function, at least partially, while the user is unable to browse the Internet or connect to anything else.

We have confirmed that you can often resolve this by replacing these registry entries. Here is a step-by-step guide:

    1. Click Start
    2. Type regedit and press Enter
    3. Click File > Export… and then save the file to a place you will remember. This file is your registry backup. If anything goes wrong, you can double-click this file from your machine, and it will restore your current registry settings. The export may take a moment.
    4. Once the export is finished, copy this line – HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters – and paste it into the white space directly below File – Edit – etc., and press Enter, which should navigate you to the correct location in the registry, as seen below (right-click on the image and open image in a new tab to expand):

      Ports Registry Fix
      Ports Registry Fix
    5. With Parameters remaining highlighted on the left side, right-click the empty white space on the right and click New > DWORD (32-bit)
      Even though nearly all Windows 10 installs are 64-bit, DWORD (32-bit) is the correct selection.
    6. Name it TcpTimedWaitDelay and press Enter.
    7. Double-click the newly created TcpTimedWaitDelay and change the Value to 0000001e. Leave the Base setting as Hex. It should look like the below screenshot.

      Ports Registry Fix Entry
      Ports Registry Fix Entry
    8. Click OK.
    9. Repeat steps 5-8, creating the following keys:
      1. Name: MaxUserPort
        Value: 0000fffe
        Base: Hexadecimal
      2. Name: TcpNumConnections
        Value: 00fffffe
        Base: Hexadecimal 
      3. Name: TcpMaxDataRetransmissions
        Value: 00000005
        Base: Hexadecimal 
    10. Click File > Exit
    11. Restart by clicking Start > Power > Restart and test.

If the issue returns, future updates of Windows may overwrite these changes. Unfortunately, the best remedy will be to re-input these registry keys if you find that they are missing with future updates.

If you have followed all of the troubleshooting steps above and are still experiencing issues, please contact us by clicking the button on the left. Make sure you include a diagnostic so that we can analyze your specific situation appropriately.

Updated on April 12, 2019

Was this article helpful?

Related Articles

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!