Windows Server 2022 — SQL Browser port conflicts with third-party monitoring — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Named instance discovery fails and clients intermittently cannot resolve SQL instance ports. Monitoring agents competing for UDP 1434 can block SQL Browser responsiveness and break connection routing.

Environment & Reproduction

Occurs in environments with legacy instance discovery plus endpoint scanners or network telemetry collectors installed on the same host.

Get-Service SQLBrowser
netstat -ano | findstr :1434
Get-Process -Id (Get-NetUDPEndpoint -LocalPort 1434).OwningProcess

Root Cause Analysis

A non-SQL process binds or intercepts UDP query flows used by SQL Browser, or endpoint security policy throttles outbound response packets.

Quick Triage

Confirm ownership of UDP 1434 and inspect SQL Browser service health/events.

sc.exe query SQLBrowser
Get-WinEvent -LogName Application -MaxEvents 30 | Where-Object {$_.ProviderName -match 'SQLBrowser|MSSQL'}
Get-NetFirewallRule -DisplayName '*SQL*' | Select DisplayName,Enabled,Direction,Action

Step-by-Step Diagnosis

Validate instance network settings and compare dynamic/static port assignments to client connection strings.

Get-ChildItem 'HKLM:/SOFTWARE/Microsoft/Microsoft SQL Server'
Get-ItemProperty 'HKLM:/SOFTWARE/Microsoft/Microsoft SQL Server/MSSQL16.MSSQLSERVER/MSSQLServer/SuperSocketNetLib/Tcp/IPAll' -ErrorAction SilentlyContinue
Resolve-DnsName 

Solution — Primary Fix

Move SQL instances to static TCP ports, restart SQL Browser, and eliminate local agent binding collisions on UDP 1434.

Restart-Service SQLBrowser -Force
Restart-Service MSSQLSERVER -Force
New-NetFirewallRule -DisplayName 'Allow SQL TCP 1433' -Direction Inbound -Protocol TCP -LocalPort 1433 -Action Allow
New-NetFirewallRule -DisplayName 'Allow SQL Browser UDP 1434' -Direction Inbound -Protocol UDP -LocalPort 1434 -Action Allow

Solution — Alternative Approaches

Bypass SQL Browser dependency by updating clients to explicit server,port entries and disabling SQL Browser if no named-instance discovery is required.

Set-Service SQLBrowser -StartupType Disabled
Stop-Service SQLBrowser
# Update app connection strings to tcp:,

Verification & Acceptance Criteria

Clients should connect reliably with no discovery timeouts and no recurring SQL Browser bind warnings.

Test-NetConnection -ComputerName  -Port 1433
Get-WinEvent -LogName Application -MaxEvents 20 | Where-Object {$_.ProviderName -match 'SQLBrowser'}
Invoke-Sqlcmd -ServerInstance ',1433' -Query "SELECT GETDATE()"

Rollback Plan

If connectivity degrades after static port changes, restore previous SQL network configuration and re-enable SQL Browser.

Set-Service SQLBrowser -StartupType Automatic
Start-Service SQLBrowser
Remove-NetFirewallRule -DisplayName 'Allow SQL TCP 1433' -ErrorAction SilentlyContinue

Prevention & Hardening

Reserve SQL discovery/engine ports in endpoint management policy and run periodic socket ownership audits.

Get-NetUDPEndpoint | Where-Object {$_.LocalPort -eq 1434}
Get-NetTCPConnection | Where-Object {$_.LocalPort -in 1433,1434}

Related Errors & Cross-Refs

Related to SQL network interface errors, provider timeouts, and named instance resolution failures under mixed static/dynamic port deployments.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft SQL Server network configuration references, SQL Browser behavior docs, and Windows Firewall guidance for database services.