Hi Lester,

There are two things you should on Linux.
1 - To accelerate the connection, try registering the IPs of the PCs
that will connect in the /etc/hosts file

2 - if you have lots of connections, you should consider modifying the
/etc/xinet.d/firebird file and add

instances = UNLIMITED

Give it a try

Regards

Salim

--- In firebird-support@yahoogroups.com, Lester Caine <lester@...> wrote:
>
> Marcin Bury wrote:
> > I can't directly find out what OS is running on workstations 'having
> > problems' connecting to Firebird CS on Linux box.
> > If this OS is Windows XP with recent updates applied I have some
solution
> > for you.
> >
> > Xinetd service on Linux box requires that workstation trying to
connect to
> > 'introduce' itself. This operation requires that port 113 should
be open on
> > WinXP workstation. One of the recent MS so called security patches
closes
> > this port by default.
> >
> > The are two way of solving this issue:
> > 1. There is some parameters in xinetd configuration that is
responsible for
> > the amount of time that linux box waits for the 'introduction' and
this time
> > can be reduced to some minimum
> That was one of the original questions on this thread as I haven't
found a
> good reference to the xinetd setup.
>
> > 2. Simply open port 113 on Win XP workstation (firewall settings)
> No firewall enabled on all three machines
>
> > A few weeks ago we setup a new linux box in customer office. Since
the
> > amount of concurrent connections often reaches 100 and more we
decided to
> > try Classic Firebird. Then we expirenced huge delay in connecting
to the
> > database - even 60 second. After that application works like a
charm and
> > users started to say 'woooow'. Everything would be great but this
delay...
> > We have noticed that this delay occured only on WinXP
workstations, we have
> > some Win2K boxes and even one or two Win98 ;-). These workstations
were
> > connecting to the Firebird immiediately.
> Yep - XP - but it was working fine here.
> Another question was if switching to Superserver would help. I've
only 10 or
> so active connections when running.
>
> > My friend, who is linux administrator in this company, did some
searching in
> > Internet and found that xinetd requires some comunication through
port 113
> > before establishing connection bewteen Firebird client and server.
Opening
> > port 113 in firewall setting on WinXP solved the issue.
> The port is open, but the customer has supplied fixed IP addresses
for the
> machines and I don't think that they are actually defined *IN* the
DNS server.
> Could this be a problem for xinetd?
>
> > Lester, if you need further details - let me know - I ask my
friend to
> > provide them.
> This *IS* something that needs getting to the bottom of. The site
has run fine
> all day with Firebird on the XP machine so it is just the connection
into
> Firebird that is causing a problem :(
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
> L.S.Caine Electronic Services - http://home.lsces.co.uk
> MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
> Firebird - http://www.firebirdsql.org/index.php
>