Connection Timeout

Hello,
We have a sitaution at a client site where the connection string in the our
application times-out on 2 of the PC's yet 2 other PC's work fine and the
server works fine. I tried altering the Remote Connection Timeout in the SQL
Express properties from the default of 20 seconds to 60 seconds and
restarting the SQL Server but it doesn't appear to have made a difference.
They are not stopped from working, after the connection timeout box appears
the user can click Okay and bingo they are connected.
Where else should we be looking?
Thank you!
ChrisAs far as I recall, remote connection timeout was an option removed in
SQL2000. You may want to look into the connection string used by the app to
connect to the SQL instance. For instance, if it is using the .NET provider
for SQL Server, the connection timeout is set in the
System.Data.SqlClient.Connection.Timeout property.
Linchi
"Chris Marsh" wrote:

> Hello,
> We have a sitaution at a client site where the connection string in the ou
r
> application times-out on 2 of the PC's yet 2 other PC's work fine and the
> server works fine. I tried altering the Remote Connection Timeout in the S
QL
> Express properties from the default of 20 seconds to 60 seconds and
> restarting the SQL Server but it doesn't appear to have made a difference.
> They are not stopped from working, after the connection timeout box appear
s
> the user can click Okay and bingo they are connected.
> Where else should we be looking?
> Thank you!
> Chris
>
>|||Chris,
you could change the timeout property of the connection string / command
object to overcome the issue. However I'd start by looking at network
connectivity between the 2 PCs and the main box. You could start with
ping -t but your network admin guys might have some better tools for this.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .