Subject Re: Another "connection forcibly closed by the remote host" problem
Author Adam
> I have a mini-network at home where I work. My main computer runs
Win2K and
> has FB 1.5.3 SS running. I also use my laptop as an FB server and
client for
> testing back and forth. For a quick test, I opened IBOConsole on the
> (Windows XP Home Edition Version 2002 SP2), connected to my main
> and then connected to a database. I didn't select anything else in
> IBOConsole, views, tables, etc. I just let it sit on the database name.
> After a little over an hour, I clicked on the tables and voila, I
get the
> same error about the connection being closed.
> I am going to try it again (I have only done it once so far) but I
> it might be important to let someone know that I saw the same
problem occur
> at least once in a simple environement without any MS server software
> running.

> Now, at the same time that I was just letting IBOConsole sit there,
I was
> listening to Rush through a stream on the Internet on the laptop.
> the network card

[*** on the laptop ***]

> can not be a factor since it was continually being used for
> the streaming.

Of course, if the network card on the server turns itself off, you
have the same thing.

> I will continue some further testing and if I can confirm this using
> IBOConsole as well as one of my own programs, I would like to ask
for more
> guidance in helping track down this type of problem. I'm not an FB
guru and
> I don't have the means to compile C source. (I'm a Delphi guy
through and
> through :)

I know some of our customers leave their machine logged in over the
weekend (yes the same muppets that whinge that we should implement a
password expiration policy but anyone can walk up to their machine and
do whatever) and we do not experience these sorts of issues. There is
no keepalive timer on this setup.

I do not know what IBOConsole does, certainly if you could duplicate
it using iSQL as the client on multiple machines, there may be a case
for a bug report.

If Firebird implemented its own keepalive heartbeat, then we would
never run into this problem, but naturally that is easier said than done.