| Subject | Re: [firebird-support] Linux connections |
|---|---|
| Author | Marcin Bury |
| Post date | 2007-10-15T18:21:32Z |
Lester,
I can't directly find out what OS is running on workstations 'having
problems' connecting to Firebird CS on Linux box.
If this OS is Windows XP with recent updates applied I have some solution
for you.
Xinetd service on Linux box requires that workstation trying to connect to
'introduce' itself. This operation requires that port 113 should be open on
WinXP workstation. One of the recent MS so called security patches closes
this port by default.
The are two way of solving this issue:
1. There is some parameters in xinetd configuration that is responsible for
the amount of time that linux box waits for the 'introduction' and this time
can be reduced to some minimum
2. Simply open port 113 on Win XP workstation (firewall settings)
A few weeks ago we setup a new linux box in customer office. Since the
amount of concurrent connections often reaches 100 and more we decided to
try Classic Firebird. Then we expirenced huge delay in connecting to the
database - even 60 second. After that application works like a charm and
users started to say 'woooow'. Everything would be great but this delay...
We have noticed that this delay occured only on WinXP workstations, we have
some Win2K boxes and even one or two Win98 ;-). These workstations were
connecting to the Firebird immiediately.
My friend, who is linux administrator in this company, did some searching in
Internet and found that xinetd requires some comunication through port 113
before establishing connection bewteen Firebird client and server. Opening
port 113 in firewall setting on WinXP solved the issue.
Lester, if you need further details - let me know - I ask my friend to
provide them.
HTH
Marcin
PS. Sorry for my English not being as accurate as it should be...
I can't directly find out what OS is running on workstations 'having
problems' connecting to Firebird CS on Linux box.
If this OS is Windows XP with recent updates applied I have some solution
for you.
Xinetd service on Linux box requires that workstation trying to connect to
'introduce' itself. This operation requires that port 113 should be open on
WinXP workstation. One of the recent MS so called security patches closes
this port by default.
The are two way of solving this issue:
1. There is some parameters in xinetd configuration that is responsible for
the amount of time that linux box waits for the 'introduction' and this time
can be reduced to some minimum
2. Simply open port 113 on Win XP workstation (firewall settings)
A few weeks ago we setup a new linux box in customer office. Since the
amount of concurrent connections often reaches 100 and more we decided to
try Classic Firebird. Then we expirenced huge delay in connecting to the
database - even 60 second. After that application works like a charm and
users started to say 'woooow'. Everything would be great but this delay...
We have noticed that this delay occured only on WinXP workstations, we have
some Win2K boxes and even one or two Win98 ;-). These workstations were
connecting to the Firebird immiediately.
My friend, who is linux administrator in this company, did some searching in
Internet and found that xinetd requires some comunication through port 113
before establishing connection bewteen Firebird client and server. Opening
port 113 in firewall setting on WinXP solved the issue.
Lester, if you need further details - let me know - I ask my friend to
provide them.
HTH
Marcin
PS. Sorry for my English not being as accurate as it should be...
----- Original Message -----
From: "Steve Wiser" <steve@...>
To: <firebird-support@yahoogroups.com>
Sent: Monday, October 15, 2007 7:24 PM
Subject: Re: [firebird-support] Linux connections
>A long time ago we had a problem where the Windows desktops could ping
> nicely to the linux servers, but when making a connection it would sit
> there for 30 seconds or more before finally connecting. It turns out
> that the desktops were using DHCP, but the DNS settings were
> hard-coded. At the time (Win98) Windows really wanted the DNS settings
> to come over with the IP Address for DHCP, but the problem only surfaced
> during connections to Firebird (well, Interbase at that time). We made
> the DNS section DHCP as well and all of the connection issues went away.
>
> I would assume that this wouldn't happen with Windows 2000, XP or Vista
> since I think they have a new TCP/IP system.
>
> -steve
>
> Lester Caine wrote:
>>
>> John vd Waeter wrote:
>> >> The problem I have is where do I learn about these sorts of problems.
>> >> Accessing Firebird on the Windows box on this site is fine -
>> accessing the
>> >> Linux box is simply very slow :(
>> >>
>> >
>> > Hmm, DNS?
>> >
>> > How about the difference in pinging both servers?
>>
>> Fixed hosts tables on all three machines now - but made no difference.
>> All pings are sub 1ms
>> Access to Apache on port 80 is not a problem, and PHP's access to the
>> Firebird
>> server IN Linux box is not a problem. Also TightVNC into the box seems
>> fine.
>> It is ONLY the 3050 port and Firebird that seems to have the problem
>> which is
>> what I can't explain :(
>>
>> --
>> Lester Caine - G8HFL
>> -----------------------------
>> Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
>> <http://home.lsces.co.uk/lsces/wiki/?page=contact>
>> L.S.Caine Electronic Services - http://home.lsces.co.uk
>> <http://home.lsces.co.uk>
>> MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
>> <http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/>
>> Firebird - http://www.firebirdsql.org/index.php
>> <http://www.firebirdsql.org/index.php>
>>
>>
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://www.firebirdsql.org and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>