2005 remote connection problem (yes, I have enabled TCP/IP)

I've gone through about 30+ google results looking for the magic answer to
this problem. I have a brand new machine with a brand new install of Sql
Server 2005 express. I am trying to connect via SQLCMD in a command window
with the following info: SQLCMD -S 192.168.1.103 -U **** -P ******!
the ip is my local machine and the machine that SS2005 Express is installed
on.
-U is a login that I created. I have set authentication to mixed mode
Not sure what else to try. Anyone have any hints?
"sklett" <sklett@.mddirect.com> wrote in message
news:%23s3PyC0NGHA.3908@.TK2MSFTNGP10.phx.gbl...
> I've gone through about 30+ google results looking for the magic answer to
> this problem. I have a brand new machine with a brand new install of Sql
> Server 2005 express. I am trying to connect via SQLCMD in a command
> window with the following info: SQLCMD -S 192.168.1.103 -U **** -P ******!
> the ip is my local machine and the machine that SS2005 Express is
> installed on.
> -U is a login that I created. I have set authentication to mixed mode
>
By default SqlExpress uses an instance name of SQLEXPRESS. Your connection
info would be correct for the default instance, not a named instance.
Try
SQLCMD -S 192.168.1.103\SQLEXPRESS -U **** -P ******!
How to: Connect to the Database Engine Using sqlcmd.exe
http://msdn2.microsoft.com/en-us/library(d=robot)/ms188247.aspx
Also to user the instance name you need the SQL Browser service started.
And double check in Computer Management\SQL Server Configuration
Manager\Protocols for SQLEXPRESS TCP/IP is enabled for that IP interface.
David
|||Have you enabled remote connections? Yes, you have to explicitly enable it
to accept connections from external machines. Doesn't matter what libraries
or connection strings you are sending. If remote connections are not
enabled, the only thing that any SQL Server 2005 database will respond to is
something from the machine it resides on.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"sklett" <sklett@.mddirect.com> wrote in message
news:%23s3PyC0NGHA.3908@.TK2MSFTNGP10.phx.gbl...
> I've gone through about 30+ google results looking for the magic answer to
> this problem. I have a brand new machine with a brand new install of Sql
> Server 2005 express. I am trying to connect via SQLCMD in a command
> window with the following info: SQLCMD -S 192.168.1.103 -U **** -P ******!
> the ip is my local machine and the machine that SS2005 Express is
> installed on.
> -U is a login that I created. I have set authentication to mixed mode
> Not sure what else to try. Anyone have any hints?
>
|||Hi Michael,
I have enabled them the only way I know how, what I did was use "SQL Server
Surface Are Configuration" app and checked the "Using TCP/IP only" option
under the "Local and remote connections" section. This is one of the first
things that I did. I should have mentioned that in my original post,
apologies.
Any other ideas?
"Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
news:u%23XwyS0NGHA.3144@.TK2MSFTNGP11.phx.gbl...
> Have you enabled remote connections? Yes, you have to explicitly enable
> it to accept connections from external machines. Doesn't matter what
> libraries or connection strings you are sending. If remote connections
> are not enabled, the only thing that any SQL Server 2005 database will
> respond to is something from the machine it resides on.
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "sklett" <sklett@.mddirect.com> wrote in message
> news:%23s3PyC0NGHA.3908@.TK2MSFTNGP10.phx.gbl...
>
|||Hi David,
I have tried to specify the name in the address, it doesn't make a
difference I'm afraid.
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:OmHC9Q0NGHA.2668@.tk2msftngp13.phx.gbl...
> "sklett" <sklett@.mddirect.com> wrote in message
> news:%23s3PyC0NGHA.3908@.TK2MSFTNGP10.phx.gbl...
> By default SqlExpress uses an instance name of SQLEXPRESS. Your
> connection info would be correct for the default instance, not a named
> instance.
> Try
> SQLCMD -S 192.168.1.103\SQLEXPRESS -U **** -P ******!
>
> How to: Connect to the Database Engine Using sqlcmd.exe
> http://msdn2.microsoft.com/en-us/library(d=robot)/ms188247.aspx
> Also to user the instance name you need the SQL Browser service started.
> And double check in Computer Management\SQL Server Configuration
> Manager\Protocols for SQLEXPRESS TCP/IP is enabled for that IP interface.
> David
>