Subject Re: [firebird-support] TCPIP vs Piped lines
Author Mark Rotteveel
You could have a virus scanner or firewall on one or both sides that closes the connection prematurely. I am not exacly sure, but I believe that for example NOD32 has a mode where it closes a (not well known) port if it receives a lot of traffic in a short time period.

This would most likely also cause an error 10054.

Mark

> Hello:
>
> I have an application installed in a network with the following technical
> data:
>
> Delphi 5 with IBX
> FireBird 2.1.2.18118 SS
> Server: Windows 2003 Server
> Clients: Windows XP SP3
>
> Using the application in the server or connecting to the server via
> Terminal server, everything works perfect.
>
> Using the application in a PC client of the local network, ALMOST
> everything works perfect. In only 3 of the tables, when the application executes a
> SELECT * FROM <TableName>, the application "hangs". In firebird.log I see
> the following:
>
> INET/inet_error: read errno = 10054
>
> Looking for this error code, I found that may be this is because the table
> has too many fields. But this is not the case because it happens with a
> table with 93 fields, but it does not happen with other tables that have, for
> example, 145 fields.
>
> To access the database I was using TCPIP style. For example:
> SERVER:ALIASOFMYDATABASE. Following a suggestion I found, I changed this to piped lines.
> For example: \\SERVER\ALIASOFMYDATABASE. With this change, now ¡it works!
>
> But I have other customers with networks similar to this one and
> everything works fine using TCPIP. So I guess, there has to be something that is
> causing this problem in this case.
>
> Then my question is:
>
> What may be causing this?
--
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser