Below is our issue for SQL Express 2005 (SP3)

We have an application that utilizes SQL Express 2005 as database.
The application is installed locally at the branch pc and accesses a local
database and we have no problem with it.
However, we have branches having 2 PCs.
The set-up here is that PC1 will have the application and SQL server and
database installed, while PC2 has the application and no database installed
(though SQL Server exists).
PC2's connection string points to PC1's SQL server name.

The problem here is that PC2's SQL connection is intermittent. During Day1
implementation of the application, we were able to use the apps in PC2
connection to PC1's SQL database from morning to 12noon. We encountered a
broadband connection problem around 12 noon but were resolved when we reset
the modem router of the broadband. Afterwards, PC2 apps encountered
problems connection to SQL of PC1.


There are days wherein the PC2 works (able to connect to SQL Express in PC1)
but most of the time it does not work.

We already ruled out the network connection since PC1 and PC2 is connected
directly to the broadband dsl router. We can ping PC1 from PC2 without any
problem.


Anyone please advise.

What exactly "it does not work" mean? Can you tell it in "SQL Server"
language? For instance, do you get an error, if so what's the error message?
It'll be good if you try to be more specific.

--
Ekrem Önsoy - SQL Server MVP



"Jerome Pacificar" <test1 (AT) pjlhuillier (DOT) com>, iletisinde sunu yazdi,
news:%23zsTlqQBKHA.1492 (AT) TK2MSFTNGP03 (DOT) phx.gbl...