Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4689

SQL Virtual Network Name not connecting

$
0
0
Hi,
I have configured two node SQL Failover Cluster on Windows Server 2012 R2 and SQL Server 2016 with default instance joined in a domain.

I have tested Failover in all possible way and it is working fine. This is not the first time I have configured FCI. I have been working on them quite a few years. But This time I am stuck into an issue which I am not able to recall what is wrong.



Everything is working fine except that I am not able to connect to SQL VNN from the passive node. e.g. If SQL is running on NodeA; I am able to connect to my SQL VNN name "VSQL" from NodeA (Open SSMS on NodeA and connect no issue) but I am not able to connect to SQL VNN from current passive node NodeB. Opposite is also true means when I failover to NodeB, I am able to connect from NodeB and not from NodeA.

All pings working fine except name resolution of SQL VNN.

The error is very generic: (Microsoft SQL Server, Error: 53) The network path was not found

Any suggestions please.



Cheers!!
Sunil

Kindly mark the reply as answer if they help


Viewing all articles
Browse latest Browse all 4689

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>