All geek questions in one place

Unable to connect to SQL Server using an alias

I have SQL Server 2000 installed on a server that is having connection problems.

Using SSMS, I can’t connect to it using Alias, which I have installed in Configuration Manager. The alias is configured to use TCPIP, which is the first protocol in the order below shared memory. If I use the same server name that I put in Alias, then I can connect normally.

I see the same behavior in my ASP.NET application using an alias that I get a connection failure using the name it connects is just fine. The ASP.NET connection string does not specify a protocol.

+3
source share
2 answers

Using the server name will use the default connection protocol for the client. This can be called pipe or tcp / ip (MDAC version, update vs install, etc.).

The alias is configured to use TCPIP, which first protocol in the following order is shared memory

I assume that if the client alias is configured to use tcp, then the server is only configured to listen on named pipes, so it only works with the server name. Ultimately, the client will find named pipes in the list of protocols used.

To check, replace the server name with np: servername and tcp: servername to change the protocol without using an alias.

Or check that the server is listening and fixing it ...

- TCP- (, 1433) , 1433/1434.

SQL 2000

+1

? ? ? ( )

0

Source: https://habr.com/ru/post/1699470/

More articles:


All Articles