Yes I've read that article before. By "very well", I mean the "flow" of things in terms of what happens, i.e. the WSFC computer object is what needs access to...

Yes it is. As mentioned, I can connect to all instances (standalone and AG) from SSMS just fine.

The problem on AG instances is expanding the Databases node and querying user...

So just to repeat, all the SQL Server instances are LAN-based, domain joined and using domain accounts for the services.

I am simply having this problem connecting to any AG-based, domain-joined...

• This reply was modified 3 years, 6 months ago by lanky_doodle.
• This reply was modified 3 years, 6 months ago by lanky_doodle.

SQL auth has the issue.

The DMZ host is not domain joined so can't use Windows auth anyway (well not without trying to run SSMS as another user and specifying domain\username...

Has this ever worked?

Not from the DMZ host, no, but it is something that has only been needed very recently.

From everywhere else on the LAN both standalone instances and AG...

Yes, all SQL Services are using domain accounts (and those accounts have all the SPNs for Kerberos)

Using SQL auth

Blue question mark is 'part' of the problem, but not the only (biggest) problem. Though WMI is something I will look at.

• This reply was modified 3 years, 6 months ago by lanky_doodle.

I agree 100% is seems network related.

But why don't standalone instances have this issue. Why is it only AG instances. It's not like it's even hit and miss - all standalone...

• This reply was modified 3 years, 7 months ago by lanky_doodle. Reason: additional details

Thanks for both those replies.

Yes SQL Browser 1434 is allowed through the Windows firewall (and the DMZ rules are currently also in "allow all" mode from the DMZ device to...

PS: Running:

Test-NetConnection -Port 1433 -ComputerName <SQLHostname>

from the device in the DMZ comes back successful

Hi,

Thanks for the replies and sorry for the delay!

Basically we are moving to Availability Groups as the default HA option for SQL, however this comes with the downside of having...

Not per application, but per SQL Database Engine Instance - unless you are using these terms interchangeably. We have...

That ?? at the end was supposed to be a thumbs up!

I didn't think you can install multiple instances on the same Windows host anymore, at least that's what I'm reading for SQL 2019.

I mean connecting SSRS to the actual SQL...

PS: Before anyone says "upgrade everything to one instance". We have hundreds of DBs all from different suppliers who all have maximum supported versions 🙂