Subject | Re: [firebird-support] FB 1.5 Log Messages (Many errors) |
---|---|
Author | Helen Borrie |
Post date | 2004-06-25T23:10:27Z |
At 07:08 PM 25/06/2004 +0000, you wrote:
initialise the TCP/IP socket. You'll need to track down what's happening
when that workstation communicates with the server. Could it be that your
network is using dynamic IP addressing? You must have a static IP address
for the server and make sure that clients' connections point to that
address (an entry in the HOSTS file).
Make sure that the workstation isn't already using port 3050 for something
else, e.g. IBConsole or some other tool that has loaded an old client
library and is already communicating through that port.
Another possibility is that the client has the wrong version of the client
library. At least you should check it...
list of Winsock error codes and brief descriptions.
But as for finding information, network errors are notoriously hard to
track down. The error that the network reports isn't necessary the one
that started the chain of disaster.
/heLen
>We have started installing FB 1.5 lately and one of our client'sIt's a TCP/IP configuration error - Winsock interprets it as a failure to
>server has frozen twice in the last 3 weeks. We had twice the same
>error sequence in the log file. All other installs went well so far
>(and in our labs too),
initialise the TCP/IP socket. You'll need to track down what's happening
when that workstation communicates with the server. Could it be that your
network is using dynamic IP addressing? You must have a static IP address
for the server and make sure that clients' connections point to that
address (an entry in the HOSTS file).
Make sure that the workstation isn't already using port 3050 for something
else, e.g. IBConsole or some other tool that has loaded an old client
library and is already communicating through that port.
Another possibility is that the client has the wrong version of the client
library. At least you should check it...
>Where can I find information about these errors ???http://www.uwm.edu/IMT/Computing/sasdoc8/sashtml/odbc/z0928595.htm is a
list of Winsock error codes and brief descriptions.
But as for finding information, network errors are notoriously hard to
track down. The error that the network reports isn't necessary the one
that started the chain of disaster.
/heLen