OmniGuard nsite.tech
← All articles
· 2 min read

Three Windows protocols to turn off today

SMB1, LLMNR and NetBIOS over TCP/IP are enabled on far more machines than anyone expects. All three are obsolete, all three are exploited routinely, and none of them are missed.

hardeningnetworkingsmb

Some hardening is a trade-off. This is not — these three protocols are obsolete, actively abused, and switching them off costs nothing on a modern network.

SMB1

SMB1 is the file-sharing protocol behind WannaCry and NotPetya. Microsoft has been removing it since 2017 and has been unambiguous that nobody should be running it.

It survives because upgrades preserve it, and because a handful of ancient network scanners and NAS boxes still require it. If you have one of those, it is worth replacing the device rather than keeping a protocol with that record alive on your network.

Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol
Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

Check the server-side setting too, since they are separate:

Get-SmbServerConfiguration | Select-Object EnableSMB1Protocol

LLMNR

Link-Local Multicast Name Resolution is a fallback for when DNS fails. A machine that cannot resolve a name shouts the question at the whole local network and trusts whoever answers first.

That is the entire attack. An attacker on your network answers every query, the victim hands over credentials to authenticate against the attacker's machine, and those credentials are relayed or cracked offline. It is one of the first things run on any internal engagement, and it works constantly.

DNS handles everything LLMNR does. Turn it off:

New-Item -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient' -Force
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient' `
  -Name EnableMulticast -Value 0 -Type DWord

NBT-NS, its older sibling, has the same weakness and is disabled per-adapter under the WINS tab, or via the NetbiosOptions value on each interface.

NetBIOS over TCP/IP

NetBIOS exposes port 139 and provides name resolution nothing modern needs. Like LLMNR, it answers questions from anyone and can be poisoned the same way.

The wrinkle worth knowing: new adapters and VPN connections reset this to the default. Disable it across the board, then add a VPN or plug in a new USB network adapter, and it is back on that interface. If you harden this once and never look again, you will drift.

That is a general truth about interface-level settings, and a good argument for checking rather than assuming.

Verify from the system, not from the script

Every one of these can appear to apply and not take effect — a policy can be overridden, a per-adapter setting can be reset. Read the state back afterwards:

Get-SmbServerConfiguration | Select-Object EnableSMB1Protocol
Get-ItemProperty 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient' -Name EnableMulticast
Get-CimInstance Win32_NetworkAdapterConfiguration -Filter 'IPEnabled=true' |
  Select-Object Description, TcpipNetbiosOptions

TcpipNetbiosOptions of 2 is disabled, 1 is enabled, 0 is "use DHCP" — which means whatever the network says, and is not a setting so much as a shrug.

Why this is worth doing first

These three account for a disproportionate share of internal compromise. Not because they are exotic, but because they are present, ignored, and trusted by default.

There is no modern workload that needs any of them. That combination — high risk, zero cost — makes them the first thing to fix on any Windows network.

OmniGuard puts this on autopilot — threats, network, Bluetooth and hardening in one console.
Download OmniGuard