SQL 2000 TIMEOUT ERROR WHEN TRYING TO CONNECT USING C#

[=?Utf-8?B?VGVycmFuY2U=?=]

I have an application that runs fine on my machine(of course) that access the
local Sql Server. However, when trying to run this application from another
machine I receive a Sql timeout error. I thought it was my stored procedure
but that doesn't seem to be the case. The following are the connection
strings that I've tried:

//private string connstring = "integrated security=SSPI;data source=<ip
address>;"
// "persist security info=False;initial catalog=projectDB";

private string connstring = "pwd=<password>;uid=<username>;" +
"database=projectDB;server=<ip address>";

//private string connstring = "Data Source=<ip address>;" +
// "Initial Catalog=projectDB;" +
// "User Id=<username>;" +
// "Password=<password>";

Do anyone know how I can get over this hump? By the way I'm running the
application locally on the remote computer.
--
TC

[Norman Yuan]

1. If the SQL Server and the app are not on the same computer, make sure the
SQL Server allows remote access.
2. Since you pass username/password in ConnectionString, make sure the SQL
Server has mixed security mode enabled (by default installed, only Windows
security mode is enabled).

"Terrance" <Te******@discussions.microsoft.comwrote in message
news:23**********************************@microsof t.com...

>I have an application that runs fine on my machine(of course) that access
the
local Sql Server. However, when trying to run this application from
another
machine I receive a Sql timeout error. I thought it was my stored
procedure
but that doesn't seem to be the case. The following are the connection
strings that I've tried:

//private string connstring = "integrated security=SSPI;data source=<ip
address>;"
// "persist security info=False;initial catalog=projectDB";

private string connstring = "pwd=<password>;uid=<username>;" +
"database=projectDB;server=<ip address>";

//private string connstring = "Data Source=<ip address>;" +
// "Initial Catalog=projectDB;" +
// "User Id=<username>;" +
// "Password=<password>";

Do anyone know how I can get over this hump? By the way I'm running the
application locally on the remote computer.
--
TC

[=?Utf-8?B?VGVycmFuY2U=?=]

How do I determine if the sql server does or does not allow remote access?
--
TC
"Norman Yuan" wrote:

1. If the SQL Server and the app are not on the same computer, make sure the
SQL Server allows remote access.
2. Since you pass username/password in ConnectionString, make sure the SQL
Server has mixed security mode enabled (by default installed, only Windows
security mode is enabled).

"Terrance" <Te******@discussions.microsoft.comwrote in message
news:23**********************************@microsof t.com...

I have an application that runs fine on my machine(of course) that access
the
local Sql Server. However, when trying to run this application from
another
machine I receive a Sql timeout error. I thought it was my stored
procedure
but that doesn't seem to be the case. The following are the connection
strings that I've tried:

//private string connstring = "integrated security=SSPI;data source=<ip
address>;"
// "persist security info=False;initial catalog=projectDB";

private string connstring = "pwd=<password>;uid=<username>;" +
"database=projectDB;server=<ip address>";

//private string connstring = "Data Source=<ip address>;" +
// "Initial Catalog=projectDB;" +
// "User Id=<username>;" +
// "Password=<password>";

Do anyone know how I can get over this hump? By the way I'm running the
application locally on the remote computer.
--
TC

[=?Utf-8?B?VGVycmFuY2U=?=]

I checked the Sql Server and it has Allow other SQL Servers to connect
remotely to this SQl using RPC. Is this what your were talking about?

--
TC
"Norman Yuan" wrote:

1. If the SQL Server and the app are not on the same computer, make sure the
SQL Server allows remote access.
2. Since you pass username/password in ConnectionString, make sure the SQL
Server has mixed security mode enabled (by default installed, only Windows
security mode is enabled).

"Terrance" <Te******@discussions.microsoft.comwrote in message
news:23**********************************@microsof t.com...

I have an application that runs fine on my machine(of course) that access
the
local Sql Server. However, when trying to run this application from
another
machine I receive a Sql timeout error. I thought it was my stored
procedure
but that doesn't seem to be the case. The following are the connection
strings that I've tried:

//private string connstring = "integrated security=SSPI;data source=<ip
address>;"
// "persist security info=False;initial catalog=projectDB";

private string connstring = "pwd=<password>;uid=<username>;" +
"database=projectDB;server=<ip address>";

//private string connstring = "Data Source=<ip address>;" +
// "Initial Catalog=projectDB;" +
// "User Id=<username>;" +
// "Password=<password>";

Do anyone know how I can get over this hump? By the way I'm running the
application locally on the remote computer.
--
TC

[Norman Yuan]

OK, if the SQL Server is accessible from other computer, you then need to
make sure it does accept username/pasword pair (that is, mixed security mode
is enabled).
"Terrance" <Te******@discussions.microsoft.comwrote in message
news:9C**********************************@microsof t.com...

>I checked the Sql Server and it has Allow other SQL Servers to connect
remotely to this SQl using RPC. Is this what your were talking about?

--
TC
"Norman Yuan" wrote:

>1. If the SQL Server and the app are not on the same computer, make sure
the
SQL Server allows remote access.
2. Since you pass username/password in ConnectionString, make sure the
SQL
Server has mixed security mode enabled (by default installed, only
Windows
security mode is enabled).

"Terrance" <Te******@discussions.microsoft.comwrote in message
news:23**********************************@microso ft.com...

>I have an application that runs fine on my machine(of course) that
access
the
local Sql Server. However, when trying to run this application from
another
machine I receive a Sql timeout error. I thought it was my stored
procedure
but that doesn't seem to be the case. The following are the connection
strings that I've tried:

//private string connstring = "integrated security=SSPI;data source=<ip
address>;"
// "persist security info=False;initial
catalog=projectDB";

private string connstring = "pwd=<password>;uid=<username>;" +
"database=projectDB;server=<ip address>";

//private string connstring = "Data Source=<ip address>;" +
// "Initial Catalog=projectDB;" +
// "User Id=<username>;" +
// "Password=<password>";

Do anyone know how I can get over this hump? By the way I'm running the
application locally on the remote computer.
--
TC