Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I just setup SQL Server 2012 (on Windows Server 2012) Always On feature and have a problem with connecting to SQL Server Listener from non-primary node (it works from primary node though).

Here is the scenario:

2 nodes in different subnets: 
   SQL1 (primary)
   SQL2 (secondary)
  Name: SQLPROD1
  Port: 1433
  Subnets       IP address

I can connect to SQLPROD1 in SSMS on primary node (either SQL1 or SQL2) but can't connect (not even ping) SQLPROD1 from secondary or from any other client in the network.

I checked firewall and it doesn't seem to be the cause of the problem. I can ping SQL1 or SQL2 from any client but can't ping SQLPROD1.

Beside this, everything else works in Always On. I can successfully fail-over and see databases on other node.

share|improve this question

migrated from Mar 7 '14 at 13:35

This question came from our site for professional and enthusiast programmers.

Are you sure that the hostname is resolving to the right IP address, or resolving at all? That would be my first verification. – Thomas Stringer Mar 7 '14 at 18:45
Have you verified the listener is configured for both subnets? – Steve Mangiameli Jan 16 '15 at 19:43
did you get to resolve this issue? I am still facing the same :( – Ganesh Hegde Oct 20 '15 at 7:23

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.