PORTEncrypted only with SMB 3 encryptionBlock at edgeIANA assigned
Port 445SMB (file sharing)
Port 445 is the TCP port for SMB (Server Message Block) directly over TCP, used for Windows file and printer sharing, mapped network drives, Group Policy delivery and much remote administration. It is essential inside a Windows network and must never be reachable from the internet; the 2017 WannaCry outbreak spread through exposed 445.
What port 445 is used for
SMB is the protocol behind \\server\share. Over port 445 it provides:
- File and printer sharing, mapped drives,
net use. - Delivery of Group Policy and logon scripts from the
SYSVOLandNETLOGONshares on domain controllers. - Administrative shares (
C$,ADMIN$) used by remote management and deployment tools. - Named pipes that carry RPC for services such as the Service Control Manager, the registry and the print spooler.
- Hyper-V and SQL Server storage on SMB 3 file shares.
Every Windows machine listens on 445 by default because the Server service is always installed.
SMB versions
| Version | Introduced | Status |
|---|---|---|
| SMB 1 | 1980s–1990s | Insecure, removed from default Windows installs since 2017; disable everywhere |
| SMB 2 | Vista / Server 2008 | Supported; no encryption |
| SMB 3.x | Windows 8 / Server 2012 onward | Signing, encryption, multichannel; current |
Security considerations
Port 445 has been the vehicle for the most damaging worms of the past two decades (Conficker, WannaCry, NotPetya). The lessons are consistent:
- Block 445 at the internet edge in both directions. Inbound to stop attacks; outbound to prevent credential leakage, since Windows will happily send NTLM authentication to any server it is tricked into contacting.
- Disable SMB 1.
Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocolshows whether it is present. - Require SMB signing and enable SMB encryption for shares carrying sensitive data.
- Segment. Workstations rarely need to reach each other on 445; allow it to file servers and domain controllers only.
- Patch. SMB vulnerabilities are wormable by nature.
How to check port 445
Is something listening locally? On Windows, open Command Prompt and run:
netstat -ano | findstr :445A line in the LISTENING state means a local program has bound port 445; the last column is its process ID (PID). Match the PID in Task Manager (Details tab) or with tasklist /fi "PID eq <pid>". On Linux or macOS the equivalent is ss -tulnp | grep :445 or lsof -i :445.
Can you reach it on a remote host? PowerShell's built-in connection test attempts a TCP handshake:
Test-NetConnection fileserver01 -Port 445TcpTestSucceeded : True means the remote system accepted a TCP connection on port 445. False means the port is closed, filtered by a firewall, or the host is unreachable; the output's ping result helps tell those apart.
See the netstat and Test-NetConnection records for the full option sets.
Check which SMB version a connection negotiated:
Get-SmbConnectionThe Dialect column shows 3.1.1 on current systems. Get-SmbServerConfiguration shows whether signing and encryption are required on the local server.
Firewall considerations
The "File and Printer Sharing (SMB-In)" rule is enabled on the Private and Domain profiles when network discovery or sharing is turned on, and disabled on Public. Keep it that way, scope it to the local subnet where possible, and never forward 445 on a router.
On Windows, inbound rules live in Windows Defender Firewall with Advanced Security (wf.msc). A rule allowing port 445 only takes effect on the profile (Domain, Private, Public) it is assigned to. The command-line equivalent is netsh advfirewall firewall add rule; see the netsh record.
Frequently asked questions
Can I disable port 445 on Windows?
Blocking it inbound with the firewall (the default on the Public profile) stops other machines from reaching this PC's shares while the PC can still access shares elsewhere. Disabling the Server service (LanmanServer) closes the listener entirely but also breaks administrative shares and some management features.
What is the difference between 445 and 139?
Both carry SMB. 139 is SMB over the older NetBIOS session layer; 445 is SMB directly over TCP, introduced with Windows 2000. Modern systems try 445 first. NetBIOS on 137–139 can be disabled if nothing legacy needs it.
Is SMB encrypted?
SMB 3.0 and later can encrypt per share or server-wide, and SMB signing protects integrity. Neither is on by default for ordinary file servers, although Windows 11 24H2 enables signing by default. SMB 1 has no protection and should be removed.