March 6, 2009 at 6:59 am
Does anybody know of any reason why a default instance install of SQL Server 2005 SP3 is not listening on Port 1434 for the Dedicated Admin Connection Support tool straight after the installation has been completed?
I have checked and Port 1434 is not being blocked by a firewall.
March 6, 2009 at 8:37 am
Have you checked that the DAC is enabled on the SQL Server Configuration Manager?
March 6, 2009 at 8:53 am
Hi John.
The DAC is enabled by default. I think you are getting confused with enabling the DAC to allow remote connections via the Surface Area Control Tool?
Regards
Carl
March 6, 2009 at 8:56 am
Hi Carl,
So you are attempting to use the DAC locally to SQL Server then?
You see the DAC will only permit local connections by default and so network connections are not enabled unless you permit them.
See below for reference.
March 6, 2009 at 8:59 am
Sorry John. I am just wondering why it is listening on a different port than the default port?
I haven't tried to use it.
March 6, 2009 at 9:14 am
You may also find the following article useful on identifying the ports that your SQL Server Endpoints are using and also the rules that are used for each.
March 6, 2009 at 9:15 am
Thanks for your help John, but I'm still no wiser on why it isn't listening on port 1434?
March 6, 2009 at 9:25 am
No problemo Carl.
So if you execute the following script is the DAC endpoint specified to listen on a specific port?
select * from sys.tcp_endpoints
If the value is set to 0 then it should be using the default rule and so the port will be dependant on what ports are specified in the TCP/IP protocol defined in the SQL Server Configuration Manager.
March 6, 2009 at 9:28 am
Hi John.
The port is set to 0 which is the default.
March 6, 2009 at 9:32 am
The TCP/IP protocol settings are the same as another server which is listening on the default port for the DAC?
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply