This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 23%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAA%3C/text%3E%3C/svg%3E)
We are unable to connect to Synapse dedicated pool through Synapse Data Studio as well as SSMS from last few days randomly. We are getting can't connect to synapse server. We have all the network firewall in place. The additional details explains that a network related or instance specific error occurred while establishing connection to server. (Provider: Named Pipes provider, error:40 - Could not open a connection to SQL server). The network path was not found.
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
Maybe changing DNS servers can help you.
Hey, Can you please confirm whether you are able to access the dedicated pool via portal query editor at the time when you are unable to access from ssms or data studio
Answer accepted by question author
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(86.4, 36%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBM%3C/text%3E%3C/svg%3E)
The issue was resolved by whitelisting the IP address by adding the IP address to the access control list. This allowed connection to the dedicated SQL endpoint.
Have you tried with Azure Data Studio ? it should not be any difference but last week I had a similar issue and it worked for me
Getting same thing from Azure Data Studio.
Maybe changing DNS servers can help you.
If the Named Pipes protocol is causing issues, you can use other connection protocols like TCP/IP.
In SSMS, you can specify the protocol in the connection properties. For Synapse Data Studio, use the connection string with the specified protocol.
Thank you, Vahid Ghafarpour
Hello Ashu Anand,
I am checking to see if you got a chance to look into the above answer provided by Vahid. Please let us know if you have any further questions.
If this answers your question, please consider accepting the answer by hitting the Accept answer and up-vote as it helps the community look for answers to similar questions.
Hi Vahid I am getting the same error while changing to TCP protocol also.
Hello Ashu Anand,
Can you please try using Data Studio?
How to open Synapse Data Studio with connection string and specified protocol?
You can't open Synapse Data Studio with a connection string and specified protocol.
I want you to try from "Azure Data Studio" and see if you are getting the same error.
We don't use Azure Data Studio for connecting to the dedicated pool right now. I have to get it installed and then check the connectivity.
I tried using Azure Data Studio and getting the same error message.
Thanks for the details.
Can you please test the port connectivity using the below PS command?
You should see TcpTestSucceeded : Ture
Test-netconnection -computername 'test.sql.azuresynapse.net' -port 1433
I am getting below while running the above command.
Thank you for the details.
Most likely, the issue could be with the firewall(the firewall could block the connection). Can you please check with your Network admin?
The IP addresses are allowed in the firewall settings.
Hello Ashu Anand,
Since TcpTestSucceded: False, it only has to do with the firewall or the port.
I would suggest opening a support case so that the support engineer can live troubleshoot the issue.
If you don't have a support plan, please let me know so I can enable a one-time free support request.
I am looking forward to hearing from you.
Also why it is trying to connect to a private ip instead of a public ip address?
Also why it is trying to connect to a private ip address instead of public ip address for the server?
Hello Ashu Anand,
Glad to know the issue is resolved. Can you please give us more specifics about the resolution?
Are you not using the dedicated SQL pool endpoint while connecting using SSMS or Azure data studio?
Your answer would be helpful for other community members looking for a similar issue.
We took up with the network team of the client and they added it to the access list. After that we are able to connect to the dedicated sql endpoint. Yes, We are using the same dedicated sql endpoint to connect through SSMS.
Hello Ashu Anand,
Thank you so much for the details. I have added your resolution steps in the answer section.
If you could accept the answer it will help other community users looking for answers to the similar issue.
Have a great weekend.