Hello,

we are having serious problems with an application that uses an ODBC
connection (System DSN) to a SQL Server in another subnet. The network is
fine, all network tests reveal nothing of consequence. However, the problem
does not appear when SQL server and client are in the same subnet.

The ODBC connection from the client gets dropped at seemingly random
intervals and in the logs one can see the following:

{NIL, 10054, [01000][10054][Microsoft][ODBC SQL Server
Driver][DBNETLIB]ConnectionWrite (send()).}

{NIL, 59, [01000][59][Microsoft][ODBC SQL Server
Driver][DBNETLIB]ConnectionWrite (WrapperWrite()).}

{NIL, -1, [08S01][0][Microsoft][ODBC SQL Server
Driver]Communication link failure}

We honestly don't know what else to look for. Maybe anyone has an idea?



Thanks in advance,



Thomas Liss

Well, after configuring "Flow Control" on the network cards of the SQL
Server, the problems were gone.



"Thomas Liss" <liss@uipugmbh.com> wrote in message
news:upFsIo9TFHA.2664@TK2MSFTNGP15.phx.gbl...
> Hello,
>
> we are having serious problems with an application that uses an ODBC
> connection (System DSN) to a SQL Server in another subnet. The network is
> fine, all network tests reveal nothing of consequence. However, the
> problem does not appear when SQL server and client are in the same subnet.
>
> The ODBC connection from the client gets dropped at seemingly random
> intervals and in the logs one can see the following:
>
> {NIL, 10054, [01000][10054][Microsoft][ODBC SQL Server
> Driver][DBNETLIB]ConnectionWrite (send()).}
>
> {NIL, 59, [01000][59][Microsoft][ODBC SQL Server
> Driver][DBNETLIB]ConnectionWrite (WrapperWrite()).}
>
> {NIL, -1, [08S01][0][Microsoft][ODBC SQL Server
> Driver]Communication link failure}
>
> We honestly don't know what else to look for. Maybe anyone has an idea?
>
>
>
> Thanks in advance,
>
>
>
> Thomas Liss
>
>

Could you please explain what was the old setting and what is the new one?

Regards,
Marko Erzen

"Thomas Liss" <liss@uipugmbh.com> wrote in message
news:e2wez$JUFHA.2172@TK2MSFTNGP15.phx.gbl...
> Well, after configuring "Flow Control" on the network cards of the SQL
> Server, the problems were gone.
>
>
>
> "Thomas Liss" <liss@uipugmbh.com> wrote in message
> news:upFsIo9TFHA.2664@TK2MSFTNGP15.phx.gbl...
> > Hello,
> >
> > we are having serious problems with an application that uses an ODBC
> > connection (System DSN) to a SQL Server in another subnet. The network
is
> > fine, all network tests reveal nothing of consequence. However, the
> > problem does not appear when SQL server and client are in the same
subnet.
> >
> > The ODBC connection from the client gets dropped at seemingly random
> > intervals and in the logs one can see the following:
> >
> > {NIL, 10054, [01000][10054][Microsoft][ODBC SQL Server
> > Driver][DBNETLIB]ConnectionWrite (send()).}
> >
> > {NIL, 59, [01000][59][Microsoft][ODBC SQL Server
> > Driver][DBNETLIB]ConnectionWrite (WrapperWrite()).}
> >
> > {NIL, -1, [08S01][0][Microsoft][ODBC SQL Server
> > Driver]Communication link failure}
> >
> > We honestly don't know what else to look for. Maybe anyone has an idea?
> >
> >
> >
> > Thanks in advance,
> >
> >
> >
> > Thomas Liss
> >
> >
>
>

Thomas,

I just read your post and we are experiencing the same kind of error
here. The communication link failure is only occurring for clients
connecting from outside of the server's home subnet and the failure is
intermittent. Did you ever resolve your problems?


*** Sent via Developersdex http://www.developersdex.com ***