prefixkit Ask an engineerAsk RU

Port 137 NetBIOS Name

NetBIOS name service of old Windows networking.

Protocol
UDP
Service
NetBIOS Name
Category
File sharing
Exposing to the internet
Do not expose

This is a UDP port: UDP reachability cannot be tested reliably with a simple connect; check firewall rules and packet counters.

Is it safe to open

File-sharing protocols are not designed for the internet: they leak data and spread ransomware. Keep them inside the LAN and give remote users a VPN or an HTTPS-based service instead.

How to open port 137

Open to everyone

# Linux iptables
iptables -A INPUT -p udp --dport 137 -j ACCEPT
# Ubuntu ufw
ufw allow 137/udp
# firewalld
firewall-cmd --permanent --add-port=137/udp && firewall-cmd --reload
# MikroTik
/ip firewall filter add chain=input protocol=udp dst-port=137 action=accept place-before=0 comment="port 137"
# Windows (PowerShell)
New-NetFirewallRule -DisplayName "Port 137 UDP" -Direction Inbound -Protocol UDP -LocalPort 137 -Action Allow

Only for your addresses

# allow only one address or network (replace 203.0.113.0/24)
iptables -A INPUT -p udp --dport 137 -s 203.0.113.0/24 -j ACCEPT
iptables -A INPUT -p udp --dport 137 -j DROP
ufw allow from 203.0.113.0/24 to any port 137 proto udp
/ip firewall filter add chain=input protocol=udp dst-port=137 src-address=203.0.113.0/24 action=accept
/ip firewall filter add chain=input protocol=udp dst-port=137 action=drop

If the server is behind a router, you also need a port forward (dst-nat). Behind ISP CGNAT (100.64.0.0/10 on the WAN) forwarding will not help: you need a public IP or a VPN.

What is listening

Check on the server

# what listens on the port
ss -lntup | grep ':137 '
netstat -ano | findstr :137   # Windows
lsof -i :137   # macOS

Related ports