I installed MS SQL Server 2014 on a machine that had an MS SQL Server 2012 default instance.

On the local machine, I can connect to both instances using named pipes. However, from a remote client, I can only connect to the default instance using named pipes. I can connect to both instances remotely if I use TCPIP. I do not understand why I cannot connect to the named instance remotely.

Any ideas? I have checked the usual configuration etc.


Verify your remote named pipe connection string, for a named instance the format is



  • Thank you very much. I appreciate your help. This was my first named instance setup. – Tesh Oct 13 '19 at 19:15
  • I'm happy to help. Please let me know if that does the trick for you, otherwise we'll keep at it until solved. – Rob Pearson Oct 13 '19 at 19:58
  • Thank you very much Rob, this did the trick. I got a bit confused. On the PC where I have SQL Server named instance installed, I can use<computer_name>\<instance_name> and that worked. So without thinking, I was trying the same on my client PC connecting to the server. What I do not understand, is at work they have many many SQL Server Instances on different servers and we never have to use \\<computer_name>\pipe\MSSQL$<instance_name>\sql\query. We only use <computer_name>\<instance_name>. – Tesh Oct 13 '19 at 22:21
  • I'm not sure from what you said, but I would guess that it's a TCP/IP thing vs. Named Pipes. – Rob Pearson Oct 14 '19 at 0:57

Google for: ms sql connect via tcp/ip site:microsoft.com

One of the first links leads to: Configure a Server to Listen on a Specific TCP Port

  • Thanks the TCP was working as expected but the named instance did not. I am learning about SQL Server. – Tesh Oct 13 '19 at 19:16

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.