I'm a newbie for microsoft technologies and I'm having problems in connectivity part for SQL Server 2014. This is probably an easy issue but I'm stuck.

I've 4 servers. One of them is the Active Directory Domain Controller, one is the application server and the others are being used for SQL Servers. Since it's a connectivity issue, IP's for servers are; -AD DC : 10.6.0.100 ( Also the DNS Server ) -APP : 10.6.0.110 -SQL 1 : 10.6.0.120 -SQL 2 : 10.6.0.121

I've successfully created a failover cluster (DBCLUSTER) and set the IP address of the FC as 10.6.0.130( which is not an actual server IP, I really don't get this part.. ).

Later, I've created an AlwaysOn Availability Group for sql servers. I've successfully created the AG without listener. I could connect to servers from each other, database syncs without problem. Then, I've created a listener (AG-LISTENER) and set it's ip as 10.6.0.131 ( which is not an actual server IP, again? ) and set it's port to 5525. It gave no problems.

So I wanted to test connectivity. When I wanted to make connections from APP server to directly SQL 1or SQL 2, I can connect without problem. But when I try to connect to AG-LISTENER, it cannot find it on network. When I check the DNS records. I can see it as it's being hosted on 10.6.0.131.

When I tried to ping to AG-LISTENER from AD-DC, APP, SQL 2 servers, it responds that the destination host is unreachable (it's pinging 10.6.0.131 but the response comes from the IP's of AD-DC, APP and SQL 2 servers). It can connect from SQL 1 server, which is the primary for AG.

I've checked the firewalls, there's no problem. But I think this is an network issue which I have no clue.

PS: Servers are operating on Windows Server 2012 and are not being hosted on Azure.

Lets start with concepts.

The Cluster IP and the AG Listener IP are virtual IP addresses.  Windows Server Failover Clustering (WSFC) will bind and unbind those addresses to specific cluster nodes to enable connectivity.  WSFC arbitrates the use of the virtual addresses so that client applications are abstracted away from the underlying physical resources.  This is by design.

Ping will always respond from whatever physical NIC currently owns the virtual IP.  This has been driving firewall admins nuts for over ten years. 

Just for grins, you can see the Virtual objects in both Active Directory and in DNS.  I would check and see that these are as expected.

Troubleshooting.  You have most of the issues solved.  I would check SQL Server Management Studio as well as Failover Cluster manager and make sure all the AG resources are online.  The AG listener should connect to the primary replica from anywhere in the network.  Since you can connect to the underlying SQL instances, there is no connectivity or security issue.  You can use SQL Configuration Manager to inspect (DO NOT CHANGE ANYTHING!!) SQL server network bin

Just to confirm:

Where have you configured AlwaysON and SQL Server failover cluster?

Are these on same servers and what about failover part, are they sharing same disks among these clustered nodes?

Did you get any solution to your problem.

I am stuck with the same issue. I have a listener configured, I can query the sql database using SQLCMD from one of both data base server using listner and port 1433 but without SQL authentication user. So, if in my SQLCMD query I mention username -U and Password -P, it returns login failed for the user. 

I want the listner as part of my application server connection string. How can I achieve that ?

P.S. My application servers is are in a different subnet and cloud service then the database, WSFCnode and DC, but in same virtual network.

Thanks