SQL Server replication requires the actual server name to make a connection to the server. - by Kurt Moskal

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 365761 Comments
Status Closed Workarounds
Type Bug Repros 5
Opened 9/2/2008 12:44:09 PM
Access Restriction Public


I was hoping this “feature” would have been change with SQL Server 2008 but it’s not.  When using any of the Management Studio wizards I get a message box with the following error:
SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name, 'XXXXXXXXXXXX\XXXXXXXXXXXX'. (Replication.Utilities).
This only occurs when connecting using the tools installed on my workstation. When using the tools on the server the problem doesn’t occur. 
Problem background, when I connect from my workstation, I must manually provide the TCP/IP port. We don’t use the default port of 1433 and we also disable the SQL Browsers service since we don’t want SQL to respond to “noise” neighbors.  Thus when I connect to SQL from my workstation I must either create a server alias or provide the port.  Something in the tool doesn’t like this. Please correct the problem as it make both setting up replication and replication monitoring very difficult.
Sign in to post a comment.
Posted by Saurabh Sinha DBA on 3/25/2015 at 8:25 PM
In2014 , I am getting different error :-)
Posted by HLaRoux on 8/22/2014 at 10:23 AM
Still an issue in SSMS 2014 :-(
Posted by Iain Elder on 3/5/2014 at 8:11 AM
This is still an issue in SSMS 2012.

I can't see the properties of a publication in object explorer if I connect to the publisher using a DNS alias.

The stupid thing about this is that SSMS actually responds with the actual server name in the error message.

Why can't SSMS just create a new connection with the actual server name it already knows?
Posted by ncPip on 6/12/2011 at 1:34 AM
I also get this error if I use the fully qualified DNS name of the server.
Posted by Microsoft on 9/10/2008 at 10:13 AM
This is by design, we are looking into removing this limitation in a future release