How to use alises to connect to an instance SQL Server Express

Hi
I can create an TCP/IP alias for a server on the domain using the servername
and it works fine, if the IP address in the alias works I would guess that it
is somehow a name resolution issue.
John
"SteveM" wrote:

> Actually,
> I dont have to use alias, your correct, the servername,port works just
> fine. It just would make things simpler to use an alias, and I have
> done this with W2K, and thought it should work with 2005, but perhaps
> I was wrong.
> I have tried an IP address, and we dont use .hosts files.
> Thanks for your response
> -Steve
> On Feb 3, 1:46 pm, "John Bell" <jbellnewspo...@.hotmail.com> wrote:
>
Thats probably a good guess, but it would seem to me that I have
eliminated that possibility by hardcoding the ip address of the server
in the alias description
Alias Name: stptest
Server: 149.59.22.48\STPTEST
Protocol: TCP\IP
Port: 1439
SQLCMD: sqlcmd -S stptest -E -d metrics
HResult 0x2AF9, Level 16, State 1
TCP Provider: No such host is known.
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred
while establishing a connection to
the server. When connecting to SQL Server 2005, this failure may be
caused by the fact that under th
e default settings SQL Server does not allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
But this works:
sqlcmd -S titan\STPTEST,1439 -E -d metrics
So I suspect that it may not be a name resolution issue
Thanks for your response
-SteveM
On Feb 4, 12:27Xam, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> I can create an TCP/IP alias for a server on the domain using the servername
> and it works fine, if the IP address in the alias works I would guess thatit
> is somehow a name resolution issue.
> John
>
> "SteveM" wrote:
>
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -
|||Hi
I don't have any issues with using either the IP address or the machine
names for the server in the aliases. If the browser service is running I
don't need the port. This is on release 3159.
I would verify that you can connect using these without the VPN.
John
"SteveM" wrote:

> Thats probably a good guess, but it would seem to me that I have
> eliminated that possibility by hardcoding the ip address of the server
> in the alias description
> Alias Name: stptest
> Server: 149.59.22.48\STPTEST
> Protocol: TCP\IP
> Port: 1439
> SQLCMD: sqlcmd -S stptest -E -d metrics
> HResult 0x2AF9, Level 16, State 1
> TCP Provider: No such host is known.
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred
> while establishing a connection to
> the server. When connecting to SQL Server 2005, this failure may be
> caused by the fact that under th
> e default settings SQL Server does not allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> But this works:
> sqlcmd -S titan\STPTEST,1439 -E -d metrics
> So I suspect that it may not be a name resolution issue
> Thanks for your response
> -SteveM
> On Feb 4, 12:27 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
|||Aliases do not work even inside our firewall and not using VPN. I have
tried the servername/named_instance,port
and the ip address in place of the servername. I had the browser
service running but turned it off, it made no difference, also you are
aware that the browser service uses UDP 1434 by default aren't you?
This is the nature of the problem, as I said I can connect around
using the alias, but since all the Microsoft documentation indicates
this should work, something else is missing. I am simply trying to
figure out what. I am currently using SQL Server SP2 9.00.1399.00.
Thanks for trying to help, but the answer still eludes me
-SteveM
On Feb 4, 10:09Xam, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> I don't have any issues with using either the IP address or the machine
> names for the server in the aliases. If the browser service is running I
> don't need the port. This is on release 3159.
> I would verify that you can connect using these without the VPN.
> John
>
> "SteveM" wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -
|||Hi Steve
Your version is RTM and not SP2.
You don't need the port if the browser service is running and the browser
service port is open. But if you specify the port that should not make any
difference so long as the port specified is the correct one. As you can
connect from the command line with the port it should be correct, therefore
I can't see any reason why it should not work apart from the version.
Alaises do work.
John
"SteveM" <steve.moody@.philips.com> wrote in message
news:ae619598-f894-4c9c-b9c2-6ba9855c615a@.q39g2000hsf.googlegroups.com...
Aliases do not work even inside our firewall and not using VPN. I have
tried the servername/named_instance,port
and the ip address in place of the servername. I had the browser
service running but turned it off, it made no difference, also you are
aware that the browser service uses UDP 1434 by default aren't you?
This is the nature of the problem, as I said I can connect around
using the alias, but since all the Microsoft documentation indicates
this should work, something else is missing. I am simply trying to
figure out what. I am currently using SQL Server SP2 9.00.1399.00.
Thanks for trying to help, but the answer still eludes me
-SteveM
On Feb 4, 10:09 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> I don't have any issues with using either the IP address or the machine
> names for the server in the aliases. If the browser service is running I
> don't need the port. This is on release 3159.
> I would verify that you can connect using these without the VPN.
> John
>
> "SteveM" wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -
|||Actually the information I gave you was incorrect but on my client I
am running SP2 of SQL Server Express. I know this because I needed to
work with Microsoft to resolve an issue and the solution was to
download SQL Express 2005 SP2. I also want to state I am not saying
aliases do not work, and I find that they seem to work for the default
instance on the remote server, but then its not using static port its
using dynamic and is probably listening on port 1433. The SQL Server
Browser is running on my machine, but when I try to use the alias (in
all the different configurations you suggested) for the named instance
on the remote server that has static port 1439 it fails with an error
indicating it can not connect.
The fact remains that for whatever reason this implementation of
ailases does not work for me. I was hoping to get a clue from someone
as to why this might be, but research, and posting to two different
sources has produced no clues. I am willing to accept that for
whatever reason this mechanism is just not going to work in my case.
That being said I want you to know I appreciate all your suggestions
and help. I appreciate your taking the time to consider my plight and
that you would take the time to write. Thank you very much for your
attempts at trying to resolve my issue.
-SteveM
On Feb 4, 12:45Xpm, "John Bell" <jbellnewspo...@.hotmail.com> wrote:
> Hi Steve
> Your version is RTM and not SP2.
> You don't need the port if the browser service is running and the browser
> service port is open. But if you specify the port that should not make any
> difference so long as the port specified is the correct one. As you can
> connect from the command line with the port it should be correct, therefore
> I can't see any reason why it should not work apart from the version.
> Alaises do work.
> John"SteveM" <steve.mo...@.philips.com> wrote in message
> news:ae619598-f894-4c9c-b9c2-6ba9855c615a@.q39g2000hsf.googlegroups.com...
> Aliases do not work even inside our firewall and not using VPN. I have
> tried the servername/named_instance,port
> and the ip address in place of the servername. I had the browser
> service running but turned it off, it made no difference, also you are
> aware that the browser service uses UDP 1434 by default aren't you?
> This is the nature of the problem, as I said I can connect around
> using the alias, but since all the Microsoft documentation indicates
> this should work, something else is missing. I am simply trying to
> figure out what. I am currently using SQL Server SP2 9.00.1399.00.
> Thanks for trying to help, but the answer still eludes me
> -SteveM
> On Feb 4, 10:09 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -