--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:

>
> > > If you need a client named gds32.dll and it has to be in the

machines

> > system32 directory, then make sure those two options are checked.
> >
> >I missed this the first time, but that just made the ODBC driver
> >crazy. It wasn't causing the unavailable database error.
>
> To make sure you have the right client, you should check the

version string

> in the property editor of the library that your driver is

accessing. If it

> doesn't match the version string of fbserver.exe (in the build

number at

> least) then there's a good chance it belongs to something else. Do

I need

> to say that remote clients should access the database from the

correct

> client library version as well?
>
>
> Since it's unclear (from another message) whether it was the

MACHINE or the

> SOFTWARE that was moved, it's kinda like crystal ball gazing to try

to

> identify your problem. For example, if you moved *the software*

you could

> well be looking at a firewall problem....if it was just the machine

that

> was moved, not the software, and connection worked before...then

does the

> machine still have the same node address? What's the environment -

is

> there a terminal server in the picture?
>
>

from rereading this part of the message, and your other response, I
realize that I have not made clear: I don't have the client side of
this setup working yet. I have been using isql.exe, cause that's
what the Quick Start recommends as the first step check, from the
machine and directory where the database (and software) is actually
installed.

When I follow the syntax exactly as shown in the Quick Start Guide, I
get the unavailable database message. [originally, this worked]

when I did the telnet check, I did it from the same machine where the
databases and software are installed, as well as a remote computer.

Ann Cecil