At 01:57 AM 29/05/2004 +0000, you wrote:

>When I look at taskmgr on the w2k box I see a single fbserver and
>fbguard process running while I have 5 open JDBC connections to it
>from a Java process running on a separate machine. All this implies to
>me, newbie that I am, that it is the superserver architecture.
>
>How else may I tell if I have the classic version installed?

You are running Superserver. The Classic server's name is fb_inet_server.

The next thing to look at is the connection string being passed by the
application. Remote clients can't use localhost: (since this is the local
loopback server that applies only to the local machine, including the
client). They must use either the server's IP address or (safer in dynamic
tcp setups) a server name resolved by implanting it statically in the HOSTS
files of both client and server.

A tcp/ip connection string to a Windows server looks like this:

servername:D:\path\to\database.file
or
nnn.nnn.nnn.nnn:D:\path\to\database.file

Configuring the HOSTS file is safer than using the IP address if your
tcp/ip server is assigning IP addresses dynamically. If there is a HOSTS
entry, that IP address won't be assigned to any other node and also the
node that has that IP address gets to keep it.

On Windows it's also a very good idea to screw down the IP address in both
your TCP/IP service properties and in the property sheet of the NIC. Also
make sure that the IP mask is correct in your tcp/ip confguration, and is
consistent across all nodes in the network.

/heLen