You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having issues validating connections to SQL domain instances through a SOCKS proxy (Proxifier on Windows). Does the Test connection process actually needs UDP at all ? Any tips of getting to work through SOCKS ? Get-SQLInstanceDomain | Get-SQLConnectionTestThreaded
I can confirm manually that the SQL instance is indeed running for a particular host, TCP 1433 is accessible. It still says 'not accessible' or 'no named instance found' when running Get-SQLConnectionTest or Invoke-SQLAuditDefaultLoginPw
I'm running PowerUpSQL without -Username -Password field, from runas /netonly session.
The text was updated successfully, but these errors were encountered:
I have had similar issues. When you say you can confirm manually does that mean there is an MSSQL SPN on set for that host in Active Directory? I'm asking because AFAIK that is what Get-SQLInstance domain uses: SPNs.
Hi,
I'm having issues validating connections to SQL domain instances through a SOCKS proxy (Proxifier on Windows). Does the Test connection process actually needs UDP at all ? Any tips of getting to work through SOCKS ?
Get-SQLInstanceDomain | Get-SQLConnectionTestThreaded
I can confirm manually that the SQL instance is indeed running for a particular host, TCP 1433 is accessible. It still says 'not accessible' or 'no named instance found' when running Get-SQLConnectionTest or Invoke-SQLAuditDefaultLoginPw
I'm running PowerUpSQL without -Username -Password field, from runas /netonly session.
The text was updated successfully, but these errors were encountered: