Hi,


Thanks everyone for replying. Here a quick update on the testing.
Put in a laptop to replace the server and the problem is gone.

Took the client's server back for testing and unsurprisingly the problem could not be reproduced anymore at my office. Going to perform few test on the server before deciding to reformat the server.


Thanks and regards,
John

--- In firebird-support@yahoogroups.com, "gwc8182" <gwc8182@...> wrote:
>
> Hi everyone,
>
> I have encountered a weird network problem and have no idea what might be the cause of it.
>
> Background info: Using Firebird 2.0.5
> Program is written on Delphi with BDE.
> Server is Windows 7 Ultimate
> Clients are running mixed of Windows 7 Starter, Home Premium, WinXP, Vista Home Premium.
>
> Client connection path to the database is using TCP/IP
>
>
> Situation: Client's program frequently shows
> Error writing data to the connection
> An existing connection was forcibly closed by the remote host
>
> Client stated it happened after using the program for some time.
> As testing, I tried saving couple of big transaction on the client computer and will encountered the same error. Note: Processing time for the transaction takes less then 3 mins.
>
> Initially thought might be related to memory but hit the same problem with a computer with 2 GB memory. Tried adjusting memory usage in Firebird.conf file but makes no different. Firebird.conf was then restore back to original to continue testing for other possibility.
>
> Testing on network so far shows it is stable.
> Perform test by pinging the server and then transferring file to the server while the program is running. Will get the same error above but ping and file transfer continue without hiccup.
> Perform another test by having two program open. Only the program running the test above will crashed with error and the second program can continue being used without any problem.
>
>
> Server Firebird's log file only recorded 10054 error.
> Tried running both SuperServer and Classic mode and
> tried Firebird 2.5.1 as well but no go.
>
> Also suspected something is not right with the program but running the same test at my own office with lower end computer and much heavier transaction will not have any problem. I pretty much given up and not sure what so unique about this client network that keep getting this error.
>
> Thanks and regards,
> John
>