(SAM HERE AGAIN. ORIGINATOR)
SPECIFIC QUESTIONS for anyone:
1. Does the FB1.5.2 install EXE (from the Firebird site) install
Firebird, ready to use on a network, or must I "configure" it so it
will? I'm concerned about the "Default Instance" Status in Services.
2. In a peer-to-peer network, is it necessary for someone to be
logged onto the server, in order for Firebird to be able to respond to
client requests?
TO REVIEW MY ENVIRONMENT AND PROBLEM:(still no fix)
1. The client is using the minimal client install option of the FB
EXE install.
2. The client can ping the "server" (peer-to-peer) at all times.
3. Client requests to FB to connect to the database are only
successful if I run a little Delphi form-based, "connect" app on the
server first and leave it in memory.
4. My database is located in a dir just inside "Program Files" on the
server.

Thx for all of your time and good information, and special thanks to
Helen. (Reviewed your great FB book last year and will be buying it
when it's available in our area.)
Sam

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

> At 02:31 PM 31/03/2005 +0200, Daniel Albuschat wrote:
>
>
> >\\servername\C:\Program Files\Foo.fdb is a *local* path for FB,
>
> No, it is a remote path for a Named Pipes client attaching to a

server that

> is *not* local.
>
> >thus
> >it will use the locally running firebird server to open a database
> >over a network
> >connection (which FB is not even aware of, because it's "hidden" by
> >the filesystem).
>
> No. A FB server cannot open a database over a network connection. The
> database MUST be on physical disk space that is controlled by the

same host

> machine that hosts the FB server.
>
>
> >But I thought you couldn't "share" you Program Files dir?
>
> You don't share directories that contain database files.
>
>
> >servername:C:\Program Files\Foo.fdb is a remote database.
>
> Yes. The same as \\servername\C:\Program Files\Foo.fdb. The

difference

> between the two is that one is the remote path for a client using the
> TCP/IP transport protocol, whereas the other is the remote path for a
> client using the Named Pipes transport protocol. Both are absolute

path

> locations on a server that is remote (physically or logically) from the
> connecting client.
>
> >The FB client
> >library will connect to the FB server running on the machine

"servername"

> >via TCP/IP, and this FB server there will open the (from the

server's point

> >of view) local file C:\Program Files\Foo.fdb.
>
> That is correct, both for Named Pipes and for TCP/IP.
>
>
> >Ther error description sounds more like some domain/OS user issues,

though.

>
> The error description exactly describes what happens when a client

tries to

> open a connection (whether local or remote) using a path that is
> inconsistent with the path that was used by the first client when it
> connected. The part of the path that "matters" here is the path as

seen

> locally by the server machine. Typically, a "good" connection uses the
> correct format
>
> C:\Program Files\Foo.fdb
>
> while the connection that is disallowed uses
>
> C:Program Files\Foo.fdb
>
> (notice the missing backslash after C: -- this is allowed by Windows

and

> forbidden by Firebird if the database file was already opened using the
> correct string.)
>
> ./heLen