Subject Re: [firebird-support] Re: Another "connection forcibly closed by the remote host" problem
Author Woody

After running as many variations of the tests that I could (it was a
holiday weekend after all) I could not duplicate the problem. Even the
inital test of just the IBOConsole seeemed to work fine now. I also had
access to the Windows 2003 Standard server at one of my clients through
terminal services. I tried different combinations on that server and it all
seemed to work fine. I am beginning to think, like the others, that this is
strictly an issue with the virtual server edition and timing but I don't
have access to a 2003 Virtual server. I am going to continue to run random
testing as much as possible to see if I can "make" it fail in some way.

Have you tried implementing a simple ping request as I suggested
earlier? You can use the TPing component of ICS to set up a simple ping if
the application is idle after so much time. I use it when my applications
first start to ping the server before even trying to connect. It might keep
whatever is timing out from doing so without causing any other problems
since it doesn't care about databases.

Woody (TMW)

----- Original Message -----
From: "Scott Moon" <smoon63@...>
To: <>
Sent: Tuesday, May 30, 2006 10:56 AM
Subject: Re: [firebird-support] Re: Another "connection forcibly closed by
the remote host" problem

I haven't made any more headway on this end. We had added a keep-alive query
routine in our in-house application, but it inexplcably caused a major bug
in one of the program modules that caused us to turn the keep-alive off. I
was just wondering if you had a chance over the weekend to run any of the
tests, and if so, what the results were.

Still hacking away at it,