Default instance. Telnet to the SQL port from the server itself. TCP port number is stored in a value called TCPPort under the TCP/IP registry key for a SQL Server instance. (Specifying a port number is often necessary if the SQL Server Browser service is not running on the host computer.) If you plan to connect remotely, you might also need to open the SQL Server TCP port (default 1433) on your firewall. 2. To connect using a different port specify the servername, a comma, and then the port number as shown in this post. It applies to routine connections to the default installation of the Database Engine, or a named instance that is the only instance running on the computer. This is the most common port allowed through the firewall. – joeqwerty Aug 29 '12 at 19:34 Client systems use TCP 1433 to connect to the database engine; SQL Server Management Studio (SSMS) uses the port to manage SQL Server instances across the network. Port. Second, nmap doesn't do such a great job fingerprinting SQL Server listening on an alternate port. SQL Server client library connects and sends a UDP message using port 1434. At this point, SQL Server is running on your Ubuntu machine and is ready to use! Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Cost-effective hosting solutions backed by our superb 24x7x365 live chat support. Make sure that TCP connections to the port are not blocked by a firewall. Here we list the location for each product. You only need to enable the port on Windows Firewall if … SQL Server default instance running over TCP. Port. APPHOST,2828 Connection to a default instance that is not listening on the default TCP port, by specifying both the IP address and the TCP port that is being used, in this case 2828. There are so many possible combinations that when it checks a port, it's looking for what is likely to be there. Microsoft's SQL Server Management Studio will connect by default to port 1433 and there's nowhere in the connect dialog to specify a different port from the default. TCP port 1433. SQL Server is not likely to be on port 21675, so it doesn't make sense to try … SQL Server is likely to be on 1433, so nmap does a good job fingerprinting it. Your SQL Server is now listening on the Port you have specified. For different SQL Server products, the location of the TCP/IP registry key is different. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP/IP connections to the port.” Reason: @apomene >>>Have in mind that if SQL Express is the only SQL server in this PC you can also use: [my servername],1433 or [serverIP],1433<<< If the port of Express is not 1433, be it the only server or not, you cannot connect to it using wrong port number – sepupic Oct 19 '17 at 7:40