How to Manage Network Adapter Protocol Bindings in Windows 11 Using PowerShell

Every network adapter in Windows 11 binds to a suite of networking protocols, filter drivers, and transport layers. These bindings include Internet Protocol Version 4 (IPv4), Internet Protocol Version 6 (IPv6), File and Printer Sharing for Microsoft Networks, QoS Packet Scheduler, and Link-Layer Discovery protocols. While all bindings are enabled by default for maximum compatibility, security baselines and network optimisations often require disabling unused protocols—such as unneeded IPv6 bindings on private LANs or Link-Layer Responder drivers on high-throughput interfaces.

Auditing Active Network Adapter Bindings

The NetAdapter module in Windows PowerShell includes dedicated cmdlets for querying and modifying adapter bindings. Open an elevated PowerShell session (Run as Administrator) to query the current binding states across all network interfaces.

To view all bound components for every network adapter, execute:

Get-NetAdapterBinding

To narrow the query to a specific network interface, specify the adapter name with the -Name parameter:

Get-NetAdapterBinding -Name "Ethernet"

PowerShell outputs a tabular list showing the component display name, internal ComponentID, and enabled status:

Name      DisplayName                                    ComponentID       Enabled
----      -----------                                    -----------       -------
Ethernet  Client for Microsoft Networks                  ms_msclient       True
Ethernet  File and Printer Sharing for Microsoft Netw... ms_server         True
Ethernet  QoS Packet Scheduler                           ms_pacer          True
Ethernet  Internet Protocol Version 4 (TCP/IPv4)         ms_tcpip          True
Ethernet  Internet Protocol Version 6 (TCP/IPv6)         ms_tcpip6         True
Ethernet  Link-Layer Topology Discovery Responder        ms_rspndr         True
Ethernet  Link-Layer Topology Discovery Mapper I/O Driver ms_lltdio        True
Ethernet  Microsoft LLDP Protocol Driver                 ms_lldp           True

To list only the components currently enabled on an adapter, filter using Where-Object:

Get-NetAdapterBinding -Name "Ethernet" | Where-Object { $_.Enabled -eq $true }

Understanding Standard Component IDs

When modifying bindings programmatically, PowerShell uses internal ComponentID identifiers rather than localised display names:

  • ms_tcpip: Internet Protocol Version 4 (TCP/IPv4). Essential for standard IPv4 network connectivity.
  • ms_tcpip6: Internet Protocol Version 6 (TCP/IPv6). Handles modern IPv6 addressing and prefix resolution.
  • ms_server: File and Printer Sharing for Microsoft Networks (Server Service). Enables inbound SMB file access.
  • ms_msclient: Client for Microsoft Networks (Workstation Service). Enables outbound SMB file browsing.
  • ms_pacer: QoS Packet Scheduler. Enforces bandwidth throttling and DiffServ traffic priority.
  • ms_lltdio: Link-Layer Topology Discovery Mapper I/O Driver. Maps device topology across local networks.
  • ms_rspndr: Link-Layer Topology Discovery Responder. Responds to topology discovery queries from other hosts.
  • ms_lldp: Microsoft LLDP Protocol Driver. Advertises local station capabilities to network switches.

Disabling Specific Protocol Bindings

To disable a specific protocol binding on a network adapter, use the Disable-NetAdapterBinding cmdlet. For example, to disable IPv6 on the “Ethernet” adapter:

Disable-NetAdapterBinding -Name "Ethernet" -ComponentID "ms_tcpip6"

To disable inbound File and Printer Sharing on a public or untrusted Wi-Fi connection:

Disable-NetAdapterBinding -Name "Wi-Fi" -ComponentID "ms_server"

To disable Link-Layer Discovery protocols that transmit periodic broadcast packets:

Disable-NetAdapterBinding -Name "Ethernet" -ComponentID "ms_lltdio"
Disable-NetAdapterBinding -Name "Ethernet" -ComponentID "ms_rspndr"

Verify that the binding was successfully disabled by checking the component state:

Get-NetAdapterBinding -Name "Ethernet" -ComponentID "ms_tcpip6"

Re-Enabling Adapter Bindings

If network services or corporate authentication policies require a previously disabled protocol, re-enable it using Enable-NetAdapterBinding.

To re-enable IPv6 on the “Ethernet” adapter:

Enable-NetAdapterBinding -Name "Ethernet" -ComponentID "ms_tcpip6"

To re-enable File and Printer Sharing:

Enable-NetAdapterBinding -Name "Ethernet" -ComponentID "ms_server"

To restore all default bindings on an interface simultaneously:

Get-NetAdapterBinding -Name "Ethernet" | Enable-NetAdapterBinding

Enforcing Security Baselines Across All Network Adapters

System administrators managing workstation fleets can enforce network hardening scripts across all active physical adapters. The following script identifies all physical network adapters and disables discovery responders while preserving core TCP/IP communication:

# Retrieve all physical adapters currently connected
$adapters = Get-NetAdapter -Physical | Where-Object { $_.Status -eq "Up" }

foreach ($nic in $adapters) {
    Write-Host "Hardening adapter: $($nic.Name)" -ForegroundColor Cyan
    
    # Disable LLTD discovery protocols
    Disable-NetAdapterBinding -Name $nic.Name -ComponentID "ms_lltdio" -Confirm:$false
    Disable-NetAdapterBinding -Name $nic.Name -ComponentID "ms_rspndr" -Confirm:$false
    
    # Verify binding status
    Get-NetAdapterBinding -Name $nic.Name | Select-Object Name, ComponentID, Enabled
}

Managing bindings through PowerShell eliminates the manual overhead of traversing GUI adapter properties and guarantees reproducible network configuration across Windows 11 workstations.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.