[ACCEPTED]-Error connecting to all of my SQL servers-ssms
The question seems to have been answered, but 7 I wanted to chime in. For some providers, such 6 as SQL Server, there is a parameter in connection 5 string which lets you connect to server 4 encrypted even if certificate is unknown: "TrustServerCertificate=True", so 3 if you include that in a connection string, you 2 will connect and work encrypted, and will 1 not have to run connection non-encrypted.
Try this...
Its gotta be a client issue if 12 you lost connection to all your remote servers 11 and your coworkers are fine. You probably 10 got "clicky" and changed some settings inadvertantly.
Open 9 your client network utility (mine is here: C:\WINDOWS\system32\cliconfg.exe). Under 8 the General Tab, check out the disabled 7 protocols. They should all have "force 6 protocol encryption" unchecked. If this is checked 5 for any of those values, your local SSMS 4 is probably trying to force an encrypted 3 connection and failing.
Report back if this 2 doesn't work, and I'll poke around a bit 1 more.
When connecting using MS SQL Server Management Studio in the connect window 1 go to Options->Connection Properties and check checkbox Trust server certificate
You connect to your SQL Servers requesting 13 encrypted connections and you don't trust 12 the certificate(s) used by those servers. Why 11 that happens depends on a myriad or reasons.
- Do your servers use self-signed certificates or PKI issued certificates?
- Who is the PKI authorithy that issued your certificates? Is it a corporate certificate service?
- Does your computer trust the PKI root authority?
If 10 you don't know the answers to this, you 9 must contact your network and security administrators. Simply 8 disabling protocl enforcing requirement 7 from your client may be against corporate 6 policy, or the servers may enforce SSL anyway 5 disregarding your local setting.
These are 4 all questions you should ask your own environment 3 admins, not public forums. You should try 2 to solve the issue, not hack your way arround 1 it and end up with a non-compliant machine.
From this link:
Disable client-side Force 6 Encryption on the server. On the machine 5 that runs the SQL Server instance, open 4 up the SQL Server Configuration Manager, right-click 3 SQL Native Client Configuration, and set 2 Force Protocol Encryption to No. Then 1 try connecting locally.
http://blogs.msdn.com/sql_protocols/archive/2005/12/22/506607.aspx
I got this error, I tried to connect a remote 3 server SQL (SaaS) in MS Cloud I added a 2 new firewall rule in Azure portal with my 1 client IP that solved my issue
- Open Command Prompt: press Windows Key+ R then type cmd and run
Enter this:
runas /user:[YourDomainName]\[YourActiveDirectoryUserName] /netonly cmd
Enter your active directory password 1 and press enter
- In New Command Window enter your SSMS.exe Path with double cotation like:
"C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Binn\ManagementStudio\Ssms.exe"
- Then login with windows athentication
More Related questions
We use cookies to improve the performance of the site. By staying on our site, you agree to the terms of use of cookies.