Windows Server 2022 Metered Connection

Anonymous
2024-05-07T14:17:58+00:00

Hello,

I've recently done a fresh install of a domain controller, but I'm running into an issue with Metered Connections.

I have no use for it, there is no data limit. However removing and/or disabling it seems downright impossible.

The DC only has a LAN interface, no WLAN, no cellular data options or anything like it. Just a plain old simple server. For some reason it's applied Metered Connection without my thoughts on the matter, and despite having set the Metered Connection to disabled, it still won't allow for ANY local network traffic.

When I try and enable the Metered Connection, and switch back and forth between menu's, the option returns to being disabled.

As far as I can tell, both with the appropriate regedit settings, for all intents and purposes, Metered Connection should NOT be functioning. But it appears to be blocking all network traffic somehow.

Windows for business Windows Server Networking Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes
Accepted answer
  1. Anonymous
    2024-05-08T00:09:45+00:00

    To resolve the issue of the Metered Connection affecting network traffic on your Windows Server 2022 Domain Controller, here are several steps you can take to troubleshoot and hopefully fix the problem:

    Step 1: Verify Metered Connection Settings

    First, ensure that the metered connection is indeed turned off for your Ethernet connection:

    1. **Open Settings** by pressing Win + I.
    2. Navigate to **Network & Internet > Ethernet**.
    3. Click on your network connection.
    4. Set the **Metered connection** switch to Off.

    Step 2: Check Registry Settings

    Modify the registry to ensure the Metered Connection is turned off:

    1. **Open the Registry Editor** (type regedit in the Start menu and press Enter).
    2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\DefaultMediaCost

    1. You might need permissions to modify this key. Right-click on DefaultMediaCost, choose Permissions, and then give the Administrators group Full Control.
    2. Set the value of Ethernet to 1 (1 means non-metered, 2 means metered).

    **Note:** Be careful when modifying the registry; creating a backup of the registry before making changes is recommended.


    Step 3: Disable Metered Connection Using Group Policy

    If available in Windows Server:

    1. **Open the Local Group Policy Editor** (type gpedit.msc in the Start menu and press Enter).
    2. Navigate to: Computer Configuration\Administrative Templates\Network\Network Connectivity Status Indicator
    3. Set **Set as metered connection** to Disabled.

    Step 4: Firewall and Network Troubleshooting

    • **Check Firewall Settings**: Make sure that the firewall settings are not blocking your local network traffic.
    • **Run Network Troubleshooter**: Go to Settings > Update & Security > Troubleshoot. Find and run the Network Adapter troubleshooter.

    Step 5: Ensure Correct Services are Running

    • **DNS Client**: Ensure that the DNS Client service is running as this is crucial for domain controllers.
    • Check other relevant network services via services.msc and make sure they are running.

    Step 6: Command Line Checks

    • Use ipconfig /all to check that the network adapter is correctly configured.
    • Test connectivity in your network using ping or tracert.

    Step 7: Restart Network Services

    • Sometimes restarting network services can resolve lingering issues. Use commands like: netsh winsock reset netsh int ip reset

    Followed by a system restart.

    If these steps do not resolve the issue, further investigation into network configurations and potentially even hardware checks (e.g., Ethernet cables, network adapter hardware) might be necessary. Additionally, examining event logs (Event Viewer) for any specific network-related errors could provide more clues.

    Best regards

    Rosy

    0 comments No comments

0 additional answers

Sort by: Most helpful