> Have you tried gsec -display ?

Yep, but it says:
-----
[interbase@ojo bin]$ gsec -display
connection rejected by remote interface
unable to open database
---

> Or check with ps ax|grep ib

Yep, it says:
----
[interbase@ojo bin]$ ps ax|grep ib
1441 ? S 0:00 /usr/lib/powerchute/bkupsd /dev/ttyS0 117815209
2223 ? S 0:02
/usr/lib/netscape/netscape-communicator -irix-session
2898 pts/8 S 0:00 grep ib
----

So, interbase isn't running.

> Check that loopback is working:
> The output of route -n should contain a line like
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
> lo

It says:
-----
[root@ojo root]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 10.0.0.9 0.0.0.0 UG 0 0 0 eth0
[root@ojo root]#
-----

So that looks ok.

> Check that we know our names:
> /etc/hosts should at least contain:
> 127.0.0.1 localhost
> and with the correct IP-address, and FQDN sth. like:
> 192.168.0.3 ojo.somedomain.com ojo

The /etc/hosts contains at least:
----
127.0.0.1 localhost.localdomain localhost
10.0.0.3 ojo.unwired ojo
----

> Check that we can ping the local machine
> ping -c2 ojo
> should return something like
> 64 bytes from 192.168.0.3: icmp_seq=0 ttl=255 time=0.359 ms
> 64 bytes from 192.168.0.3: icmp_seq=1 ttl=255 time=0.209 ms
> in a reasonable time.

It says:
---
[root@ojo root]# ping ojo
Warning: no SO_TIMESTAMP support, falling back to SIOCGSTAMP
PING ojo.unwired (10.0.0.3) from 10.0.0.3 : 56(84) bytes of data.
64 bytes from ojo.unwired (10.0.0.3): icmp_seq=0 ttl=255 time=60 usec
----

> /etc/services should contain the line
> gds_db 3050/tcp # InterBase Database Remote Protocol

It contains:
---
gds_db 3050/tcp # InterBase Database Remote Protocol
----

> and /etc/inetd.conf should *not* contain sth like:
> gds_db stream tcp nowait root
> /opt/interbase/bin/gds_inet_server gds_inet_server

This file is empty.

> and there shouldn't be an xinetd entry either.

There isn't an entry

As you can see, nothing strange configured, so it should work.

> Seems to be time to get a copy of this ugly RedHat 7 myself,
> to check why this distribution behaves so IB unfriendly.

This wouldn't be a bad idea, as I heard some other complaining about it as
well. The only thing is that for me, going back to RH 6.2 is a bit
difficult. A friend of my, who knows quite a bite about Linux was playing a
day with interbase to get it working under RedHat 7.0 but had no luck, and
told me that it doens't work. However I think it should work and it should
be solved.
Buttttt it seems harder than it looks apearently.
BTW: what Linux version do you prefer ?

Do you know what the meaning of these error numbers is, that appear in the
log file:
----
ojo (Client) Mon Dec 11 13:23:52 2000
INET/inet_error: read errno = 104

ojo (Client) Mon Dec 11 13:23:52 2000
INET/inet_error: receive in try_connect errno = 104

ojo (Client) Mon Dec 11 13:23:52 2000
/opt/interbase/bin/ibguard: guardian starting bin/ibserver


ojo (Server) Mon Dec 11 13:23:52 2000
INET/inet_error: bind errno = 98

ojo (Client) Mon Dec 11 13:23:52 2000
/opt/interbase/bin/ibguard: bin/ibserver terminated due to startup
error (2)
----

What do we do now ??

Thanks and regards,
Ed