Connecting to SQL Server 2005

Hi,
I am having ongoing problems connecting to the server. I thought I had it
solved thanks to help from a prev post:
C:\>sqlcmd -S dimension9150\SQLExpress
HResult 0xFFFFFFFF, Level 16, State 1
SQL Network Interfaces: Error Locating Server/Instance Specified
[xFFFFFFFF].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establi
shing a connection to the server. When connecting to SQL Server 2005, this
failu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
C:\>sqlcmd -S dimension9150\SQLExpress,1433
1> exit
C:\>
Now at least i can connect to the server using the sqlcmd utility however I
am unable to get a connection string to connect.
cmdCommand.ActiveConnection =
" Server=dimension9150;Database=IPS;Truste
d_Connection=True"
This simply returns an error number -2147467259
As with the sqlcmd utility do I need to specify port 1433 in my connection
sting ?
I am not running the SQL Browser service as I understand it is better not to
for security reasons and understand this makes connecting harder ?
I am running a firewall program on the server "Norton Internet Security"
however as it was not stopping sqlcmd from working I had assumed it would
not be a problem for my connection string either.
Any help would be greatly appreciated.
Thanks in advance...If you don't use the SQL Browser service, you would need to specify the port
in your case.
Linchi
"McHenry" wrote:

> Hi,
> I am having ongoing problems connecting to the server. I thought I had it
> solved thanks to help from a prev post:
> C:\>sqlcmd -S dimension9150\SQLExpress
> HResult 0xFFFFFFFF, Level 16, State 1
> SQL Network Interfaces: Error Locating Server/Instance Specified
> [xFFFFFFFF].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server do
es
> not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> C:\>sqlcmd -S dimension9150\SQLExpress,1433
> 1> exit
> C:\>
>
> Now at least i can connect to the server using the sqlcmd utility however
I
> am unable to get a connection string to connect.
> cmdCommand.ActiveConnection =
> " Server=dimension9150;Database=IPS;Truste
d_Connection=True"
> This simply returns an error number -2147467259
> As with the sqlcmd utility do I need to specify port 1433 in my connection
> sting ?
> I am not running the SQL Browser service as I understand it is better not
to
> for security reasons and understand this makes connecting harder ?
> I am running a firewall program on the server "Norton Internet Security"
> however as it was not stopping sqlcmd from working I had assumed it would
> not be a problem for my connection string either.
> Any help would be greatly appreciated.
>
> Thanks in advance...
>
>|||I have exactly the same problem.
I had SQL SERVER 2005 running but I cleaned all out for a reinstall
and now I get exactly the error you get.
c:\sqlcmd -S dimension9150\SQLExpress,1433 gets the same error
I have set shared memory, pipes, tcp/ip, set ports to no avail
"McHenry" wrote:

> Hi,
> I am having ongoing problems connecting to the server. I thought I had it
> solved thanks to help from a prev post:
> C:\>sqlcmd -S dimension9150\SQLExpress
> HResult 0xFFFFFFFF, Level 16, State 1
> SQL Network Interfaces: Error Locating Server/Instance Specified
> [xFFFFFFFF].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server do
es
> not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> C:\>sqlcmd -S dimension9150\SQLExpress,1433
> 1> exit
> C:\>
>
> Now at least i can connect to the server using the sqlcmd utility however
I
> am unable to get a connection string to connect.
> cmdCommand.ActiveConnection =
> " Server=dimension9150;Database=IPS;Truste
d_Connection=True"
> This simply returns an error number -2147467259
> As with the sqlcmd utility do I need to specify port 1433 in my connection
> sting ?
> I am not running the SQL Browser service as I understand it is better not
to
> for security reasons and understand this makes connecting harder ?
> I am running a firewall program on the server "Norton Internet Security"
> however as it was not stopping sqlcmd from working I had assumed it would
> not be a problem for my connection string either.
> Any help would be greatly appreciated.
>
> Thanks in advance...
>
>