Communication Link Failure

Dear experts~
My client workstation recently receives "ODBC failed -
Connection bluh bluh bluh... SQL Server: Communication
Link Failure" error message while trying to insert/update
a record. This happens on two workstations. This problem
would soon go away in few seconds and come back few hours
latter. What's interesting is when users reported
Communication Link Failure, I am still able to connect to
the SQL Server through other workstations.
I checked my Network Config. Both TCP and Name Pipes are
enabled. My server runs well for a longest time and I
haven't make any changes on Configs recently. I'd like to
know what would cause this problem occurs and Could this
be a result of Bad Network Connection rather than SQL
Server Config. Or, What I can do on SQL Server to get
rid of this problem.
I am running SQL Server 2000 SP2. The client workstion
uses MS Access .mdb file with linked table to connect to
SQL Server 2000.
Thank you soooooo much for your help~~~
Annie
.Annie,
More than likely you have a network error. I say this because the error is confined to 2 workstations and you are able to access the server from your workstation. A couple of things to try:
you can do a simple test of the network connection by using the ping command. Use the -n parameter to send a large number of echo requests. Pay attention to the statistics on lost packets and round-trip time.
If packets are being lost or the returns times are higher check the event logs on the workstations with the problems for network related software or hardware problems.
Make sure you are not having any DNS problems. Check if you can consistently link to the server by specifying the server ip address in the ODBC Datasource defintion
My experience with Named Pipes is that it can be slow on a tcp/ip network. I would configure the ODBC Datasource defintions to use only tcp/ip.
Good Luck
Lewis DiFelice
DBA
-- piyomeme@.yahoo.com wrote: --
Dear experts~
My client workstation recently receives "ODBC failed -
Connection bluh bluh bluh... SQL Server: Communication
Link Failure" error message while trying to insert/update
a record. This happens on two workstations. This problem
would soon go away in few seconds and come back few hours
latter. What's interesting is when users reported
Communication Link Failure, I am still able to connect to
the SQL Server through other workstations.
I checked my Network Config. Both TCP and Name Pipes are
enabled. My server runs well for a longest time and I
haven't make any changes on Configs recently. I'd like to
know what would cause this problem occurs and Could this
be a result of Bad Network Connection rather than SQL
Server Config. Or, What I can do on SQL Server to get
rid of this problem.
I am running SQL Server 2000 SP2. The client workstion
uses MS Access .mdb file with linked table to connect to
SQL Server 2000.
Thank you soooooo much for your help~~~
Annie
..