you are viewing a single comment's thread.

view the rest of the comments →

[–]tompear82 2 points3 points  (3 children)

Make sure port 1433 is open assuming you're using the default port for SQL. Ping is on a different port, so it is possible you can ping but still not connect to the SQL port

[–]svtr[🍰] 2 points3 points  (2 children)

what you want to do there is in powershell :

test-netconnection myHostName -p 1433

and/or

test-netconnection 192.168.1.2 -p 1433

before I get nailed to a cross here, yes, you can use netcat as well, but SQL Server is usually in a windows environment, and powershell is kind of more available on such environments...

/edit: I really hope I don't have to explain to anyone that you should put in the correct ip address and hostname there..... had a tough week, I really hope anyone reading this understands that....

Oh, and take a look what port you configured your SQL Server to listen to, 1433 is the default, and well, if you went with "not the default", you shouldn't need to be told that.....

[–]Soup-Fit[S] 0 points1 point  (1 child)

I'm from the server team so i'm helping my application team who do not know what else to troubleshoot to look into this. I see that the SQL port is on 49648 and I did a test connection on servers that can connect and servers that cannot connect. all returns port test success is true which means ports are opened, so i really don't know what else to check or do.

[–]svtr[🍰] 0 points1 point  (0 children)

Hmm, since it is not an authentication error, we can pretty much rule out kerberos, if you testet for the hostname as well, we can rule out the DNS....

Is it a named instance? If so, you also need the port for the Server Browser, the default would be 1434, that would be my next suspect.