SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Regarding Mirroring setup - TCP/IP network issue


Regarding Mirroring setup - TCP/IP network issue

Author
Message
SQLisAwE5OmE
SQLisAwE5OmE
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10541 Visits: 3113
Hi Team,

I tried setting up DB mirroring between PRD & DR side and I am getting the below error.
I checked firewall, all good, connected via telnet from PROD to DR and vice versa.
Msg 1418, Level 16, State 1, Line 1
The server network address "TCP://199.199.99.99:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.

Any idea what else can cause this problem?.....I have had this error many times and each time I troubleshoot the issue/resolution is different, so I couldn't find the exactly solution any time.

Both my PROD and DR SQL Server running under "Local Systems", not sure if this is the problem?

Can someone provide any hint. Thanks.

Regards,
SQLisAwe5oMe.
RandomStream
RandomStream
SSCrazy
SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)

Group: General Forum Members
Points: 2037 Visits: 645
SQLisAwE5OmE - Friday, January 12, 2018 2:37 PM
Hi Team,

I tried setting up DB mirroring between PRD & DR side and I am getting the below error.
I checked firewall, all good, connected via telnet from PROD to DR and vice versa.
Msg 1418, Level 16, State 1, Line 1
The server network address "TCP://199.199.99.99:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.

Any idea what else can cause this problem?.....I have had this error many times and each time I troubleshoot the issue/resolution is different, so I couldn't find the exactly solution any time.

Both my PROD and DR SQL Server running under "Local Systems", not sure if this is the problem?

Can someone provide any hint. Thanks.

Congrats. This is the most frustrating part of configuring mirror and I love it. Pinal Dave blogged about this extensively at sqlauthority.com but unfortunately I can't find it at this moment.

I assume that you had followed Microsoft's mirroring guide to the letter.

Try these (not in any particular order)
1. on each box, try to telnet to port 5022 of the partner. If 5022 is up and listening, you will get a blank screen - meaning you can connect to it;
2. use hostname, and add an entry to C:\Windows\System32\drivers\etc\hosts, then use 'TCP://hostname:5022' instead;
3. query endpoint (select * from sys.endpoints) and make sure endpoint exists;
4. if you used certificate for authentication, check and compare certificate thumb prints on both partners. Sometimes, after repeated attempts, there will be a mismatch;
5. create a rule for port 5022 on Windows firewall;
6. turn off firewall completely on both partners;
7. delete endpoints, certificates and logins that you created for mirroring and start from scratch;
8. if you have support with Microsoft, let them figure it out free of charge.

Update: also use 'netstat -na' on each host to check whether there are free tcp/ip ports available. When all 65000 ports are exhausted, the partners won't be able to talk.

RandomStream
RandomStream
SSCrazy
SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)

Group: General Forum Members
Points: 2037 Visits: 645
Here it is.

SQL SERVER – The server network address “TCP://SQLServer:5022” can not be reached or does not exist.
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (182K reputation)SSC Guru (182K reputation)SSC Guru (182K reputation)SSC Guru (182K reputation)SSC Guru (182K reputation)SSC Guru (182K reputation)SSC Guru (182K reputation)SSC Guru (182K reputation)

Group: General Forum Members
Points: 182702 Visits: 18537
SQLisAwE5OmE - Friday, January 12, 2018 2:37 PM
Hi Team,

I tried setting up DB mirroring between PRD & DR side and I am getting the below error.
I checked firewall, all good, connected via telnet from PROD to DR and vice versa.
Msg 1418, Level 16, State 1, Line 1
The server network address "TCP://199.199.99.99:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.

Any idea what else can cause this problem?.....I have had this error many times and each time I troubleshoot the issue/resolution is different, so I couldn't find the exactly solution any time.

Both my PROD and DR SQL Server running under "Local Systems", not sure if this is the problem?

Can someone provide any hint. Thanks.


can you telnet to the port and ip from the partner server?
verify if the local firewalls are enabled and also whether there is a corporate firewall between the 2 endpoints

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Arsh
Arsh
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: General Forum Members
Points: 3261 Visits: 888
SQLisAwE5OmE - Friday, January 12, 2018 2:37 PM
Hi Team,

I tried setting up DB mirroring between PRD & DR side and I am getting the below error.
I checked firewall, all good, connected via telnet from PROD to DR and vice versa.
Msg 1418, Level 16, State 1, Line 1
The server network address "TCP://199.199.99.99:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.

Any idea what else can cause this problem?.....I have had this error many times and each time I troubleshoot the issue/resolution is different, so I couldn't find the exactly solution any time.

Both my PROD and DR SQL Server running under "Local Systems", not sure if this is the problem?

Can someone provide any hint. Thanks.

Taking further, you need to have a service account for running both the SQL servers.
Mirroring configuration then needs that account for the set up.
Also , check if you can connect to either of the SQL servers from INSIDE either servers through SSMS.
Make sure the ports for SQL server are bi directionally open.

Arsh
Arsh
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: General Forum Members
Points: 3261 Visits: 888
Arsh - Monday, February 19, 2018 11:11 AM

Taking further, you need to have a service account for running both the SQL servers.
Mirroring configuration then needs that account for the set up.
Also , check if you can connect to either of the SQL servers from INSIDE either servers through SSMS.
Make sure the ports for SQL server are bi directionally open.

Best to use the same AD Account at principal and mirrored.

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search