SQL Server Browser
What is Port 1434?
Port 1434 is used by the SQL Server Browser service, which provides connection information for named SQL Server instances. When multiple SQL Server instances run on the same machine, each named instance listens on a dynamically assigned port. The Browser service on UDP 1434 acts as a directory — when a client requests a connection to a named instance, the Browser service tells the client which port that instance is using. The Browser service also responds to SSRP (SQL Server Resolution Protocol) requests. This port gained notoriety in 2003 when the SQL Slammer worm exploited a buffer overflow vulnerability in the SQL Server 2000 Resolution Service, causing widespread internet disruption by flooding networks with UDP packets.
Common Uses
- SQL Server named instance discovery
- Dynamic port resolution for SQL Server instances
- Multi-instance SQL Server environments
- Client connection routing to correct instance
Technical Details
Copy-paste commands to check port 1434 (SQL Server Browser) from your terminal
Test connectivity
nmap -p 1434 -sU -sV example.com
(echo > /dev/tcp/example.com/1434) 2>/dev/null && echo "open" || echo "closed"
Open port in firewall
sudo ufw allow 1434/udp
sudo iptables -A INPUT -p udp --dport 1434 -j ACCEPT
sudo firewall-cmd --permanent --add-port=1434/udp && sudo firewall-cmd --reload
Security Considerations
The SQL Slammer worm (2003) exploited port 1434 and spread globally in minutes. Always keep SQL Server patched. If the Browser service isn't needed (single instance or static ports), disable it. Never expose port 1434 to the internet. Use static port assignments for SQL Server instances and connect directly rather than relying on the Browser service.
Popular Ports Reference
The most commonly used and referenced network ports