Comments on: What TCP Port is SQL Server running under?

By: Ian

Ian — Wed, 07 Sep 2011 17:29:56 +0000

Re:

“Turns out someone (no one owns up) created an alias directing it to the wrong port.”

How can this happen?

By: Colin

Colin — Wed, 29 Dec 2010 14:15:59 +0000

Hi Alan

Thanks for the reply but if you cycle your error log periodically this will not work because unless your SQL Server has been restarted since the last log cycle.

By: alan

alan — Tue, 28 Dec 2010 16:45:55 +0000

xp_readerrorlog 0,1,’listen’

By: ashwinjk

ashwinjk — Tue, 14 Dec 2010 11:29:25 +0000

Thanks a lot . The information helped me

By: mknopf

mknopf — Tue, 30 Nov 2010 20:05:46 +0000

Thanks a ton, I used the Configuration Manager to discover that my named instance was using a dynamic port of 1105.

By: Paul Els

Paul Els — Thu, 05 Feb 2009 06:09:51 +0000

Approx 2 weeks ago a developer comes running to me, his SQL Server instance is running, but one cannot connect to it.

Turns out someone (no one owns up) created an alias directing it to the wrong port.

It was clearly visible when starting that instance in single user mode and checking which port it is starting up on.

By: Now syndicating Colin Stasiuk and Tim Ford | Brent Ozar - SQL Server DBA

Now syndicating Colin Stasiuk and Tim Ford | Brent Ozar - SQL Server DBA — Tue, 03 Feb 2009 19:12:54 +0000

[...] What TCP Port is SQL Server running under? The default port for SQL Server is 1433, but when you run multiple instances of SQL Server on the same server, you have to do a little detective work to find the port number of each instance. [...]

By: K. Brian Kelley

K. Brian Kelley — Mon, 02 Feb 2009 15:44:49 +0000

Another way, if you’re on the system.

Task Manager
View | Select Columns | Check PID | OK
Find sqlservr.exe as the Image Name, note the PID
Command prompt:
netstat -ano | findstr *PID*

The PID is displayed in the far right. Look for the TCP entry. The port will be after the colon (e.g. 0.0.0.0:1433 means the port is 1433).