On March 6, 2003 03:08 am, duilio_fos wrote:

> I connected several times to a Windows server.
>
> Now the database is on a Linux box, that is visible from the client
> machine with the IP address x.x.x.x
>
> I tried to connect using the following settings for WISQL :
>
> remote server: checked
> server: x.x.x.x
> database: c:\test.gdb /* this line is surely wrong */
> username: SYSDBA
> password: masterkey

Your right c:\test.gdb is wrong, under Unix (and it's clones) there is no
such thing as a separate drive, so there are no drive names (like c:),
instead everything is under a single file system. So for example if you keep
the databases in /home/firebird. Database should read /home/firebird/test.gdb

Note that Windows uses the \ to seperate directories, unix uses the / to
separate directories.

> When I try to connect, I get the error message:
>
> statement failed, SQL code -902
>
> "Unable to complete network request to host "207.44.210.19".
> -Failed to locate host machine.
> -The specified name was not found in the hosts file or Domain Name
> Services.
> "

Try to ping 207.44.210.19 and see if it is able to, if not then you need to
modify the hosts file on the Windows machine to include the Linux server.
Second part of this, and many people forget, ping the windows machine from
the Linux one, and make sure that it can also be found. If you have less
then 30 - 40 machines then you can probably create 1 hosts file and copy it
to the others. More then 40 machines and it's probably worth it to set up a
local DNS server. More then 50 and your probably best to set up DHCP as well.