At 12:56 PM 9/02/2005 +0200, you wrote:

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

Definitely try this again, since (given that you know the sysdba user
exists and you have already used the password). Has to be a typo to give
this error...although if you have a rogue setup in the client, with a
vestigial interbase.msg file there, it could just simply be returning a
wrong message, where the error really is the one described below.

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

This time, you got past login, i.e. the server found security.fdb and you
gave the right password. Now you are getting the message that file access
is denied.

Right, now, first thing to do on any XP system is to RENAME your database
so that it doesn't have ".gdb" as its suffix. This has been documented to
death, across two releases and about a gazillion times across the support
lists. It could simply be that access is being denied because there is no
other user already logged in who has already copped having to wait until
the abominable SystemRestore has finished making an image copy of the
database file and releases the file lock so that the database server can
obtain it.

Next, is this XP Home, by any chance? I note that you are continuing to try
to use Named Pipes as your protocol. Now, if this is XP Home, you will be
allowed at most one remote Named Pipes connection. If it is XP Pro, the
limit is 10, which will quickly get used up by shares and such.

Do you understand that ping tests whether the TCP/IP connection works, and
that the HOSTS file identifies IP addresses, which are TCP/IP nodes? All
you know from a successful ping is that the TCP/IP link works. It doesn't
tell you anything about Named Pipes.

Some days ago, one (or was it two) people advised you to use
TCP/IP. TCP/IP doesn't have these limitations. Please try the TCP/IP
protocol for your database connection and report back. Rename the database
file, then copy and paste the following into the client's connection string:

newserver:c:\prax\Prax.FDB

./heLen