I downloaded Firebird 2.1 for windows and loaded the client (Developer) on the Vista 64 and XP boxes. I can use the iSQL tool from those packages to connect and run a select query.

(firebird:firebird) - You are correct - this was a type by me.

I connect to the server using flamerobin and add a user. This is from the Vista 64 box. I assume that because of the above the connect strings and the firewall can be discounted in this case.

To support this I used jaybird to connect using Open Office.

My problem is when I try to open the example db after connecting to the server.

My connection string is

cedar/3050:/opt/firebird/examples/empbuild/employee.fdb

Any pointers?

--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...> wrote:
>
> At 03:18 PM 19/05/2009, you wrote:
> >I can connect from my Vista 64bit machine with the Firebird 2.1 client iSQL tool and JDBC (Openoffice.org 3). The server is Slackware linux 12.2, updated and running SuperServer 2.1.
> >
> >The hostname resolves ok and I can register the server in flamerobin but when I try to connect to the example db I get the "isc_attach_database failed" "Unavailable Database" errors.
> >
> >I cannot connect using ODBC either.
> >
> >I've tried flamerobin on a XP machine with the same result.
>
> You haven't mentioned anything about Firebird client libraries (fbclient.dll for your Windows clients, libfbclient.so for your Linux clients).
>
>
> >I've checked the permissions of the employee.fdb (Firebird:Firebird).
>
> should be firebird:firebird, surely? (Linux case-sensitivity).
>
> Likewise, paths must be passed in the form understood by the server, viz., regardless of the client platform, a connection string such as:
>
> localhost/3050:/opt/firebird/examples/empbuild/employee.fdb
>
> is different to
>
> Localhost/3050:/opt/firebird/examples/empbuild/EmPLOyEe.fDb
>
> Check also whether the firewall on your Slackware server is configured to allow access through port 3050.
>
> >At the moment I only have ssh access to the Linux box - theres no keyboard monitor attached.
>
> Hmm...the only client library that matters in this case is libfbclient.so on the server, since your SSH tunnel makes your remote user into a local one. Actually, you haven't mentioned your connection path syntax at all. You need localhost:/opt/firebird/examples/empbuild/employee.fdb (locally) to connect to the database on Superserver.
>
> On connectivity:
>
> 1. The JDBC driver that comes with OpenOffice is for OpenOffice clients. It won't work for connecting your Java apps to Firebird: you'll need the Jaybird JDBC driver for that.
>
> 2. Flamerobin is a C++ application, calling the Firebird API functions natively, using the IBPP wrappers. It doesn't use any Java drivers.
>
> 3. isql is a client application written in C++, also calling the interface routines natively. It doesn't use any intermediate layer like JDBC or ODBC either.
>
> Take care with isql, that you invoke it with the full application path (or with dot-slash from its local directory). A lot of Linux distros install MySQL's isql program as a system executable - so this is the executable you get if you invoke it nude. MySQL's isql *doesn't* connect to Firebird servers. ;-)
>
> ./hb
>