We are experiencing a strange connection problem. We are using VB
with ADO to make our connections to SQL Server. We are not specifying
the "network library", so I assume it is defaulting to using "named
pipes". Occasionally after rebooting, the client cannot connect to
the SQL Server. What we do in such a circumstance is temporarily
create an ODBC DSN, point it to the server in question, select
"TCP/IP" as the network library, and hit "Test Data Source". We don't
keep or use the DSN, but it's as if we have to "punch through" the
connection the first time. This seems to resolve the problem, and
from then on the application connects just fine using named pipes (at
least until the next reboot).
Has anyone else had this experience? Is this a known problem? Is
there a workaround? Should I just modify the application to use
Any input would be appreciated.