| Subject | Re: [firebird-support] Firebird 1.5 Log in error |
|---|---|
| Author | Helen Borrie |
| Post date | 2010-05-04T01:34:45Z |
At 09:52 AM 4/05/2010, you wrote:
"They did recently upgrade their firewall..."
Firewall[s] on Windows clients? Or the firewall on the Linux server? Upgraded to a new version of the old firewall software? Or installed new firewall software? In the latter case the likelihood that working firewall rules have been blown is much higher.
The fact that you can telnet in to the server at least says it's unlikely to be a Linux issue.
What error message[s] is/are being returned to the client applications when the connection failures occur?
"Not sure [turning off the firewall is] an option. I'm a very small fish and my customer is a very large organization."
Large enough that they have some sysadmin on site who is allowed to arbitrarily break the networked application environment through faulty change control? You didn't cause this problem: they did. They have to be involved in the forensics to find and rectify their mistake.
./hb
>A customer of ours is using using an application we wrote in Delphi to remotely access data in a Firebird 1.5 database on our linux server. All three Win XP and/or Win 7 machines at the remote location suddenly are not able to connect. We used telnet to make sure port 3050 was open. They did recently upgrade their firewall, however, my knowledge of that is severely limited.A Windows network error occurring in the firebird.log at the Linux server?
>
>The error messages in the firebird log are:
>
>"INET/inet_error: read errno = 10053"
"They did recently upgrade their firewall..."
Firewall[s] on Windows clients? Or the firewall on the Linux server? Upgraded to a new version of the old firewall software? Or installed new firewall software? In the latter case the likelihood that working firewall rules have been blown is much higher.
The fact that you can telnet in to the server at least says it's unlikely to be a Linux issue.
What error message[s] is/are being returned to the client applications when the connection failures occur?
>andSuggests it could be some kind of a timing or network protocol issue at the clients.
>"INET/inet_error: receive in try_connect errno = 203"
>I saw some traffic on this issue related to simultaneous logins. I would guess that we have less than 4 logins at any one time.I don't know what "issue" you would be referring to "related to simultaneous logins". Firebird is designed for simultaneous logins. It doesn't suddenly break of its own accord.
>Does anyone know how to resolve this?Not until enough forensics are done to discover the likely cause. You have written:
"Not sure [turning off the firewall is] an option. I'm a very small fish and my customer is a very large organization."
Large enough that they have some sysadmin on site who is allowed to arbitrarily break the networked application environment through faulty change control? You didn't cause this problem: they did. They have to be involved in the forensics to find and rectify their mistake.
./hb