Thanks again ./heLen

Followed this advice and more, unfortunately each not any more
helpful than previously:
-RPM'd the NPTL version
-turned off multithreading in BIOS under 'advanced chipset options'
-followed advice in release notes under' NTPL problems on higher
Linuxen' eg in /etc/init.d/firebird --> LD_ASSUME_KERNEL=2.2.5
export LD_ASSUME_KERNEL

The funny thing is that I can simultaneously connect to each of
these 2 databases on the Centos server (192.168.2.10) using
different GUI programs on the worksation (192.168.2.15 -ib_sql to
connect to one database and ibaccess for another), with connection
info viewable on the server:
IPV4 TCP 0u Listening on port gds_db
IPV4 TCP 1u 192.168.2.10:gds_db -> 192.168.2.15:2854 ESTABLISHED
IPV4 TCP 7u 192.168.2.10:gds_db -> 192.168.2.15:2904 ESTABLISHED

*BUT* when I try to run my workstation's clinical app which requires
a connection to BOTH of the same database, it persistently refuses
to connect to a particular one of these databases and the program
exits!

I have some 701 frames of tcp data betw the two computers from when
the clinical app was trying to connect (via a capture tool), but it
doesn't really help me - eventually the clinical app seems to give
up and requests a disconnect. Here are the first frames:

No. Time Source Destination Protocol Info
1 0.000000 192.168.2.15 192.168.2.10 TCP 3120

> gds_db [SYN] Seq=0 Ack=0 Win=60000 Len=0 MSS=1260

Frame 1 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: 00:20:ed:1e:92:32, Dst: 00:14:5e:41:06:8e
Internet Protocol, Src Addr: 192.168.2.15 (192.168.2.15), Dst Addr:
192.168.2.10 (192.168.2.10)
Transmission Control Protocol, Src Port: 3120 (3120), Dst Port:
gds_db (3050), Seq: 0, Ack: 0, Len: 0

No. Time Source Destination Protocol Info
2 0.000247 192.168.2.10 192.168.2.15 TCP
gds_db > 3120 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460

Frame 2 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: 00:14:5e:41:06:8e, Dst: 00:20:ed:1e:92:32
Internet Protocol, Src Addr: 192.168.2.10 (192.168.2.10), Dst Addr:
192.168.2.15 (192.168.2.15)
Transmission Control Protocol, Src Port: gds_db (3050), Dst Port:
3120 (3120), Seq: 0, Ack: 1, Len: 0

If you or anyone has any ideas it would be most helpful

Rgds
very_compused

> Rather, considering the office has Red Hat 8 (old threading model)
> and home has Centos 4.3 (2.6.9+ kernel, which has the new/native
> threading library (NPTL). Try either doing a full uninstall of

the

> old threading version of the v.1.5.3 rpm and replacing it with the
> NPTL version; or study the piece in the installation section of

the

> release notes about setting up your Linux to force it to use the

old

> threading model.
>
> ./heLen
> Misinformation Technology Autodidact
>
>
>
> >Regards
> >Michael
> >
> >Pastes:
> >1. Centos (at home - database connection problem)
> >For process /opt/firebird/bin/fbserver (PID 697)
> >Open network connections
> >Type Protocol File Descriptor Details
> >IPV4 TCP 0u Listening on port gds_db
> >
> >netstat -an | grep 3050
> >tcp 0 0 0.0.0.0:3050 0.0.0.0:* LISTEN
> >
> >
> >2. Office computer (firebird working - Red Hat 8)
> >
> >For process /opt/firebird/bin/fbserver (PID 697)
> >Open network connections
> >Type Protocol File Descriptor Details
> >IPV4 TCP 0u Listening on port gds_db
> >IPV4 TCP 1u 127.0.0.1:gds_db -> 127.0.0.1:32772 ESTABLISHED
> >IPV4 TCP 7u 127.0.0.1:gds_db -> 127.0.0.1:32773 ESTABLISHED
> >IPV4 TCP 8u 127.0.0.1:gds_db -> 127.0.0.1:32775 ESTABLISHED
> >IPV4 TCP 9u 192.168.1.111:gds_db -> 192.168.1.21:2625 ESTABLISHED
> >IPV4 TCP 11u 192.168.1.111:gds_db -> 192.168.1.21:2626 ESTABLISHED
> >
> >
> >netstat -an | grep 3050
> >tcp 0 0 0.0.0.0:3050 0.0.0.0:*
> >LISTEN
> >tcp 0 0 127.0.0.1:3050 127.0.0.1:32775

ESTABLISHED

> >tcp 0 0 127.0.0.1:3050 127.0.0.1:32773

ESTABLISHED

> >tcp 0 0 127.0.0.1:3050 127.0.0.1:32772

ESTABLISHED

> >tcp 0 0 127.0.0.1:32773 127.0.0.1:3050

ESTABLISHED

> >tcp 0 0 127.0.0.1:32772 127.0.0.1:3050

ESTABLISHED

> >tcp 0 0 127.0.0.1:32775 127.0.0.1:3050

ESTABLISHED

> >
> > > I don't know. There are no clues here regarding

authentication,

> >though.
> > >
> > > The firebird.log file doesn't get written to during
> > > installation. However, the gethostbyname clue says that a

client

> > > asked to connect to host by the name of asterisk1.local and the
> > > network couldn't find a mapping for it. Apparently it's the
> > > hard-coded server name the application is trying to connect to,
> >not
> > > the IP address you put in your ini file.
> > >
> > > Look in the /etc/hosts file and see what's there for that IP
> > > address....if necessary, add an entry:
> > > 192.168.2.10 asterisk1.local
> > >
> > > (case-sensitive on Linux) and see whether the app has any

better

> > > success at connecting.
> > >
> > > Might need a similar entry in the $windir$\system32
> >\drivers\etc\hosts
> > > file on the client, as well.
> > >
> > > ./heLen
> > >
> >
> >
> >
> >
> >
> >
> >++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> >Visit http://www.firebirdsql.org and click the Resources item
> >on the main (top) menu. Try Knowledgebase and FAQ links !
> >
> >Also search the knowledgebases at http://www.ibphoenix.com
> >
> >++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> >Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
>