| Port | 138 |
|---|---|
| Transport | UDP |
| Service | NetBIOS datagram |
| Category | Windows networking |
| Range | well-known (0–1023, needs root to bind on Unix) |
| Encrypted | No, plaintext |
| Exposure | Private network or VPN only |
Port 138 NetBIOS datagram · UDP
NetBIOS Datagram Service: connectionless messages between Windows hosts, used for browser elections (the "Network Neighbourhood" master browser) and legacy messaging.
What runs on port 138
NetBIOS Datagram Service: connectionless messages between Windows hosts, used for browser elections (the "Network Neighbourhood" master browser) and legacy messaging. Noise on a modern network and a fingerprinting aid for anyone scanning it.
Software that uses it: Windows networking · Samba (nmbd)
Should port 138 be open?
Private network or VPN only. Nothing good comes from this port being reachable from the internet. Keep it on an internal network, reach it over a VPN or an SSH tunnel, and firewall it from everything that does not need it.
- Block 137–139 at the perimeter; SMB today uses 445 directly.
Check port 138
# on the host: is anything listening, and which process? ss -lunp 'sport = :138' sudo lsof -i :138 # from another machine: is it reachable? nc -zuv host 138 sudo nmap -sU -p 138 host
A port that answers from the internet when it should not is the finding; nmap from a machine outside your network (or a VPS) is the honest test, because scans from inside the LAN pass the firewall you are trying to verify.
Allow or block port 138
# ufw (Ubuntu/Debian) sudo ufw allow from 10.0.0.0/8 to any port 138 proto udp sudo ufw deny 138/udp # nftables nft add rule inet filter input ip saddr 10.0.0.0/8 udp dport 138 accept nft add rule inet filter input udp dport 138 drop # iptables (legacy) iptables -A INPUT -p udp --dport 138 -s 10.0.0.0/8 -j ACCEPT iptables -A INPUT -p udp --dport 138 -j DROP # firewalld sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=138 protocol=udp accept'
Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 138" with no source is just "open".
Related ports
Part of the port number reference. Ports are 16-bit numbers; see also the subnet calculator and the packet decoder, which shows ports inside TCP and UDP headers.
Questions
Is port 138 TCP or UDP?
UDP. NetBIOS datagram is datagram-based; TCP 138 is not used by it.
Is port 138 encrypted?
No, plaintext. Anything sent over it can be read by whoever is on the path, so it belongs on a trusted network or inside a VPN or SSH tunnel.
How do I check whether port 138 is open?
On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 138 and which process. From another machine, nc -zv host 138 -u or nmap -p 138 -sU host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).
Can NetBIOS datagram run on a different port?
Yes; the number is a convention, not a requirement. Changing it reduces log noise from scanners but does not add security, and every client, firewall rule and monitoring check then needs the new number. Keep the default unless you have a concrete reason.