http://blogs.msdn.com/b/sql_protocols/archive/2008/11/05/tcp-listening-ports-and-endpoint-ports-behavior.aspxEndpoint configuration seems to be creating some confusion. I hope that this will clarify some of the behavior as it applies to TCP endpoints. With a default configuration of SQL Server, try the following: &gt; select name, port, is_dynamic_porten-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/sql_protocols/archive/2008/11/05/tcp-listening-ports-and-endpoint-ports-behavior.aspx#9463000Fri, 06 Mar 2009 19:24:57 GMT91d46819-8472-40ad-a661-2c78acb4018c:9463000Carl R<p>I am just wondering why a default instance install is not listening on Port 1434 for the DAC? &nbsp;The firewall is not blocking Port 1434 either?</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9463000" width="1" height="1">http://blogs.msdn.com/b/sql_protocols/archive/2008/11/05/tcp-listening-ports-and-endpoint-ports-behavior.aspx#9413230Wed, 11 Feb 2009 22:11:04 GMT91d46819-8472-40ad-a661-2c78acb4018c:9413230DonnaO<p>In SQL Server 2008, do you have to create a TCP Endpoint if you want SQL Server to listen to a specific IP Address and a specific port? In SQL Server Configuration Manager, the TCP/IP protocol is enabled and all the Dynamic TCP Ports and TCP Port fields for each IPx has been cleared except for one IP address. (As directed in <a rel="nofollow" target="_new" href="http://msdn.microsoft.com/en-us/library/ms177440.aspx">http://msdn.microsoft.com/en-us/library/ms177440.aspx</a>) On that one IPx the TCP Port has been set to 2505 and on the IPAll the TCP Port has been set to 2505. If the “Listen All” property is set to “No”, then remote client connections cannot connect to the server. If the “Listen All” property is set to “Yes”, then remote client connections can connect to the server. Is SQL Server really listening on all ports or does having the TCP Port set on the one IPx and the IPALL stop SQL Server from listening on all ports? The concern is an external firewall (not the Windows Firewall) requires a specific IP Address and Port number. This article (<a rel="nofollow" target="_new" href="http://msdn.microsoft.com/en-us/library/ms191220.aspx">http://msdn.microsoft.com/en-us/library/ms191220.aspx</a>) seems to indicate that a TCP endpoint is needed to override the default TCP endpoint. This installation is SQL Server 2008 (64-bit) Developer Edition with CU3 on Windows Server 2008 Standard SP1.</p> <p>In SQL Server 2005, the “Listen All” property was set to “No” and only one IPx had the TCP Port set to a specific number. And this seemed to work for remote client connections.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9413230" width="1" height="1">