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

The question is simple, the solution I suspect is not, but here it
goes.
I have a named instance (not the default) of SQL Server 2005 running
on a server at my company. While at work (behind the firewall) I am
able to connect to th is SQL Server instance with no problems
whatsoever. I can do this through the SQL Server Management Studio
Express, I can do it through a sqlcmd on a command line, and i can do
it through connection stings within programs. The issue comes up when
I try to do it from a remote login from home. Now understand this, I
have already authenticated past the firewall, and can ping the
physical machine, and even login in to the server. I have worked with
our network people and know that the reason I was being blocked was
because of the old UDP 1434 issue with regards to SQL Server. I was
instructed to set a static address instead of using dynamic
addressing, which I did. I then was able to connect to the remote
server by all of the methods described above by using the servername,
port (for example say my port is 2505, set at the server, now I can
connect to it by using thisServer,2505 ). So now I remember using
aliases with W2K and read that you can do the same thing with 2005. So
I open the SQL Server Configuration Manager, and I set an alias to
that machine to that port over TCP\IP. Everything I read says that now
I should be able to connect up using just the alias. So in SQL Server
Management Studio Express I should know be able to just connect using
the alias... it fails. I should be able to connect using the alias
using sqlcmd... this also fails. This is all very frustrating. I have
the server configured for remote connections, can connect to it
remotely using the servername, port but can not get aliases to work to
save me. What am I doing wrong?
Has anyone got this to work over TCP\IP (we are not able to use the
other protocols where i work just TCP\IP). I could use some expertise
here and some help.
Thanks to one and all
-SteveMHi
Have you tried the SQLCMD connection
sqlcmd -S tcp:<computer name>,<port number>
I can create an alias
Name: test
Port: 1433
Protocol: TCP/IP
Server: Localhost
and connect to it.
John
"SteveM"
<steve.moody@.philips.com> wrote in message
news:ccc3a173-8e6a-4a70-b622-fe08e1162347@.q21g2000hsa.googlegroups.com...
> The question is simple, the solution I suspect is not, but here it
> goes.
> I have a named instance (not the default) of SQL Server 2005 running
> on a server at my company. While at work (behind the firewall) I am
> able to connect to th is SQL Server instance with no problems
> whatsoever. I can do this through the SQL Server Management Studio
> Express, I can do it through a sqlcmd on a command line, and i can do
> it through connection stings within programs. The issue comes up when
> I try to do it from a remote login from home. Now understand this, I
> have already authenticated past the firewall, and can ping the
> physical machine, and even login in to the server. I have worked with
> our network people and know that the reason I was being blocked was
> because of the old UDP 1434 issue with regards to SQL Server. I was
> instructed to set a static address instead of using dynamic
> addressing, which I did. I then was able to connect to the remote
> server by all of the methods described above by using the servername,
> port (for example say my port is 2505, set at the server, now I can
> connect to it by using thisServer,2505 ). So now I remember using
> aliases with W2K and read that you can do the same thing with 2005. So
> I open the SQL Server Configuration Manager, and I set an alias to
> that machine to that port over TCP\IP. Everything I read says that now
> I should be able to connect up using just the alias. So in SQL Server
> Management Studio Express I should know be able to just connect using
> the alias... it fails. I should be able to connect using the alias
> using sqlcmd... this also fails. This is all very frustrating. I have
> the server configured for remote connections, can connect to it
> remotely using the servername, port but can not get aliases to work to
> save me. What am I doing wrong?
> Has anyone got this to work over TCP\IP (we are not able to use the
> other protocols where i work just TCP\IP). I could use some expertise
> here and some help.
> Thanks to one and all
> -SteveM|||On Feb 3, 11:25=A0am, "John Bell" <jbellnewspo...@.hotmail.com> wrote:
> Hi
> Have you tried the SQLCMD connection
> sqlcmd -S tcp:<computer name>,<port number>
> I can create an alias
> Name: test
> Port: 1433
> Protocol: TCP/IP
> Server: Localhost
> and connect to it.
> John
> "SteveM"<steve.mo...@.philips.com> wrote in message
> news:ccc3a173-8e6a-4a70-b622-fe08e1162347@.q21g2000hsa.googlegroups.com...
>
> > The question is simple, the solution I suspect is not, but here it
> > goes.
> > I have a named instance (not the default) of SQL Server 2005 running
> > on a server at my company. While at work (behind the firewall) I am
> > able to connect to th is SQL Server instance with no problems
> > whatsoever. I can do this through the SQL Server Management Studio
> > Express, I can do it through a sqlcmd on a command line, and i can do
> > it through connection stings within programs. The issue comes up when
> > I try to do it from a remote login from home. Now understand this, I
> > have already authenticated past the firewall, and can ping the
> > physical machine, and even login in to the server. I have worked with
> > our network people and know that the reason I was being blocked was
> > because of the old UDP 1434 issue with regards to SQL Server. I was
> > instructed to set a static address instead of using dynamic
> > addressing, which I did. I then was able to connect to the remote
> > server by all of the methods described above by using the servername,
> > port (for example say my port is 2505, set at the server, now I can
> > connect to it by using thisServer,2505 ). So now I remember using
> > aliases with W2K and read that you can do the same thing with 2005. So
> > I open the SQL Server Configuration Manager, and I set an alias to
> > that machine to that port over TCP\IP. Everything I read says that now
> > I should be able to connect up using just the alias. So in SQL Server
> > Management Studio Express I should know be able to just connect using
> > the alias... it fails. I should be able to connect using the alias
> > using sqlcmd... this also fails. This is all very frustrating. I have
> > the server configured for remote connections, can connect to it
> > remotely using the servername, port but can not get aliases to work to
> > save me. What am I doing wrong?
> > Has anyone got this to work over TCP\IP (we are not able to use the
> > other protocols where i work just TCP\IP). I could use some expertise
> > here and some help.
> > Thanks to one and all
> > -SteveM- Hide quoted text -
> - Show quoted text -
As I stated, the sqlcmd and the connection using the SQL Server
Management Studio both work with the server\named_instance,port
I do not seem to be able to get the alias to work in any situation
though
I have an alias called stptest, I should be able to do SQLCMD -S
stptest -E -d mydatabase
but that doesnt work and the error isnt all that helpful (it reminds
the default for SQL Server Express is local connections only - BTW I
have set that for local and remote and tested it inside the firewall)
So the question still remains, why isnt the alias working for me
Thanks for your response
-SteveM|||Hi
It is still not clear why you HAVE to use the alias if you can connect
without it?
Have you tried with an IP address in the Alias or changing the hosts file?
John
"SteveM" <steve.moody@.philips.com> wrote in message
news:905199b3-be8a-47a4-9394-9fb4c2ea3891@.y5g2000hsf.googlegroups.com...
On Feb 3, 11:25 am, "John Bell" <jbellnewspo...@.hotmail.com> wrote:
> Hi
> Have you tried the SQLCMD connection
> sqlcmd -S tcp:<computer name>,<port number>
> I can create an alias
> Name: test
> Port: 1433
> Protocol: TCP/IP
> Server: Localhost
> and connect to it.
> John
> "SteveM"<steve.mo...@.philips.com> wrote in message
> news:ccc3a173-8e6a-4a70-b622-fe08e1162347@.q21g2000hsa.googlegroups.com...
>
> > The question is simple, the solution I suspect is not, but here it
> > goes.
> > I have a named instance (not the default) of SQL Server 2005 running
> > on a server at my company. While at work (behind the firewall) I am
> > able to connect to th is SQL Server instance with no problems
> > whatsoever. I can do this through the SQL Server Management Studio
> > Express, I can do it through a sqlcmd on a command line, and i can do
> > it through connection stings within programs. The issue comes up when
> > I try to do it from a remote login from home. Now understand this, I
> > have already authenticated past the firewall, and can ping the
> > physical machine, and even login in to the server. I have worked with
> > our network people and know that the reason I was being blocked was
> > because of the old UDP 1434 issue with regards to SQL Server. I was
> > instructed to set a static address instead of using dynamic
> > addressing, which I did. I then was able to connect to the remote
> > server by all of the methods described above by using the servername,
> > port (for example say my port is 2505, set at the server, now I can
> > connect to it by using thisServer,2505 ). So now I remember using
> > aliases with W2K and read that you can do the same thing with 2005. So
> > I open the SQL Server Configuration Manager, and I set an alias to
> > that machine to that port over TCP\IP. Everything I read says that now
> > I should be able to connect up using just the alias. So in SQL Server
> > Management Studio Express I should know be able to just connect using
> > the alias... it fails. I should be able to connect using the alias
> > using sqlcmd... this also fails. This is all very frustrating. I have
> > the server configured for remote connections, can connect to it
> > remotely using the servername, port but can not get aliases to work to
> > save me. What am I doing wrong?
> > Has anyone got this to work over TCP\IP (we are not able to use the
> > other protocols where i work just TCP\IP). I could use some expertise
> > here and some help.
> > Thanks to one and all
> > -SteveM- Hide quoted text -
> - Show quoted text -
As I stated, the sqlcmd and the connection using the SQL Server
Management Studio both work with the server\named_instance,port
I do not seem to be able to get the alias to work in any situation
though
I have an alias called stptest, I should be able to do SQLCMD -S
stptest -E -d mydatabase
but that doesnt work and the error isnt all that helpful (it reminds
the default for SQL Server Express is local connections only - BTW I
have set that for local and remote and tested it inside the firewall)
So the question still remains, why isnt the alias working for me
Thanks for your response
-SteveM|||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=A0pm, "John Bell" <jbellnewspo...@.hotmail.com> wrote:
> Hi
> It is still not clear why you HAVE to use the alias if you can connect
> without it?
> Have you tried with an IP address in the Alias or changing the hosts file?=
> John
> "SteveM" <steve.mo...@.philips.com> wrote in message
> news:905199b3-be8a-47a4-9394-9fb4c2ea3891@.y5g2000hsf.googlegroups.com...
> On Feb 3, 11:25 am, "John Bell" <jbellnewspo...@.hotmail.com> wrote:
>
>
> > Hi
> > Have you tried the SQLCMD connection
> > sqlcmd -S tcp:<computer name>,<port number>
> > I can create an alias
> > Name: test
> > Port: 1433
> > Protocol: TCP/IP
> > Server: Localhost
> > and connect to it.
> > John
> > "SteveM"<steve.mo...@.philips.com> wrote in message
> >news:ccc3a173-8e6a-4a70-b622-fe08e1162347@.q21g2000hsa.googlegroups.com...=
> > > The question is simple, the solution I suspect is not, but here it
> > > goes.
> > > I have a named instance (not the default) of SQL Server 2005 running
> > > on a server at my company. While at work (behind the firewall) I am
> > > able to connect to th is SQL Server instance with no problems
> > > whatsoever. I can do this through the SQL Server Management Studio
> > > Express, I can do it through a sqlcmd on a command line, and i can do
> > > it through connection stings within programs. The issue comes up when
> > > I try to do it from a remote login from home. Now understand this, I
> > > have already authenticated past the firewall, and can ping the
> > > physical machine, and even login in to the server. I have worked with
> > > our network people and know that the reason I was being blocked was
> > > because of the old UDP 1434 issue with regards to SQL Server. I was
> > > instructed to set a static address instead of using dynamic
> > > addressing, which I did. I then was able to connect to the remote
> > > server by all of the methods described above by using the servername,
> > > port (for example say my port is 2505, set at the server, now I can
> > > connect to it by using thisServer,2505 ). So now I remember using
> > > aliases with W2K and read that you can do the same thing with 2005. So=
> > > I open the SQL Server Configuration Manager, and I set an alias to
> > > that machine to that port over TCP\IP. Everything I read says that now=
> > > I should be able to connect up using just the alias. So in SQL Server
> > > Management Studio Express I should know be able to just connect using
> > > the alias... it fails. I should be able to connect using the alias
> > > using sqlcmd... this also fails. This is all very frustrating. I have
> > > the server configured for remote connections, can connect to it
> > > remotely using the servername, port but can not get aliases to work to=
> > > save me. What am I doing wrong?
> > > Has anyone got this to work over TCP\IP (we are not able to use the
> > > other protocols where i work just TCP\IP). I could use some expertise
> > > here and some help.
> > > Thanks to one and all
> > > -SteveM- Hide quoted text -
> > - Show quoted text -
> As I stated, the sqlcmd and the connection using the SQL Server
> Management Studio both work with the server\named_instance,port
> I do not seem to be able to get the alias to work in any situation
> though
> I have an alias called stptest, I should be able to do SQLCMD -S
> stptest -E -d mydatabase
> but that doesnt work and the error isnt all that helpful (it reminds
> the default for SQL Server Express is local connections only - BTW I
> have set that for local and remote and tested it inside the firewall)
> So the question still remains, why isnt the alias working for me
> Thanks for your response
> -SteveM- Hide quoted text -
> - Show quoted text -|||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:
> > Hi
> >
> > It is still not clear why you HAVE to use the alias if you can connect
> > without it?
> >
> > Have you tried with an IP address in the Alias or changing the hosts file?
> >
> > John
> >
> > "SteveM" <steve.mo...@.philips.com> wrote in message
> >
> > news:905199b3-be8a-47a4-9394-9fb4c2ea3891@.y5g2000hsf.googlegroups.com...
> > On Feb 3, 11:25 am, "John Bell" <jbellnewspo...@.hotmail.com> wrote:
> >
> >
> >
> >
> >
> > > Hi
> >
> > > Have you tried the SQLCMD connection
> >
> > > sqlcmd -S tcp:<computer name>,<port number>
> >
> > > I can create an alias
> >
> > > Name: test
> > > Port: 1433
> > > Protocol: TCP/IP
> > > Server: Localhost
> >
> > > and connect to it.
> >
> > > John
> > > "SteveM"<steve.mo...@.philips.com> wrote in message
> >
> > >news:ccc3a173-8e6a-4a70-b622-fe08e1162347@.q21g2000hsa.googlegroups.com...
> >
> > > > The question is simple, the solution I suspect is not, but here it
> > > > goes.
> > > > I have a named instance (not the default) of SQL Server 2005 running
> > > > on a server at my company. While at work (behind the firewall) I am
> > > > able to connect to th is SQL Server instance with no problems
> > > > whatsoever. I can do this through the SQL Server Management Studio
> > > > Express, I can do it through a sqlcmd on a command line, and i can do
> > > > it through connection stings within programs. The issue comes up when
> > > > I try to do it from a remote login from home. Now understand this, I
> > > > have already authenticated past the firewall, and can ping the
> > > > physical machine, and even login in to the server. I have worked with
> > > > our network people and know that the reason I was being blocked was
> > > > because of the old UDP 1434 issue with regards to SQL Server. I was
> > > > instructed to set a static address instead of using dynamic
> > > > addressing, which I did. I then was able to connect to the remote
> > > > server by all of the methods described above by using the servername,
> > > > port (for example say my port is 2505, set at the server, now I can
> > > > connect to it by using thisServer,2505 ). So now I remember using
> > > > aliases with W2K and read that you can do the same thing with 2005. So
> > > > I open the SQL Server Configuration Manager, and I set an alias to
> > > > that machine to that port over TCP\IP. Everything I read says that now
> > > > I should be able to connect up using just the alias. So in SQL Server
> > > > Management Studio Express I should know be able to just connect using
> > > > the alias... it fails. I should be able to connect using the alias
> > > > using sqlcmd... this also fails. This is all very frustrating. I have
> > > > the server configured for remote connections, can connect to it
> > > > remotely using the servername, port but can not get aliases to work to
> > > > save me. What am I doing wrong?
> > > > Has anyone got this to work over TCP\IP (we are not able to use the
> > > > other protocols where i work just TCP\IP). I could use some expertise
> > > > here and some help.
> > > > Thanks to one and all
> > > > -SteveM- Hide quoted text -
> >
> > > - Show quoted text -
> >
> > As I stated, the sqlcmd and the connection using the SQL Server
> > Management Studio both work with the server\named_instance,port
> > I do not seem to be able to get the alias to work in any situation
> > though
> > I have an alias called stptest, I should be able to do SQLCMD -S
> > stptest -E -d mydatabase
> > but that doesnt work and the error isnt all that helpful (it reminds
> > the default for SQL Server Express is local connections only - BTW I
> > have set that for local and remote and tested it inside the firewall)
> >
> > So the question still remains, why isnt the alias working for me
> >
> > Thanks for your response
> > -SteveM- Hide quoted text -
> >
> > - Show quoted text -
>|||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=A0am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> I can create an TCP/IP alias for a server on the domain using the serverna=me
> 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:
> > > Hi
> > > It is still not clear why you HAVE to use the alias if you can connect=
> > > without it?
> > > Have you tried with an IP address in the Alias or changing the hosts f=ile?
> > > John
> > > "SteveM" <steve.mo...@.philips.com> wrote in message
> > >news:905199b3-be8a-47a4-9394-9fb4c2ea3891@.y5g2000hsf.googlegroups.com..=.
> > > On Feb 3, 11:25 am, "John Bell" <jbellnewspo...@.hotmail.com> wrote:
> > > > Hi
> > > > Have you tried the SQLCMD connection
> > > > sqlcmd -S tcp:<computer name>,<port number>
> > > > I can create an alias
> > > > Name: test
> > > > Port: 1433
> > > > Protocol: TCP/IP
> > > > Server: Localhost
> > > > and connect to it.
> > > > John
> > > > "SteveM"<steve.mo...@.philips.com> wrote in message
> > > >news:ccc3a173-8e6a-4a70-b622-fe08e1162347@.q21g2000hsa.googlegroups.co=m...
> > > > > The question is simple, the solution I suspect is not, but here it=
> > > > > goes.
> > > > > I have a named instance (not the default) of SQL Server 2005 runni=ng
> > > > > on a server at my company. While at work (behind the firewall) I a=m
> > > > > able to connect to th is SQL Server instance with no problems
> > > > > whatsoever. I can do this through the SQL Server Management Studio=
> > > > > Express, I can do it through a sqlcmd on a command line, and i can= do
> > > > > it through connection stings within programs. The issue comes up w=hen
> > > > > I try to do it from a remote login from home. Now understand this,= I
> > > > > have already authenticated past the firewall, and can ping the
> > > > > physical machine, and even login in to the server. I have worked w=ith
> > > > > our network people and know that the reason I was being blocked wa=s
> > > > > because of the old UDP 1434 issue with regards to SQL Server. I wa=s
> > > > > instructed to set a static address instead of using dynamic
> > > > > addressing, which I did. I then was able to connect to the remote
> > > > > server by all of the methods described above by using the serverna=me,
> > > > > port (for example say my port is 2505, set at the server, now I ca=n
> > > > > connect to it by using thisServer,2505 ). So now I remember using
> > > > > aliases with W2K and read that you can do the same thing with 2005=. So
> > > > > I open the SQL Server Configuration Manager, and I set an alias to=
> > > > > that machine to that port over TCP\IP. Everything I read says that= now
> > > > > I should be able to connect up using just the alias. So in SQL Ser=ver
> > > > > Management Studio Express I should know be able to just connect us=ing
> > > > > the alias... it fails. I should be able to connect using the alias=
> > > > > using sqlcmd... this also fails. This is all very frustrating. I h=ave
> > > > > the server configured for remote connections, can connect to it
> > > > > remotely using the servername, port but can not get aliases to wor=k to
> > > > > save me. What am I doing wrong?
> > > > > Has anyone got this to work over TCP\IP (we are not able to use th=e
> > > > > other protocols where i work just TCP\IP). I could use some expert=ise
> > > > > here and some help.
> > > > > Thanks to one and all
> > > > > -SteveM- Hide quoted text -
> > > > - Show quoted text -
> > > As I stated, the sqlcmd and the connection using the SQL Server
> > > Management Studio both work with the server\named_instance,port
> > > I do not seem to be able to get the alias to work in any situation
> > > though
> > > I have an alias called stptest, I should be able to do SQLCMD -S
> > > stptest -E -d mydatabase
> > > but that doesnt work and the error isnt all that helpful (it reminds
> > > the default for SQL Server Express is local connections only - BTW I
> > > have set that for local and remote and tested it inside the firewall)
> > > So the question still remains, why isnt the alias working for me
> > > Thanks for your response
> > > -SteveM- Hide quoted text -
> > > - Show quoted text -- Hide quoted text -
> - 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:
> > 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:
> > > > Hi
> >
> > > > It is still not clear why you HAVE to use the alias if you can connect
> > > > without it?
> >
> > > > Have you tried with an IP address in the Alias or changing the hosts file?
> >
> > > > John
> >
> > > > "SteveM" <steve.mo...@.philips.com> wrote in message
> >
> > > >news:905199b3-be8a-47a4-9394-9fb4c2ea3891@.y5g2000hsf.googlegroups.com...
> > > > On Feb 3, 11:25 am, "John Bell" <jbellnewspo...@.hotmail.com> wrote:
> >
> > > > > Hi
> >
> > > > > Have you tried the SQLCMD connection
> >
> > > > > sqlcmd -S tcp:<computer name>,<port number>
> >
> > > > > I can create an alias
> >
> > > > > Name: test
> > > > > Port: 1433
> > > > > Protocol: TCP/IP
> > > > > Server: Localhost
> >
> > > > > and connect to it.
> >
> > > > > John
> > > > > "SteveM"<steve.mo...@.philips.com> wrote in message
> >
> > > > >news:ccc3a173-8e6a-4a70-b622-fe08e1162347@.q21g2000hsa.googlegroups.com...
> >
> > > > > > The question is simple, the solution I suspect is not, but here it
> > > > > > goes.
> > > > > > I have a named instance (not the default) of SQL Server 2005 running
> > > > > > on a server at my company. While at work (behind the firewall) I am
> > > > > > able to connect to th is SQL Server instance with no problems
> > > > > > whatsoever. I can do this through the SQL Server Management Studio
> > > > > > Express, I can do it through a sqlcmd on a command line, and i can do
> > > > > > it through connection stings within programs. The issue comes up when
> > > > > > I try to do it from a remote login from home. Now understand this, I
> > > > > > have already authenticated past the firewall, and can ping the
> > > > > > physical machine, and even login in to the server. I have worked with
> > > > > > our network people and know that the reason I was being blocked was
> > > > > > because of the old UDP 1434 issue with regards to SQL Server. I was
> > > > > > instructed to set a static address instead of using dynamic
> > > > > > addressing, which I did. I then was able to connect to the remote
> > > > > > server by all of the methods described above by using the servername,
> > > > > > port (for example say my port is 2505, set at the server, now I can
> > > > > > connect to it by using thisServer,2505 ). So now I remember using
> > > > > > aliases with W2K and read that you can do the same thing with 2005.. So
> > > > > > I open the SQL Server Configuration Manager, and I set an alias to
> > > > > > that machine to that port over TCP\IP. Everything I read says that now
> > > > > > I should be able to connect up using just the alias. So in SQL Server
> > > > > > Management Studio Express I should know be able to just connect using
> > > > > > the alias... it fails. I should be able to connect using the alias
> > > > > > using sqlcmd... this also fails. This is all very frustrating. I have
> > > > > > the server configured for remote connections, can connect to it
> > > > > > remotely using the servername, port but can not get aliases to work to
> > > > > > save me. What am I doing wrong?
> > > > > > Has anyone got this to work over TCP\IP (we are not able to use the
> > > > > > other protocols where i work just TCP\IP). I could use some expertise
> > > > > > here and some help.
> > > > > > Thanks to one and all
> > > > > > -SteveM- Hide quoted text -
> >
> > > > > - Show quoted text -
> >
> > > > As I stated, the sqlcmd and the connection using the SQL Server
> > > > Management Studio both work with the server\named_instance,port
> > > > I do not seem to be able to get the alias to work in any situation
> > > > though
> > > > I have an alias called stptest, I should be able to do SQLCMD -S
> > > > stptest -E -d mydatabase
> > > > but that doesnt work and the error isnt all that helpful (it reminds
> > > > the default for SQL Server Express is local connections only - BTW I
> > > > have set that for local and remote and tested it inside the firewall)
> >
> > > > So the question still remains, why isnt the alias working for me
> >
> > > > Thanks for your response
> > > > -SteveM- Hide quoted text -
> >
> > > > - Show quoted text -- Hide quoted text -
> >
> > - Show quoted text -
>|||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=A0am, 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:
> > 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: =A0 =A0 =A0stptest
> > Server: =A0 =A0 =A0 =A0 =A0 =A0 =A0149.59.22.48\STPTEST
> > Protocol: =A0 =A0 =A0 =A0 =A0 TCP\IP
> > Port: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1439
> > SQLCMD: =A0 =A0 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
> > =A0the 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:
> > > Hi
> > > I can create an TCP/IP alias for a server on the domain using the serv=ername
> > > 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 ju=st
> > > > 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 perhap=s
> > > > 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:
> > > > > Hi
> > > > > It is still not clear why you HAVE to use the alias if you can con=nect
> > > > > without it?
> > > > > Have you tried with an IP address in the Alias or changing the hos=ts file?
> > > > > John
> > > > > "SteveM" <steve.mo...@.philips.com> wrote in message
> > > > >news:905199b3-be8a-47a4-9394-9fb4c2ea3891@.y5g2000hsf.googlegroups.c=om...
> > > > > On Feb 3, 11:25 am, "John Bell" <jbellnewspo...@.hotmail.com> wrote=:
> > > > > > Hi
> > > > > > Have you tried the SQLCMD connection
> > > > > > sqlcmd -S tcp:<computer name>,<port number>
> > > > > > I can create an alias
> > > > > > Name: test
> > > > > > Port: 1433
> > > > > > Protocol: TCP/IP
> > > > > > Server: Localhost
> > > > > > and connect to it.
> > > > > > John
> > > > > > "SteveM"<steve.mo...@.philips.com> wrote in message
> > > > > >news:ccc3a173-8e6a-4a70-b622-fe08e1162347@.q21g2000hsa.googlegroup=s.com...
> > > > > > > The question is simple, the solution I suspect is not, but her=e it
> > > > > > > goes.
> > > > > > > I have a named instance (not the default) of SQL Server 2005 r=unning
> > > > > > > on a server at my company. While at work (behind the firewall)= I am
> > > > > > > able to connect to th is SQL Server instance with no problems
> > > > > > > whatsoever. I can do this through the SQL Server Management St=udio
> > > > > > > Express, I can do it through a sqlcmd on a command line, and i= can do
> > > > > > > it through connection stings within programs. The issue comes =up when
> > > > > > > I try to do it from a remote login from home. Now understand t=his, I
> > > > > > > have already authenticated past the firewall, and can ping the=
> > > > > > > physical machine, and even login in to the server. I have work=ed with
> > > > > > > our network people and know that the reason I was being blocke=d was
> > > > > > > because of the old UDP 1434 issue with regards to SQL Server. =I was
> > > > > > > instructed to set a static address instead of using dynamic
> > > > > > > addressing, which I did. I then was able to connect to the rem=ote
> > > > > > > server by all of the methods described above by using the serv=ername,
> > > > > > > port (for example say my port is 2505, set at the server, now =I can
> > > > > > > connect to it by using thisServer,2505 ). So now I remember us=ing
> > > > > > > aliases with W2K and read that you can do the same thing with =2005.. So
> > > > > > > I open the SQL Server Configuration Manager, and I set an alia=s to
> > > > > > > that machine to that port over TCP\IP. Everything I read says =that now
> > > > > > > I should be able to connect up using just the alias. So in SQL= Server
> > > > > > > Management Studio Express I should know be able to just connec=t using
> > > > > > > the alias... it fails. I should be able to connect using the a=lias
> > > > > > > using sqlcmd... this also fails. This is all very frustrating.= I have
> > > > > > > the server configured for remote connections, can connect to i=t
> > > > > > > remotely using the servername, port but can not get aliases to= work to
> > > > > > > save me. What am I doing wrong?
> > > > > > > Has anyone got this to work over TCP\IP (we are not able to us=e the
> > > > > > > other protocols where i work just TCP\IP). I could use some ex=pertise
> > > > > > > here and some help.
> > > > > > > Thanks to one and all
> > > > > > > -SteveM- Hide quoted text -
> > > > > > - Show quoted text -
> > > > > As I stated, the sqlcmd and the connection using the SQL Server
> > > > > Management Studio both work with the server\named_instance,port
> > > > > I do not seem to be able to get the alias to work in any situation=
> > > > > though
> > > > > I have an alias called stptest, I should be able to do SQLCMD -S
> > > > > stptest -E -d mydatabase
> > > > > but that doesnt work and the error isnt all that helpful (it remin=ds
> > > > > the default for SQL Server Express is local connections only - BTW= I
> > > > > have set that for local and remote and tested it inside the firewa=ll)
> > > > > So the question still remains, why isnt the alias working for me
> > > > > Thanks for your response
> > > > > -SteveM- Hide quoted text -
> > > > > - Show quoted text -- Hide quoted text -
> > > - Show quoted text -- Hide quoted text -
> - 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:
> > 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:
> > > 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:
> > > > > Hi
> > > > > It is still not clear why you HAVE to use the alias if you can
> > > > > connect
> > > > > without it?
> > > > > Have you tried with an IP address in the Alias or changing the
> > > > > hosts file?
> > > > > John
> > > > > "SteveM" <steve.mo...@.philips.com> wrote in message
> > > > >news:905199b3-be8a-47a4-9394-9fb4c2ea3891@.y5g2000hsf.googlegroups.com...
> > > > > On Feb 3, 11:25 am, "John Bell" <jbellnewspo...@.hotmail.com>
> > > > > wrote:
> > > > > > Hi
> > > > > > Have you tried the SQLCMD connection
> > > > > > sqlcmd -S tcp:<computer name>,<port number>
> > > > > > I can create an alias
> > > > > > Name: test
> > > > > > Port: 1433
> > > > > > Protocol: TCP/IP
> > > > > > Server: Localhost
> > > > > > and connect to it.
> > > > > > John
> > > > > > "SteveM"<steve.mo...@.philips.com> wrote in message
> > > > > >news:ccc3a173-8e6a-4a70-b622-fe08e1162347@.q21g2000hsa.googlegroups.com...
> > > > > > > The question is simple, the solution I suspect is not, but
> > > > > > > here it
> > > > > > > goes.
> > > > > > > I have a named instance (not the default) of SQL Server 2005
> > > > > > > running
> > > > > > > on a server at my company. While at work (behind the firewall)
> > > > > > > I am
> > > > > > > able to connect to th is SQL Server instance with no problems
> > > > > > > whatsoever. I can do this through the SQL Server Management
> > > > > > > Studio
> > > > > > > Express, I can do it through a sqlcmd on a command line, and i
> > > > > > > can do
> > > > > > > it through connection stings within programs. The issue comes
> > > > > > > up when
> > > > > > > I try to do it from a remote login from home. Now understand
> > > > > > > this, I
> > > > > > > have already authenticated past the firewall, and can ping the
> > > > > > > physical machine, and even login in to the server. I have
> > > > > > > worked with
> > > > > > > our network people and know that the reason I was being
> > > > > > > blocked was
> > > > > > > because of the old UDP 1434 issue with regards to SQL Server.
> > > > > > > I was
> > > > > > > instructed to set a static address instead of using dynamic
> > > > > > > addressing, which I did. I then was able to connect to the
> > > > > > > remote
> > > > > > > server by all of the methods described above by using the
> > > > > > > servername,
> > > > > > > port (for example say my port is 2505, set at the server, now
> > > > > > > I can
> > > > > > > connect to it by using thisServer,2505 ). So now I remember
> > > > > > > using
> > > > > > > aliases with W2K and read that you can do the same thing with
> > > > > > > 2005.. So
> > > > > > > I open the SQL Server Configuration Manager, and I set an
> > > > > > > alias to
> > > > > > > that machine to that port over TCP\IP. Everything I read says
> > > > > > > that now
> > > > > > > I should be able to connect up using just the alias. So in SQL
> > > > > > > Server
> > > > > > > Management Studio Express I should know be able to just
> > > > > > > connect using
> > > > > > > the alias... it fails. I should be able to connect using the
> > > > > > > alias
> > > > > > > using sqlcmd... this also fails. This is all very frustrating.
> > > > > > > I have
> > > > > > > the server configured for remote connections, can connect to
> > > > > > > it
> > > > > > > remotely using the servername, port but can not get aliases to
> > > > > > > work to
> > > > > > > save me. What am I doing wrong?
> > > > > > > Has anyone got this to work over TCP\IP (we are not able to
> > > > > > > use the
> > > > > > > other protocols where i work just TCP\IP). I could use some
> > > > > > > expertise
> > > > > > > here and some help.
> > > > > > > Thanks to one and all
> > > > > > > -SteveM- Hide quoted text -
> > > > > > - Show quoted text -
> > > > > As I stated, the sqlcmd and the connection using the SQL Server
> > > > > Management Studio both work with the server\named_instance,port
> > > > > I do not seem to be able to get the alias to work in any situation
> > > > > though
> > > > > I have an alias called stptest, I should be able to do SQLCMD -S
> > > > > stptest -E -d mydatabase
> > > > > but that doesnt work and the error isnt all that helpful (it
> > > > > reminds
> > > > > the default for SQL Server Express is local connections only - BTW
> > > > > I
> > > > > have set that for local and remote and tested it inside the
> > > > > firewall)
> > > > > So the question still remains, why isnt the alias working for me
> > > > > Thanks for your response
> > > > > -SteveM- Hide quoted text -
> > > > > - Show quoted text -- Hide quoted text -
> > > - Show quoted text -- Hide quoted text -
> - 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:45=A0pm, "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, therefor=e
> 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:
>
> > 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:
> > > > 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 gues=s
> > > > 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 hav=e
> > > > > 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:=
> > > > > > Hi
> > > > > > It is still not clear why you HAVE to use the alias if you can
> > > > > > connect
> > > > > > without it?
> > > > > > Have you tried with an IP address in the Alias or changing the
> > > > > > hosts file?
> > > > > > John
> > > > > > "SteveM" <steve.mo...@.philips.com> wrote in message
> > > > > >news:905199b3-be8a-47a4-9394-9fb4c2ea3891@.y5g2000hsf.googlegroups=.com...
> > > > > > On Feb 3, 11:25 am, "John Bell" <jbellnewspo...@.hotmail.com>
> > > > > > wrote:
> > > > > > > Hi
> > > > > > > Have you tried the SQLCMD connection
> > > > > > > sqlcmd -S tcp:<computer name>,<port number>
> > > > > > > I can create an alias
> > > > > > > Name: test
> > > > > > > Port: 1433
> > > > > > > Protocol: TCP/IP
> > > > > > > Server: Localhost
> > > > > > > and connect to it.
> > > > > > > John
> > > > > > > "SteveM"<steve.mo...@.philips.com> wrote in message
> > > > > > >news:ccc3a173-8e6a-4a70-b622-fe08e1162347@.q21g2000hsa.googlegro=ups.com...
> > > > > > > > The question is simple, the solution I suspect is not, but
> > > > > > > > here it
> > > > > > > > goes.
> > > > > > > > I have a named instance (not the default) of SQL Server 2005=
> > > > > > > > running
> > > > > > > > on a server at my company. While at work (behind the firewal=l)
> > > > > > > > I am
> > > > > > > > able to connect to th is SQL Server instance with no problem=s
> > > > > > > > whatsoever. I can do this through the SQL Server Management
> > > > > > > > Studio
> > > > > > > > Express, I can do it through a sqlcmd on a command line, and= i
> > > > > > > > can do
> > > > > > > > it through connection stings within programs. The issue come=s
> > > > > > > > up when
> > > > > > > > I try to do it from a remote login from home. Now understand=
> > > > > > > > this, I
> > > > > > > > have already authenticated past the firewall, and can ping t=he
> > > > > > > > physical machine, and even login in to the server. I have
> > > > > > > > worked with
> > > > > > > > our network people and know that the reason I was being
> > > > > > > > blocked was
> > > > > > > > because of the old UDP 1434 issue with regards to SQL Server=.
> > > > > > > > I was
> > > > > > > > instructed to set a static address instead of using dynamic
> > > > > > > > addressing, which I did. I then was able to connect to the
> > > > > > > > remote
> > > > > > > > server by all of the methods described above by using the
> > > > > > > > servername,
> > > > > > > > port (for example say my port is 2505, set at the server, no=w
> > > > > > > > I can
> > > > > > > > connect to it by using thisServer,2505 ). So now I remember
> > > > > > > > using
> > > > > > > > aliases with W2K and read that you can do the same thing wit=h
> > > > > > > > 2005.. So
> > > > > > > > I open the SQL Server Configuration Manager, and I set an
> > > > > > > > alias to
> > > > > > > > that machine to that port over TCP\IP. Everything I read say=s
> > > > > > > > that now
> > > > > > > > I should be able to connect up using just the alias. So in S=QL
> > > > > > > > Server
> > > > > > > > Management Studio Express I should know be able to just
> > > > > > > > connect using
> > > > > > > > the alias... it fails. I should be able to connect using the=
> > > > > > > > alias
> > > > > > > > using sqlcmd... this also fails. This is all very frustratin=g.
> > > > > > > > I have
> > > > > > > > the server configured for remote connections, can connect to=
> > > > > > > > it
> > > > > > > > remotely using the servername, port but can not get aliases =to
> > > > > > > > work to
> > > > > > > > save me. What am I doing wrong?
> > > > > > > > Has anyone got this to work over TCP\IP (we are not able to
> > > > > > > > use the
> > > > > > > > other protocols where i work just TCP\IP). I could use some
> > > > > > > > expertise
> > > > > > > > here and some help.
> > > > > > > > Thanks to one and all
> > > > > > > > -SteveM- Hide quoted text -
> > > > > > > - Show quoted text -
> > > > > > As I stated, the sqlcmd and the connection using the SQL Server
> > > > > > Management Studio both work with the server\named_instance,port
> > > > > > I do not seem to be able to get the alias to work in any situati=on
> > > > > > though
> > > > > > I have an alias called stptest, I should be able to do SQLCMD -S=
> > > > > > stptest -E -d mydatabase
> > > > > > but that doesnt work and the error isnt all that helpful (it
> > > > > > reminds
> > > > > > the default for SQL Server Express is local connections only - B=TW
> > > > > > I
> > > > > > have set that for local and remote and tested it inside the
> > > > > > firewall)
> > > > > > So the question still remains, why isnt the alias working for me=
> > > > > > Thanks for your response
> > > > > > -SteveM- Hide quoted text -
> > > > > > - Show quoted text -- Hide quoted text -
> > > > - Show quoted text -- Hide quoted text -
> > - Show quoted text -- Hide quoted text -
> - Show quoted text -