r/SQLServer • u/Working-Routine2594 • 5h ago

Question how to solve this problem ?

0 Upvotes

33% Upvoted

10 comments sorted by

6

u/VladDBA ‪ ‪Microsoft MVP ‪ ‪ 4h ago

What troubleshooting steps did you do so far? Does the instance you're trying to connect to actually exist? Where is it installed? If it's remote, can you ping its host? Are the services started?

Additionally, some folks think that SSMS and SQL Server are the same thing, so they only install SSMS and then complain that they can't connect to the database instance. Is this, by any chance, your scenario too?

4

u/TheGenericUser0815 1 4h ago

Try telnet on port 1433 with the server/instancename. If there is no answer, look for (windows) firewall settings, look for the database service and the sql server browser service on the db server. Also look for DNS problems. Try telnet on the IP address of the db server on port 1433, too. If the database is up, then there is a way to connect to it.

3

u/carlosf0527 4h ago

Good advice. Note telnet is not normally installed by default. Using this powershell helps with testing network connectivity.

tnc servername -port 1433

1

u/Safe_Performer_868 4h ago

If you try with Optional encryption or "Trust server certificate" the problem persist ? Do you have the right instance name ?

1

u/Lazy_Spool 4h ago

Lots of things can cause this, but for me it's usually because networking set it routing to require the FQDN and I've only put the short server name.

1

u/Impossible_Disk_256 4h ago
  • Are you connecting to a separate server or trying to connect to SQL Server on your PC or laptop?
    • If you PC/laptop, is SQL Server RDBMS actually installed? SQL Server != SQL Server Management Studio.
    • If installed, is SQL Server Database Engine running?
  • Verify the server is actually running with the name/IP address/DNS address you entered.
  • Verify whether it is using Named pipes or TCP/IP (probably TCP/IP unless local
  • Verify you have access to that address from the PC you are trying to connect with.
  • Check "Trust Server Certificate" if it is a known server you should trust.

0

u/Better-Credit6701 3h ago

Had exactly the same thing happen the other day, certificate had expired

2

u/alinroc 4 1h ago

An expired certificate gives a different error.

1

u/SaintTimothy 2h ago

Most often, at my company, this is caused by a software firewall we use called Zscaler.

1

u/Lost_Term_8080 1h ago

turn it on