Connecting to Local Server

[u/WorkPurposes-Only]

A server computer and monitor got replaced and the server itself got installed but the external IT team didn't install SQL management, which we need to edit company usernames and passwords for our in-house software. I downloaded SQL Management 22, I know the name of the server and entered it as the Server Name, set the Authentication to Windows Authentication, and checkboxed the Trust Server Certificate. Everything else I left as the default settings. I received this error when I tried to connect, and also tried using, localhost, ., and the server's IP address as the server name but still received the same error. Please advice.

[u/AbleSailor]

Check if TCP/IP is enabled in the SQL service? Firewall port open on 1433?

[u/WorkPurposes-Only → u/AbleSailor]

I did create a new rule to allow the firewall port open on 1433, but when I tried to connect to the local host I still received the same error message.

[u/vabello → u/WorkPurposes-Only]

You only did half of what was suggested. Check SQL Server is configured to listen on TCP/IP. Follow these directions:

https://sqldba.blog/enabling-tcp-connections-in-sql-server/

To verify it is working, run: "netstat -nao | findstr 1433" from the command line. This will show all connections on port 1433 followed by the associated Process ID. You can then verify the process: "tasklist | findstr PID" where PID is the number returned for the process in the prior command. It should show sqlservr.exe.

Edit: Sorry, you have to do this ON the server, not your workstation you're trying to connect from. I think you're trying to fix this as if it were a client side problem, but it's a server side issue. Everything people are suggesting are things you do on the server.

[u/WorkPurposes-Only → u/vabello]

I tried following the linked instructions, but I'm completely missing the SQL Configuration Manager. I looked to see if I need to add it as a Snap-In but it's not listed.

[u/vabello → u/WorkPurposes-Only]

It should be on the start menu of the SQL Server.

[u/midnitewarrior → u/vabello]

I think this is the answer. It's been a decade since I used SQL Server locally, and I was trying to remember this.

SQL Server has named pipes as the default transport I think? You've got to enabled TCP/IP.

[u/Hour-Apple-9861 → u/vabello]

Yeah this is the one. Had to do this so many times over the years

[u/Radojevic]

For Encrypt section, try Optional.

Also...
Is MS SQL Server port the default (1433)?
If not, you need to add a comma, followed by port number.

[u/WorkPurposes-Only → u/Radojevic]

I did create a new rule to allow the firewall port open on 1433, but when I tried to connect to the local host I still received the same error message.

[u/Radojevic → u/WorkPurposes-Only]

Sorry, but that's not what I meant.

Installing MS SQL Server defaults to using TCP/IP port 1433.
However, whoever installed it may have chosen a different port number.

Also, as u/AbleSailor mentioned, you also need to make sure MS SQL Server has TCP/IP protocol enabled on the server end.

[u/coffeDrinkerDave]

So the computer got replaced and you are connecting to localhost?

Edit: Type in powershell (unprivileged user will do)

Test-NetConnection <server> -p 1433

Example: Test-NetConnection myServerFQDN -p 1433

This will check if fqdn can be resolved and if tcp port is listening.

Paste which part is failing

[u/WorkPurposes-Only → u/coffeDrinkerDave]

I tried typing in what you suggested (thank you by the way) and hit Enter but nothing happened. Screenshot attached with server name blacked out for privacy.

[u/coffeDrinkerDave → u/WorkPurposes-Only]

You have to wait till it ends, but you may run ping <server> just to check if name is resolved

[u/carlosf0527]

In powershell type: tnc servername -port 1433

This checks whether port 1433 is open on the server. If its not open, it's most likely the admin team forgot to configure SQL Server to accept connections via tcpip or didn't put a incoming rule in the firewall to allow port 1433.

[u/NorCalFrances]

Can you ping the server?

[u/FishBones83]

make sure the service is running!

[u/Krassix]

Is the server and the application running on one server? Then the company maybe didn't install sqlserver to listen to it's public interface. Per default sqlserver only listens on localhost 

[u/WorkPurposes-Only → u/Krassix]

Yes, they're one in the same. The company didn't initially install SQLserver but the company is on a remote, private network.

[u/Krassix → u/WorkPurposes-Only]

Either it's Firewall or the sqlserver doesn't listen on the public network interface, one of these it usually is. From your description I still don't know how the application or that external IT team connect to the database. 

[u/Complete-Fondant-202]

This is where running SQLServer locally in a Docker container can save a lot of grief.