I have two machines at a client's shop. Call them A and B.

A runs my application and Firebird, and works just dandy. I have
defined an alias (AXPDATA) which appl. inst. A uses when it
connects. The application runs and does what it's supposed to do.
My application always uses TCP/IP.

B is intended to run my application and connect to Firebird on A. I
can ping A from B. I can telnet to port 3050 on A from B. isql
connects to the database using a node name of A and a DB name of
AXPDATA and shows me stuff that's in the database.

When my application on B tries connect to A:AXPDATA, it gets ISC
Error code 335544375, Unavailable Database.

The fbclient.dll on A matches the Firebird (2.0.1) on B. I know
this because my application's install kit was used to set up both
machines and my install kit contains and invokes the 2.0.1 Firebird
kit.

Firebird on B has been turned off.

A and B are running Windows XP professional that's been fully
updated.

At other sites, the same version of the application and of FB
converse across the network just fine. I've done this before with a
different application and the same version of FB, etc. The only
trouble I've ever had was forgetting about Windows Firewall (off in
this case) and that would've prevented isql and telnet from working.

I'm thinking I'll try setting it up the other way (FB on B, client
on A) just to see if this matters and after that maybe Ethereal to
see what, exactly, is happening across the network, but I'll have to
make a trip back to the Customer's place to do that. Does anyone
have any other, hopefully better suggestions?

Michael D. Spence
Mockingbird Data Systems, Inc.