Thanks Helen .. now here is where I stand:

Helen asked:
What about NEWSERVER: is it the hostname that the server machine
broadcasts in the network? (Inspect My Computer > Properties > Network
identification > Full computer name).

Full computer name broadcasted by server: newserver

Or is it a mapped drive or sharename? If it is either of these, it will
not work as a hostname that Firebird can connect to....

No it is not.

Helen said:
Yes, you seem to be barking up the wrong tree entirely. Forget about
sharing: you will CAUSE problems by configuring things on shared
filesystems. This should be painted in the sky!!

OK! I removed every share on all the database folders, on firebird install
dir etc.

>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.4881 Firebird
>Super Server on Server PC: Version 1.5.1.4881 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.

Well, does c:\temp actually exist on the server?
YES it does. I removed the share on it.

Earlier, you were talking
of [sic] /windows/system32/temp [not a valid filesystem path on Windows,
anyway...] and below you are talking about similar (with a typo?)
Please ignore above .. sorry!

>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

Here we have another invalid file path; but not a good choice anyway: if
this path exists, it's sitting inside a privileged directory. You were
referring to the typo .. its gone now!

>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.

The owner of the server process in Windows is (by default) the LocalSystem
user, which has huge privileges. In short, unless you installed Fb 1.5 to
be owned by a different user than LocalSystem, permissions won't be the
problem.

Well I uninstalled firebird. Deleted its install directory. I then
reinstalled. I fixed the config file, and the only entry changed is the
tempDirectories. I Checked carefully that I don't have typos.
The temp directory on the hard drive is: c:\temp
And the TempDirectories = c:\temp added to config.

Also, be aware that changes to firebird.conf don't take effect until you
shut down and restart the server.
Yep .. you clearly point that out in your book. So I stopped and restarted
it, even rebooted the server just to make sure.

I also recommend that you double-check your firebird.conf entry for typos.
Only entry is the entry above.

NOW I have the following scenario:
I can log on to database Prax.gdb on the server machine quite fine.
I can doe this as administrator.

Now I go to one of the client PC's on the network running Win 2000.
I logon as the user with administrator priviledges.
I check the hosts file for the entry IPAddress newserver. It is correct, no
typos.
I ping the newserver .. no problems.
I then logon to Prax.gdb , as SYSDBA with the SYSDBA password, using:
\\newserver\c:\prax\prax.gdb
IT WORKS!!!!

Now I log off, and logon, using one of my secretaries logon: no
administrator priviledges.
I ping the newserver .. no problems.
I then logon to Prax.gdb , as SYSDBA with the SYSDBA password, using:
\\newserver\c:\prax\prax.gdb
It won't work ..get error message: "unable to complete network request to
host "newserver". Failed to establish a connection. Logon failure:unknown
user name or bad password"

Now I go to one of the WINXP pc's on the network:
I log on as user with administrator priviledges.
The hosts file is correct.
I ping the newserver .. no problems.
I then logon to Prax.gdb , as SYSDBA with the SYSDBA password, using:
\\newserver\c:\prax\prax.gdb
It won't work ..get error message: "I/O error for file "C:\Prax\PRAX.GDB"
Error while trying to open file Access is denied."

I've tried to give as much info as possible.
Thanks so far ... I hope I can sort it out while the sky is still blue!

Adrian