At 12:19 AM 3/2/2001 +1000, matt wrote:

>the interbase log (on the server) is filling up with the following
>error
>
>SERVER (Server) Wed Feb 28 09:24:38 2000
>WNET/wnet_error: ReadFile end-of-file errno = 109
>
>the message below (from borland.com communities)
>states its only a netbui problem.... i'm tearing my hair out here
>
>trickier than i thought.... client has a 4 pc network
>all running NT4 workstation with SP6 & IE5
>TCP-IP is the ONLY protocol installed and bound to nics...

One thought that comes to mind is the connect string. InterBase
decides what protocol to use based on the punctuation of the
connect string. I'm appending a message from Andy Canfield
sent to another list in answer to a different question, but
appropriate enough -



Regards,

Ann
www.ibphoenix.com
We have answers.




X-POP3-Rcpt: harrison@linux
Return-Path: interbase-admin@...
Received: from linux.mers.com ([204.225.98.10]) by linux (8.6.12/8.6.9)
with ESMTP id KAA32190 for <HARRISON@...>; Fri, 1 Dec 2000
10:19:27 -0500
Received: (from mailman@localhost)
by linux.mers.com (8.9.3/8.9.3) id QAA27030;
Mon, 4 Dec 2000 16:44:20 -0500
X-Authentication-Warning: linux.mers.com: mailman set sender to
interbase-admin@... using -f
Received: from adamsint.com (elara.webvis.net [202.157.134.2])
by linux.mers.com (8.9.3/8.9.3) with SMTP id XAA12401
for <interbase@...>; Sun, 3 Dec 2000 23:52:33 -0500
Received: from think6 ([203.146.121.133]) by adamsint.com ; Mon, 04 Dec
2000 11:50:01 +0800 SGT
Message-ID: <006501c05da5$7a72ba20$9cdbfea9@think6>
From: "Andy Canfield" <andy@...>
To: <interbase@...>
References: <909n22$b4v$1@...>
Subject: Re: Setting Up A Server Questions
Date: Mon, 4 Dec 2000 10:49:38 +0700
MIME-Version: 1.0
Content-Type: text/plain;
charset="Windows-1252"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by linux.mers.com id
XAA12402
Sender: interbase-admin@...
Errors-To: interbase-admin@...
X-BeenThere: interbase@...
X-Mailman-Version: 2.0beta5
Precedence: bulk
Reply-To: interbase@...
List-Id: InterBase ListServer <interbase.mers.com>

> I am in the process of learning how to do use Interbase and setup a remote
> server. I setup a simple network with 2 machines both using Win 98 and
> TCP/IP to connect them. I opened IB Console to register a server and it
> asked for the server name. What would the server name be? I used the name
> of my computer, but it didn't like that.

I use Win98 also. Open Network Neighborhood. The name you have to use for
the server is the name shown there for the other computer. Server name is
computer name. So the TCP/IP connection string is:
COMPUTERNAME:DatabaseFileName

This implies that you can have only one database server running on a given
computer.

One thing that confused me initially is that the server name ( computer
name ) is used to contact the server which is a program running on that
computer, and then the DatabaseFileName is relative to that server program;
i.e. a local name on the server computer. The database need not be in a
shared directory; for security reasons it probably should NOT be shared.

Interbase databases traditionally have the extension ".gdb" but that is
optional; I don't use any extension and I haven't yet run into any problem.

If you don't specify any directory name the default location is C:\Program
Files\Interbase which IMHO is the wrong place to store data. I put all my
databases into C:\Database so that my connection string looks like:
COMPUTERNAME:\Database\Filename

One nice thing about Interbase is that in the connection string you can use
forward or backward slashes interchangably.

I would not recommend trying to put the database on another drive;
desirable as this is for performance / security / defragmentation reasons
the colon after the drive letter will probably confuse some software; e.g.
SERVER1:D:\Database\MyData.gdb <== NOT A GOOD IDEA

Be careful of the capitalization. Because Windows doesn't care about it,
you can use 'SERVER1:filename' in one place and 'SERVER1:FileName' in
another place and 'SERVER1:FILENAME' in another piece of code. This will
work fine until you move the database to a UNIX server, and then things
break. If the upper/lower case of your connection string exactly matches
the upper/lower case of the actual file name then you should be OK anywhere.

The connection string as above:
servername colon [ directoryname slash ] filename
tells Interbase to use TCP/IP. Unfortunately Windows 98 wants to send any
TCP/IP request to the Internet and you may get the Dial-Up Connection
popping up all the time. I'm working on how to avoid that. The standard way
in Windows to refer to files on a file server is:
slash slash computername slash sharename slash [ directoryname slash ]
filename
If you use something similar for a connection string:
slash slash servername slash [ directoryname slash ] filename
then Interbase will attempt to use NetBUEI. I haven't tried that yet. If
you try it, notice that there is no sharename involved; as with TCP/IP, the
database directory name is local to the server computer, not a published
share name.

---------------------------------------------------------
The opinions expressed herein are not the opinions of God
unless signed by her.



_______________________________________________
Interbase mailing list
Interbase@...
http://mers.com/mailman/listinfo/interbase