Quantcast
Channel: SQL Server Database Engine forum
Viewing all articles
Browse latest Browse all 12963

The server network address“TCP://SS72:7022″ cannot be reached or does not exist.

$
0
0

SQL Mirror setup error

I am trying to set up mirroring between two SQL Server 2012 instances. I get the error:

 

The server network address “TCP://SS72.local:7022” can not be reached or does not exist…

 

I have searched many blogs and MS sites for s solution, but none that I have found / implemented have worked.

Primary server:  Win 2008R2, SQL Server Ent. 2012 SP1, on working group (not domain), name = SS70

Secondary server:  Win 2008R2, SQL Server Ent. 2012 SP1, on working group (not domain), name = SS72

The servers are in different parts of the country, on different working groups, no domains.

I have:

  1. Followed http://technet.microsoft.com/en-us/library/ms191477.aspx in creating Db master key, encrypted certificates, and endpoints.
  2. I go through the mirror wizard, and everything is successful until I try to actually start mirroring.
  3. Verified that the ‘MLB-mirror’ SQL Server user can login to it’s SQL instance.

 

I have tried to make the following changes (according to solutions that have worked for some)

  1. Verified that ports were being listened to (netstat –na | find 7022).
  2. Changed the Log On As for SQL Services to local system (instead of NT Authority) on both systems.
  3. Tried IPs instead of computer names in mirror setup wizard.
  4. Added ‘local’ to "Primary DNS Suffix of this Computer" text box on both servers, and then tried the full name of SS70.local:7022.
  5. Added each server to the other servers hosts file, including a 2<sup>nd</sup> line for the hostname.local option.

I think it is an authentication or permission problem, but I cant seem to find it. I have seen a message about adding an authentication line on the endpoint creation code, but I am not using a domain.  Not sure how that would go.


Viewing all articles
Browse latest Browse all 12963

Trending Articles