At 12:39 PM 19/01/2007, you wrote:

>xinetd is definitely running. I used "service xinetd status" . It's
>there.
>
>I tried netstat as you suggested and it returns that 0.0.0.0 3050 is
>listening.
>
>I thought that was really weird as there were serveral other services
>that had 127.0.0.1 3050. So I am confused as whether Linux is
>allowing the outside world to see this. I also tried ISQL and it ran
>fine.

Some comments:

1) If you used ISQL locally, i.e., not via the localhost server,
then you are not using xinetd OR the local loopback server. You are
connecting directly to the database via a Classic process that is
embedded in libfbembed.so, not an instance of the fb_inet_server
executable started by xinetd.

2) Do you know whether localhost is even available to a Xen virtual
server? If not, you'll need to use the virtual server's IP address
and the libfbclient.so as your client library. The libfbembed.so
client allows a localhost connection is localhost is available but it
can't do a connection via a real remote connection...I'm kinda
envisaging some kind of parallel between your problem and the problem
that a local RTS client with localhost on Windows.

Supposing localhost is allowable by some means, does Xen know whether
it is allowed to pass traffic between localhost and your machine's
network node? Does your machine, at network level, know that Xen
wants to pass traffic through localhost:3050?

3) If the "several other services that had 127.0.0.1:3050" were not
fb_inet_server then you now have somewhere to look. Port 3050 won't
be available for a Firebird connection if something else has live
sockets off it. So find out what those services are...if you don't
need them, disable them. If they are needed, and they are multiple,
they will all have trouble so, at a minimum, you will need to
reconfigure them. Find all that out next.

4) If it turns out that something else really-really-really must use
port 3050 then you can change Firebird's service port. Detailed
instructions are in the Firebird 1.5 release notes. (Albeit, we
still don't know whether it's Xen that's doing this to you...)

5) I suppose you have actually checked in /etc/hosts to see whether
localhost is configured. (Sorry, I don't know anything about SuSE's
graphical tools to know how you could check and configure this With
Pretty Pictures...)

./heLen