May 2, 2017 at 8:03 am
Configuration:
I have setup an AlwaysOn availability group using SQL Server 2016 on Windows Server 2016 using 2 machines (separate data centers on different subnets) in a workgroup configuration without a domain. In creation of the Availability group, I also created a listener using the multiple subnet feature and set the port to 1433 (same port being used by the sql service on each machine). I was actually surprised that the listener created successfully as it is my understanding that when the listener is created, it gets registered and an entry is made in DNS.
Problem:
I am not able to successfully test (connect to) the listener even when on the host serving as Primary. When I attempt to connect to it via SSMS (even after setting MultiSubnetFailover=True and increasing the timeout). The connection attempt acts like it is not finding (resolving) the listener name and times out.
My question:
Does the AG listener still function in the same way in a workgroup configuration without a domain? Are there any differences in how connections should be made to the listener?
May 2, 2017 at 9:09 am
Don''t have a clue, but just wondering if you should really be using the same port as SSMS. Just seems like an increase in your "attack surface area" that perhaps isn't necessary? I could be way off base though...
Steve?(aka sgmunson)?:) 🙂 :)?
Health & Nutrition
Rent Servers for Income (picks and shovels strategy)
May 8, 2017 at 11:21 am
MG-253362 - Tuesday, May 2, 2017 8:03 AMConfiguration:
I have setup an AlwaysOn availability group using SQL Server 2016 on Windows Server 2016 using 2 machines (separate data centers on different subnets) in a workgroup configuration without a domain. In creation of the Availability group, I also created a listener using the multiple subnet feature and set the port to 1433 (same port being used by the sql service on each machine). I was actually surprised that the listener created successfully as it is my understanding that when the listener is created, it gets registered and an entry is made in DNS.Problem:
I am not able to successfully test (connect to) the listener even when on the host serving as Primary. When I attempt to connect to it via SSMS (even after setting MultiSubnetFailover=True and increasing the timeout). The connection attempt acts like it is not finding (resolving) the listener name and times out.My question:
Does the AG listener still function in the same way in a workgroup configuration without a domain? Are there any differences in how connections should be made to the listener?
it's just an AD disconnected cluster, It still uses DNS, are your DNS records correct?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply