Subject Re: [firebird-support] TCP/IP problem with 2 networkcards in the server
Author Helen Borrie
At 08:09 AM 23/09/2004 +0000, you wrote:

>We are experiencing problems with Firebird when there are 2
>networkcards in the server. Sometimes it's wortking well, and
>sometimes after rebooting Firebird is trying to communicate through
>the wrong networkcard. Then after a few times rebooting, it's ok
>again. Is there a way to tell Firebird that it has to work always
>though networkcard A instead of card B ?
>Many thanks in advance,

With firebird 1.5, you can configure a single bind address for network
connections to the server. That will prevent anyone trying to connect to
any other node address for a Firebird connection. See RemoteBindAddress in

With either 1.0 or 1.5, configure the NIC you want to be used in the
Firebird users' LAN. On Windows, do this via Settings | Network and Dialup
Connections and pick the "Local Area Network" applet.

Once it's open, highlight Internet Protocol (TCP/IP) and then click
Properties. (Don't be confused here: this doesn't impact your Internet
settings at all!!)

Set "Use the Following IP Address" and set it up with an internal IP
address - anything you like - I've got my LAN set up with IP addresses in
the range 10.12.13.nnn, being easy to remember when I want to assign a new
address. Set the mask to ( (it's enough if you have 255 or
fewer nodes on the network; otherwise you'll want to extend it out a
level, using for the mask and make use of variable numbers at
both levels). Make sure that Obtain DNS Server Address automatically is
NOT selected.

Next, click the Advanced button, click Add... and enter the IP address you
have chosen for the card. Click out with OK all through and you're done.

If you're not on Windows, look up the network admin docs for your
particular Linux flavour for how to configure the NIC for the LAN. The
procedure is pretty similar to what you do on Windows.