At 2001-03-08 12:18 +1300, you wrote:

>A few days ago, Brad Pepers had problems connecting to Windows databases
>from Linux ISQL. He later said that it was a VMWare issue. Today I had
>the same problem. It wasn't a VMWare issue. Here are the steps I went
>through to solve it:
>
> >>> $ isql 192.168.1.1:/x:/Databases/XxxxxxCopyOfHost.gdb
> >>> Statement failed, SQLCODE = -902
> >>>
> >>> Unable to complete network request to host "backupserver".
> >>> -Failed to locate host machine.
> >>> -Undefined service x/tcp.
> >>> Use CONNECT or CREATE DATABASE to specify a database
> >>> SQL>
>
>Right, so it can't connect, but it managed to translate the IP address

I don't have a Windows InterBase server running any more, but, unless
memory fails, I used to use strings of the form:

"machinename:c:\mypath\mydb.gdb"

I also used to make use of InterBase's idea of a home drive (the drive it
looks at by default), so that I could use the same connect string as to a
Linux machine:

"machinename:/var/databases/mydb.gdb"

Assuming InterBase is installed on C: drive, that would map to the database
at "c:\var\databases\mydb.gdb". This won't work for you, though, because no
doubt you don't have IB installed on drive X.

Give the first one a try!

Regards

David Trudgett