CODEWITHSUNDEEP
sql-servertcpremote-access
Alexander
Alexander

Reputation: 20234

SQL Server TCP/IP times out

I have to connect to a fresh SQL Server Express 2017 on a machine not part of my domain. I have configured

I now tried to access from a remote computer, and got a timeout. I then tried to connect from the local SSMS, which works without special settings, but when under options, forced "Protocol: TCP/IP" is set, with the same credentials as before, I also got a timeout.

So am I right that I can rule out the firewall or problems finding the instance, and everything points towards a configuration issue in TCP/IP protocol, or did I overlook some setting?

EDIT: I have disabled Windows firewall, and no other firewall is installed on the computer. I have restarted the computer. I also found this article about PortQry and had a check - locally:

C:\Users\Administrator\Downloads>PortQry.exe  -n 172.17.41.124 -p UDP -e 1434

Querying target system called:

 172.17.41.124

Attempting to resolve IP address to a name...


IP address resolved to WIN-AECL8CJVS7E.test.local

querying...

UDP port 1434 (ms-sql-m service): NOT LISTENING

EDIT: I have run NETSTAT and it seems no port in the 14xx range is open at all, although the SQL Server Browser service is running. I must be missing something there...

Upvotes: 2

Views: 1269

Answers (1)

sepupic
sepupic

Reputation: 8687

You did not show your connection string, but I suppose you use your instance name here.

In order to connect to SQL Server the network library has to know 2 things: IP address and a port. Your instance is named and uses non-default port 1438.

So your connection string should use 172.17.41.124,1438 as server name, or, alternatively, you can use instance name like this: 172.17.41.124\EXPRESS2017 but SQL Server Browser should run.

Upvotes: 0

Related Questions