How to Connect to MSSQL Remotely from SQL Server Management Studio

Quick answer: To connect to MSSQL remotely from SSMS, enable SQL Server (mixed-mode) authentication, create a scoped SQL login, and connect using server-ip,1433 with SQL Server Authentication. If it times out, TCP/IP or the firewall is the cause; if login fails, the credentials are.

By default a MSSQL server accepts connections only from the local machine. To reach it from SQL Server Management Studio (SSMS) on your own computer, three things must be in place: mixed-mode authentication, a remote-enabled server, and an open firewall port. This guide covers the SSMS side; the companion article covers enabling TCP/IP and the firewall.

1. Enable SQL Server (mixed-mode) authentication

Remote tools usually connect with a SQL login rather than a Windows account. In SSMS on the server, right-click the server name, choose Properties > Security, and select SQL Server and Windows Authentication mode. Restart the SQL Server service for the change to take effect.

2. Create a SQL login for remote access

Under Security > Logins, add a new login, set a strong password, clear "Enforce password policy" only if your policy requires it, and map the login to the target database with the rights it needs. Grant the minimum required - avoid using the sa account for day-to-day connections.

3. Connect from your computer

Open SSMS on your PC and enter:

Server name:      your-server-ip,1433
Authentication:   SQL Server Authentication
Login / Password: the login you created

The comma before 1433 is required when specifying the port. If you changed the SQL port, use that number instead.

4. If the connection times out

A timeout almost always means TCP/IP is disabled or the firewall is blocking the port, not a credential problem. Work through enabling TCP/IP and opening port 1433 (see the related article), then retry. A "login failed" message, by contrast, means the server was reached but the credentials or database mapping are wrong.

Frequently asked questions

Why must I put a comma before 1433?
The comma tells SSMS the number is a port; use it whenever you specify the port explicitly.

Should I use the sa account?
No - create a dedicated login with only the permissions it needs, and keep sa for emergencies.

MSSQL runs best on Windows, and every SoftSys managed Windows VPS can be provisioned with SQL Server pre-configured for secure remote access, including the firewall rules and a scoped login, so you can connect from SSMS on day one.