Connecting to an SQL Named Pipe Alias

Hi All , I have been racking my head on this for the last two days and really it should be a no brainier. Anyways I can only assume that I’m missing something here but...

In a nut shell I am attempting to connect to a new SQL Alias that i have created by simply adding the following in the client network utility

Current SQL server name DASQL

Default instance

Alias Name: TASQL

Server Name: DASQL

Pipe Name: \\DASQL\pipe\sql\query

I can connect the new alias via the local (server consol) yet when i attempt to connect remotely it times out as if it can't find the server.

Any Thought?

Thanks

I knowat server console Shared Memory protocol is used. There is NamedPipes protocol enabled for client and server too ?|||

You need to create the alias on the client that you are using to connect to the server. It looks like you may have created this alias on the server itself - which means when using a client on the server to connect, the alias is available. You would need to create this on other clients to use the alias.

-Sue

|||

Thanks for the quick reply,

Hmm. so if I understand you correctly the following steps are needed to created an alias that is accessable by remote clients

1 create an alias on the server that is going to host the connection point.(Named Pipes)

within the alias properties:

Example Case (Server Name DASQL)

Alias Name: TASQL

Server Name: DASQL

Pipe Name: \\DASQL\pipe\sql\query -- which points the currently alais name of DASQL as TASQL

2 create another alias on ANYclient that going to connect to the remote alias( this what Im fuzzy on, how would you create a alias on a client that doesnt have to ablity to support alias) ie web or application servers

Example case ( MyComputer DEVLAP)

Alias Name: TASQL

Server Name: DASQL

Pipe Name: \\DASQL\pipe\sql\query

Is this correct?

Thanks

|||

If you have SQL Server listening on named pipes, just setup the alias on the clients.

-Sue

Connecting to an alias fails

Created a new alias with the SQL Server client network utility. With
the connection parameters, changed the server name to the IP address -
still no success.
Edited the Sql Server Network utility to use port 1433 to use port 0
(per another google discussion), still no success.
Any other ideas? The goal is to use the alias identically as how we
access the server name. Using the default instance of SQL Server.
Thanks,
-KevinError message? Version of SQL Server? Service packs?
Inquiring minds want to know
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Justin" <kfwolf@.hotmail.com> wrote in message
news:1166725627.977804.61320@.42g2000cwt.googlegroups.com...
> Created a new alias with the SQL Server client network utility. With
> the connection parameters, changed the server name to the IP address -
> still no success.
> Edited the Sql Server Network utility to use port 1433 to use port 0
> (per another google discussion), still no success.
> Any other ideas? The goal is to use the alias identically as how we
> access the server name. Using the default instance of SQL Server.
> Thanks,
> -Kevin
>

Connecting to an alias fails

Created a new alias with the SQL Server client network utility. With
the connection parameters, changed the server name to the IP address -
still no success.
Edited the Sql Server Network utility to use port 1433 to use port 0
(per another google discussion), still no success.
Any other ideas? The goal is to use the alias identically as how we
access the server name. Using the default instance of SQL Server.
Thanks,
-Kevin
Error message? Version of SQL Server? Service packs?
Inquiring minds want to know
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Justin" <kfwolf@.hotmail.com> wrote in message
news:1166725627.977804.61320@.42g2000cwt.googlegrou ps.com...
> Created a new alias with the SQL Server client network utility. With
> the connection parameters, changed the server name to the IP address -
> still no success.
> Edited the Sql Server Network utility to use port 1433 to use port 0
> (per another google discussion), still no success.
> Any other ideas? The goal is to use the alias identically as how we
> access the server name. Using the default instance of SQL Server.
> Thanks,
> -Kevin
>

Connectectivity problem after Alias is created

I have an SQL 2000 DB that was upgraded from SQL7. I can connect to and work
with the 7 DB with out any problems. After I upgrade the DB to 2000 sp3 I
can connect to it through enterprise manger only on a workstation that does
not have an alias created to the SQL2000 server. The application we are
using against this DB requires an Alias to connect to the data. I have tried
using the server name -which works fine to connect to the SQL7 DB, I have
tried using IP address, & I have tried using the fully qualified domain name,
when creating the Alias. after the alias is created we can not connect to
the DB.
Civic wrote:
> I have an SQL 2000 DB that was upgraded from SQL7. I can connect to
> and work with the 7 DB with out any problems. After I upgrade the DB
> to 2000 sp3 I can connect to it through enterprise manger only on a
> workstation that does not have an alias created to the SQL2000
> server. The application we are using against this DB requires an
> Alias to connect to the data. I have tried using the server name
> -which works fine to connect to the SQL7 DB, I have tried using IP
> address, & I have tried using the fully qualified domain name, when
> creating the Alias. after the alias is created we can not connect to
> the DB.
Are you saying that you are creating an alias on the client using the
SQL Server 2000 Client Network Utility. You give the alias a name that
differs from the server name and are presumably using TCP/IP as the
protocol. When you try and connect to the 2000 server using the server
name, it works. However, when you connect to the server using the alias
name, you can not connect. If so, can you post your alias information as
you set it up.
Can you connect to SQL Server from Query nalyzer using the alias and
server name both?
David Gugick
Imceda Software
www.imceda.com
|||I created the Alias using SQL Server 2000 Client Network Utility I created
the Alias with the same name as our SQL server using TCPIP and the server
name ( I have also since then tried using the FQDN, and IP address for Server
Name) The initial alias cfg'd with server name works fine with the pre
upgrade SQL7 DB. After the Alias is created I can not connect to the SQL
database at all. Using query analyzer I can not connect to the lowercase
server name -populated by the Alias, or by browsing out to the server. I
lose all connectivity to the SQL server. After I remove the Alias I can once
again connect to the server.
"David Gugick" wrote:

> Civic wrote:
> Are you saying that you are creating an alias on the client using the
> SQL Server 2000 Client Network Utility. You give the alias a name that
> differs from the server name and are presumably using TCP/IP as the
> protocol. When you try and connect to the 2000 server using the server
> name, it works. However, when you connect to the server using the alias
> name, you can not connect. If so, can you post your alias information as
> you set it up.
> Can you connect to SQL Server from Query nalyzer using the alias and
> server name both?
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Is your SQL 7 using Named Pipes or TCP/IP (Server Network Utility). I
believe Named Pipes was the default for SQL 7...
"Civic" <Civic@.discussions.microsoft.com> wrote in message
news:6FD4CF01-DB82-4CB2-9FA8-2ECEC5942441@.microsoft.com...[vbcol=seagreen]
>I created the Alias using SQL Server 2000 Client Network Utility I created
> the Alias with the same name as our SQL server using TCPIP and the server
> name ( I have also since then tried using the FQDN, and IP address for
> Server
> Name) The initial alias cfg'd with server name works fine with the pre
> upgrade SQL7 DB. After the Alias is created I can not connect to the SQL
> database at all. Using query analyzer I can not connect to the lowercase
> server name -populated by the Alias, or by browsing out to the server. I
> lose all connectivity to the SQL server. After I remove the Alias I can
> once
> again connect to the server.
> "David Gugick" wrote:
|||Civic wrote:
> I created the Alias using SQL Server 2000 Client Network Utility I
> created the Alias with the same name as our SQL server using TCPIP
> and the server name ( I have also since then tried using the FQDN,
> and IP address for Server Name) The initial alias cfg'd with server
> name works fine with the pre upgrade SQL7 DB. After the Alias is
> created I can not connect to the SQL database at all. Using query
> analyzer I can not connect to the lowercase server name -populated by
> the Alias, or by browsing out to the server. I lose all connectivity
> to the SQL server. After I remove the Alias I can once again connect
> to the server.
>
Why would you create an alias with the same name as the server? An alias
should have a different name... which is the point of an alias.
From BOL:
"In some cases, an instance of SQL Server may be configured to listen on
alternate network addresses. If this is done, client applications
connecting to that instance must explicitly specify the alternate
address. While applications could specify the alternate addresses on
each connection request, it is easier to use the Client Network utility
to set up an alias specifying the alternate addresses. Applications can
then specify the alias name in place of the server network name in their
connection requests."
Which seems to indicate you should be using a unique alias name that
differs from the server name.
David Gugick
Imceda Software
www.imceda.com
|||"David Gugick" wrote:

> Civic wrote:
> Why would you create an alias with the same name as the server? An alias
> should have a different name... which is the point of an alias.
>
> From BOL:
> "In some cases, an instance of SQL Server may be configured to listen on
> alternate network addresses. If this is done, client applications
> connecting to that instance must explicitly specify the alternate
> address. While applications could specify the alternate addresses on
> each connection request, it is easier to use the Client Network utility
> to set up an alias specifying the alternate addresses. Applications can
> then specify the alias name in place of the server network name in their
> connection requests."
> Which seems to indicate you should be using a unique alias name that
> differs from the server name.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>

Connectectivity problem after Alias is created

I have an SQL 2000 DB that was upgraded from SQL7. I can connect to and wor
k
with the 7 DB with out any problems. After I upgrade the DB to 2000 sp3 I
can connect to it through enterprise manger only on a workstation that does
not have an alias created to the SQL2000 server. The application we are
using against this DB requires an Alias to connect to the data. I have trie
d
using the server name -which works fine to connect to the SQL7 DB, I have
tried using IP address, & I have tried using the fully qualified domain name
,
when creating the Alias. after the alias is created we can not connect to
the DB.Civic wrote:
> I have an SQL 2000 DB that was upgraded from SQL7. I can connect to
> and work with the 7 DB with out any problems. After I upgrade the DB
> to 2000 sp3 I can connect to it through enterprise manger only on a
> workstation that does not have an alias created to the SQL2000
> server. The application we are using against this DB requires an
> Alias to connect to the data. I have tried using the server name
> -which works fine to connect to the SQL7 DB, I have tried using IP
> address, & I have tried using the fully qualified domain name, when
> creating the Alias. after the alias is created we can not connect to
> the DB.
Are you saying that you are creating an alias on the client using the
SQL Server 2000 Client Network Utility. You give the alias a name that
differs from the server name and are presumably using TCP/IP as the
protocol. When you try and connect to the 2000 server using the server
name, it works. However, when you connect to the server using the alias
name, you can not connect. If so, can you post your alias information as
you set it up.
Can you connect to SQL Server from Query nalyzer using the alias and
server name both?
David Gugick
Imceda Software
www.imceda.com|||I created the Alias using SQL Server 2000 Client Network Utility I created
the Alias with the same name as our SQL server using TCPIP and the server
name ( I have also since then tried using the FQDN, and IP address for Serve
r
Name) The initial alias cfg'd with server name works fine with the pre
upgrade SQL7 DB. After the Alias is created I can not connect to the SQL
database at all. Using query analyzer I can not connect to the lowercase
server name -populated by the Alias, or by browsing out to the server. I
lose all connectivity to the SQL server. After I remove the Alias I can onc
e
again connect to the server.
"David Gugick" wrote:

> Civic wrote:
> Are you saying that you are creating an alias on the client using the
> SQL Server 2000 Client Network Utility. You give the alias a name that
> differs from the server name and are presumably using TCP/IP as the
> protocol. When you try and connect to the 2000 server using the server
> name, it works. However, when you connect to the server using the alias
> name, you can not connect. If so, can you post your alias information as
> you set it up.
> Can you connect to SQL Server from Query nalyzer using the alias and
> server name both?
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Is your SQL 7 using Named Pipes or TCP/IP (Server Network Utility). I
believe Named Pipes was the default for SQL 7...
"Civic" <Civic@.discussions.microsoft.com> wrote in message
news:6FD4CF01-DB82-4CB2-9FA8-2ECEC5942441@.microsoft.com...[vbcol=seagreen]
>I created the Alias using SQL Server 2000 Client Network Utility I created
> the Alias with the same name as our SQL server using TCPIP and the server
> name ( I have also since then tried using the FQDN, and IP address for
> Server
> Name) The initial alias cfg'd with server name works fine with the pre
> upgrade SQL7 DB. After the Alias is created I can not connect to the SQL
> database at all. Using query analyzer I can not connect to the lowercase
> server name -populated by the Alias, or by browsing out to the server. I
> lose all connectivity to the SQL server. After I remove the Alias I can
> once
> again connect to the server.
> "David Gugick" wrote:
>|||Civic wrote:
> I created the Alias using SQL Server 2000 Client Network Utility I
> created the Alias with the same name as our SQL server using TCPIP
> and the server name ( I have also since then tried using the FQDN,
> and IP address for Server Name) The initial alias cfg'd with server
> name works fine with the pre upgrade SQL7 DB. After the Alias is
> created I can not connect to the SQL database at all. Using query
> analyzer I can not connect to the lowercase server name -populated by
> the Alias, or by browsing out to the server. I lose all connectivity
> to the SQL server. After I remove the Alias I can once again connect
> to the server.
>
Why would you create an alias with the same name as the server? An alias
should have a different name... which is the point of an alias.
From BOL:
"In some cases, an instance of SQL Server may be configured to listen on
alternate network addresses. If this is done, client applications
connecting to that instance must explicitly specify the alternate
address. While applications could specify the alternate addresses on
each connection request, it is easier to use the Client Network utility
to set up an alias specifying the alternate addresses. Applications can
then specify the alias name in place of the server network name in their
connection requests."
Which seems to indicate you should be using a unique alias name that
differs from the server name.
David Gugick
Imceda Software
www.imceda.com|||"David Gugick" wrote:

> Civic wrote:
> Why would you create an alias with the same name as the server? An alias
> should have a different name... which is the point of an alias.
>
> From BOL:
> "In some cases, an instance of SQL Server may be configured to listen on
> alternate network addresses. If this is done, client applications
> connecting to that instance must explicitly specify the alternate
> address. While applications could specify the alternate addresses on
> each connection request, it is easier to use the Client Network utility
> to set up an alias specifying the alternate addresses. Applications can
> then specify the alias name in place of the server network name in their
> connection requests."
> Which seems to indicate you should be using a unique alias name that
> differs from the server name.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>

Connectectivity problem after Alias is created

I have an SQL 2000 DB that was upgraded from SQL7. I can connect to and work
with the 7 DB with out any problems. After I upgrade the DB to 2000 sp3 I
can connect to it through enterprise manger only on a workstation that does
not have an alias created to the SQL2000 server. The application we are
using against this DB requires an Alias to connect to the data. I have tried
using the server name -which works fine to connect to the SQL7 DB, I have
tried using IP address, & I have tried using the fully qualified domain name,
when creating the Alias. after the alias is created we can not connect to
the DB.Civic wrote:
> I have an SQL 2000 DB that was upgraded from SQL7. I can connect to
> and work with the 7 DB with out any problems. After I upgrade the DB
> to 2000 sp3 I can connect to it through enterprise manger only on a
> workstation that does not have an alias created to the SQL2000
> server. The application we are using against this DB requires an
> Alias to connect to the data. I have tried using the server name
> -which works fine to connect to the SQL7 DB, I have tried using IP
> address, & I have tried using the fully qualified domain name, when
> creating the Alias. after the alias is created we can not connect to
> the DB.
Are you saying that you are creating an alias on the client using the
SQL Server 2000 Client Network Utility. You give the alias a name that
differs from the server name and are presumably using TCP/IP as the
protocol. When you try and connect to the 2000 server using the server
name, it works. However, when you connect to the server using the alias
name, you can not connect. If so, can you post your alias information as
you set it up.
Can you connect to SQL Server from Query nalyzer using the alias and
server name both?
David Gugick
Imceda Software
www.imceda.com|||I created the Alias using SQL Server 2000 Client Network Utility I created
the Alias with the same name as our SQL server using TCPIP and the server
name ( I have also since then tried using the FQDN, and IP address for Server
Name) The initial alias cfg'd with server name works fine with the pre
upgrade SQL7 DB. After the Alias is created I can not connect to the SQL
database at all. Using query analyzer I can not connect to the lowercase
server name -populated by the Alias, or by browsing out to the server. I
lose all connectivity to the SQL server. After I remove the Alias I can once
again connect to the server.
"David Gugick" wrote:
> Civic wrote:
> > I have an SQL 2000 DB that was upgraded from SQL7. I can connect to
> > and work with the 7 DB with out any problems. After I upgrade the DB
> > to 2000 sp3 I can connect to it through enterprise manger only on a
> > workstation that does not have an alias created to the SQL2000
> > server. The application we are using against this DB requires an
> > Alias to connect to the data. I have tried using the server name
> > -which works fine to connect to the SQL7 DB, I have tried using IP
> > address, & I have tried using the fully qualified domain name, when
> > creating the Alias. after the alias is created we can not connect to
> > the DB.
> Are you saying that you are creating an alias on the client using the
> SQL Server 2000 Client Network Utility. You give the alias a name that
> differs from the server name and are presumably using TCP/IP as the
> protocol. When you try and connect to the 2000 server using the server
> name, it works. However, when you connect to the server using the alias
> name, you can not connect. If so, can you post your alias information as
> you set it up.
> Can you connect to SQL Server from Query nalyzer using the alias and
> server name both?
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Is your SQL 7 using Named Pipes or TCP/IP (Server Network Utility). I
believe Named Pipes was the default for SQL 7...
"Civic" <Civic@.discussions.microsoft.com> wrote in message
news:6FD4CF01-DB82-4CB2-9FA8-2ECEC5942441@.microsoft.com...
>I created the Alias using SQL Server 2000 Client Network Utility I created
> the Alias with the same name as our SQL server using TCPIP and the server
> name ( I have also since then tried using the FQDN, and IP address for
> Server
> Name) The initial alias cfg'd with server name works fine with the pre
> upgrade SQL7 DB. After the Alias is created I can not connect to the SQL
> database at all. Using query analyzer I can not connect to the lowercase
> server name -populated by the Alias, or by browsing out to the server. I
> lose all connectivity to the SQL server. After I remove the Alias I can
> once
> again connect to the server.
> "David Gugick" wrote:
>> Civic wrote:
>> > I have an SQL 2000 DB that was upgraded from SQL7. I can connect to
>> > and work with the 7 DB with out any problems. After I upgrade the DB
>> > to 2000 sp3 I can connect to it through enterprise manger only on a
>> > workstation that does not have an alias created to the SQL2000
>> > server. The application we are using against this DB requires an
>> > Alias to connect to the data. I have tried using the server name
>> > -which works fine to connect to the SQL7 DB, I have tried using IP
>> > address, & I have tried using the fully qualified domain name, when
>> > creating the Alias. after the alias is created we can not connect to
>> > the DB.
>> Are you saying that you are creating an alias on the client using the
>> SQL Server 2000 Client Network Utility. You give the alias a name that
>> differs from the server name and are presumably using TCP/IP as the
>> protocol. When you try and connect to the 2000 server using the server
>> name, it works. However, when you connect to the server using the alias
>> name, you can not connect. If so, can you post your alias information as
>> you set it up.
>> Can you connect to SQL Server from Query nalyzer using the alias and
>> server name both?
>>
>> --
>> David Gugick
>> Imceda Software
>> www.imceda.com
>>|||Civic wrote:
> I created the Alias using SQL Server 2000 Client Network Utility I
> created the Alias with the same name as our SQL server using TCPIP
> and the server name ( I have also since then tried using the FQDN,
> and IP address for Server Name) The initial alias cfg'd with server
> name works fine with the pre upgrade SQL7 DB. After the Alias is
> created I can not connect to the SQL database at all. Using query
> analyzer I can not connect to the lowercase server name -populated by
> the Alias, or by browsing out to the server. I lose all connectivity
> to the SQL server. After I remove the Alias I can once again connect
> to the server.
>
Why would you create an alias with the same name as the server? An alias
should have a different name... which is the point of an alias.
From BOL:
"In some cases, an instance of SQL Server may be configured to listen on
alternate network addresses. If this is done, client applications
connecting to that instance must explicitly specify the alternate
address. While applications could specify the alternate addresses on
each connection request, it is easier to use the Client Network utility
to set up an alias specifying the alternate addresses. Applications can
then specify the alias name in place of the server network name in their
connection requests."
Which seems to indicate you should be using a unique alias name that
differs from the server name.
David Gugick
Imceda Software
www.imceda.com|||"David Gugick" wrote:
> Civic wrote:
> > I created the Alias using SQL Server 2000 Client Network Utility I
> > created the Alias with the same name as our SQL server using TCPIP
> > and the server name ( I have also since then tried using the FQDN,
> > and IP address for Server Name) The initial alias cfg'd with server
> > name works fine with the pre upgrade SQL7 DB. After the Alias is
> > created I can not connect to the SQL database at all. Using query
> > analyzer I can not connect to the lowercase server name -populated by
> > the Alias, or by browsing out to the server. I lose all connectivity
> > to the SQL server. After I remove the Alias I can once again connect
> > to the server.
> >
> Why would you create an alias with the same name as the server? An alias
> should have a different name... which is the point of an alias.
>
> From BOL:
> "In some cases, an instance of SQL Server may be configured to listen on
> alternate network addresses. If this is done, client applications
> connecting to that instance must explicitly specify the alternate
> address. While applications could specify the alternate addresses on
> each connection request, it is easier to use the Client Network utility
> to set up an alias specifying the alternate addresses. Applications can
> then specify the alias name in place of the server network name in their
> connection requests."
> Which seems to indicate you should be using a unique alias name that
> differs from the server name.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>