I could not establish a local DAC connection using SSMS while I was logged into the Sql-Server's Operating System's Remote Desktop. First reason was SQL-Browser Service turned off. Lateron, second reason I was pointed to was this "DAC is not activated" error:
"No DAC connection could be established on the default port. Make sure DAC is enabled".
I looked out for a solution. The suggested solution I found was to enable the "RemoteDacEnabled" Facet property or run
sp_configure 'remote admin connections', 1
This makes me wonder, why I should enable a REMOTEDacEnabled property in case I wanted to connect from LOCAL SYSTEM? Do I get REMOTE wrong here?
"The connection is only allowed from a client running on the server. No network connections are permitted."
If I HAVE TO logon from local server and NOT over the network, what sense does a REMOTE DAC setting ever make?
EDIT/part of the answer: The main reason for my question was, that I did NOT understand why we have to allow /enable the REMOTEDAC settings just in case we want to establish a LOCAL DAC connection from the server itself (that was what I tried with no luck in the first place).
NOW after giving it more tries I figured out that using...
caused this error connecting to DAC while...
DOES WORK (without activating the RemoteDac setting).
(Weird about this is that I can connect fine using a "normal" connection with both options)
Root cause was that the FQDN was interpreted to be a remote server and this caused the error above.
However, after I have enabled REMOTEDAC, both options from above work for a DAC, no matter if I try it local on the server or from remote clients.