Comments on: “under current configuration sql server studio express doesnot support remote connection”. http://linwinsysadmin.com/blog/Window/under-current-configuration-sql-server-studio-express-doesnot-support-remote-connection.html Wed, 07 Jan 2009 18:28:23 +0000 http://wordpress.org/?v=2.6.2 By: Ron http://linwinsysadmin.com/blog/Window/under-current-configuration-sql-server-studio-express-doesnot-support-remote-connection.html#comment-6 Ron Tue, 24 Jul 2007 19:08:17 +0000 http://blog.linwinsysadmin.com/?p=6#comment-6 Thank you for this post. This also worked for me in the Microsoft Client. In the ODBC, Client Configuration (Edit Network Library Configurations) I choose Named Pipes. Server Alias, Server Name, & Pipe Name populated automatically. For some reason Microsoft did not populate the Pipe Name correctly. I had manually enter the following as the Pipe Name: [\\MachineName\pipe\mssql$InstanceName\sql\query] Again thanks for your post. For some reason the MachineName and InstanceName were not published in this reply. Thank you for this post. This also worked for me in the Microsoft Client. In the ODBC, Client Configuration (Edit Network Library Configurations) I choose Named Pipes.
Server Alias, Server Name, & Pipe Name populated automatically.

For some reason Microsoft did not populate the Pipe Name correctly. I had manually enter the following as the Pipe Name:
[\\MachineName\pipe\mssql$InstanceName\sql\query]

Again thanks for your post.

For some reason the MachineName and InstanceName were not published in this reply.

]]> By: Ron http://linwinsysadmin.com/blog/Window/under-current-configuration-sql-server-studio-express-doesnot-support-remote-connection.html#comment-5 Ron Tue, 24 Jul 2007 19:07:54 +0000 http://blog.linwinsysadmin.com/?p=6#comment-5 Thank you for this post. This also worked for me in the Microsoft Client. In the ODBC, Client Configuration (Edit Network Library Configurations) I choose Named Pipes. Server Alias, Server Name, & Pipe Name populated automatically. For some reason Microsoft did not populate the Pipe Name correctly. I had manually enter the following as the Pipe Name: [\\>\pipe\mssql$>\sql\query] Again thanks for your post. For some reason the MachineName and InstanceName were not published in this reply. Thank you for this post. This also worked for me in the Microsoft Client. In the ODBC, Client Configuration (Edit Network Library Configurations) I choose Named Pipes.
Server Alias, Server Name, & Pipe Name populated automatically.

For some reason Microsoft did not populate the Pipe Name correctly. I had manually enter the following as the Pipe Name:
[\\>\pipe\mssql$>\sql\query]

Again thanks for your post.

For some reason the MachineName and InstanceName were not published in this reply.

]]> By: Ron http://linwinsysadmin.com/blog/Window/under-current-configuration-sql-server-studio-express-doesnot-support-remote-connection.html#comment-4 Ron Tue, 24 Jul 2007 19:06:26 +0000 http://blog.linwinsysadmin.com/?p=6#comment-4 Thank you for this post. This also worked for me in the Microsoft Client. In the ODBC, Client Configuration (Edit Network Library Configurations) I choose Named Pipes. Server Alias, Server Name, & Pipe Name populated automatically. For some reason Microsoft did not populate the Pipe Name correctly. I had manually enter the following as the Pipe Name: [\\\pipe\mssql$\sql\query] Again thanks for your post. Thank you for this post. This also worked for me in the Microsoft Client. In the ODBC, Client Configuration (Edit Network Library Configurations) I choose Named Pipes.
Server Alias, Server Name, & Pipe Name populated automatically.

For some reason Microsoft did not populate the Pipe Name correctly. I had manually enter the following as the Pipe Name:
[\\\pipe\mssql$\sql\query]

Again thanks for your post.

]]>