See previous thread: error upon connecting to database from remote client.

Well I tried finding the solution. First by re-reading relevant chapters in
The Firebird Book by Helen.
Chapters 5, 6,7. Then appendix II pages 915 - 921

The only way I could get it to work, was to share the Firebird folder over
the network.
Then I noticed it worked, and that an entry was placed in the firebird.txt
file, showing a connect from a client had occurred. I think this is an error
log.
When this folder is not shared, then the client does not have permission to
write to this file.

Helen if you are out there: you do mention in your book that there can be
problems with permissions on NTFS drives.
You don't' however anywhere recommend that the (and these are the files that
required sharing) following be shared:
Folder in which the database resides.
Folder that Firebird is installed into.
Temp folder in windows/system32/temp.

Surely none of these folders need to be shared on the network, nor do users
need to have permission to write to them. I would think that the SuperServer
residing on the host machine, should be albe to handle any folder on the
same server .. in my case the same hard disk, and that clients should not
have share access to the default install directory of Firebird, nor to the
database directory for that matter. What prevents them from just copying the
database, or even worse just deleting it then.

There must be more to this, and I'm really hoping for an answer.

Server: Win XP Professional (Only because Boxed Suse Linux 9.2 would not run
on the machine due to SATA problem .. have to wait for a new kernel that
supports latest Intel motherboards.
Clients: Mix of Win 2000, Win XP Professional.
On all clients Firebird Client installed version 1.5.1.4880
Firebird Super Server on Server PC: Version 1.5.1.4880
Static IP addresses, due to a wireless router in the network that requires
specific address range for internet access.
Hosts file configured on each machine to contain localhost ip, and NEWSERVER
ip
Config default, except that added c:\temp 500000000 entry hoping this was
the problem.
Gbak database transportable, then Gbak -c on the server machine.
Now that all the folders mentioned below are shared across the network, with
write permissions it all works:
C:\Prax Database: C:\Prax\Prax.gdb
C:\Program Files\Firebird Default install directory C:\Program
Files\Firebird\Firebird_1_5
C:\Temp
C:\Windows\Systme32\Temp

Perhaps the answer lies in the following paragraph from Helen's book:
"Does the Owner of the Server Process Have Sufficient Permissions To Open
Files?" pg 918
Helen .. how do I give the SERVER these write permissions on the same drive.

This would then solve me having to share any of the abovementioned folders,
dramatically improving security.

Thanks in advance .. Adrian