At 06:37 AM 27/12/2004 -0500, you wrote:

>Same here. This is a really irritationg issue. I have tried EVERY fix
>found on the lists/archives/google to no avail. The problem occurs under
>Win2000 and XP. This is regardless of connection type. Even connecting
>remote to a linux server (dual opteron 2G+ RAM) the windows side takes
>FOREVER. Doing it locally also makes no difference. This is on machines
>with 2.2G+ processors (both intel and AMD), 1G+ RAM, 250G+ Storage.

Well, you have to suspect the way your systems are configured (network
cards, firewall, etc.) I have a mix of servers on the LAN here. The
Windows ones are Win2000, the Linux ones are RedHat 8 and Mandrake 9.1
respectively. All machines are single CPU, ranging from 1.3 GHz AMD down
to Intel ~450 MHz. All of the hard disks except one are 5400 IDE (though I
don't recommend slow disks!!) Mea culpa, I don't think I've ever defragged
any of them. I don't get connection delays with any of them on the first
connection, either as servers or clients.

I use TCP/IP for all Firebird connections and I additionally have an Apache
server running on the daggiest server of them all.

I use strictly static host name setups for all machines - hostname mapped
directly to the IP address that the NIC is broadcasting from its setup,
subnetmask configured to 255.255.255.0 in all cases.

I'm also ultra-pertickler about ensuring the clients are using the right
client library.

Have you studied the Quick Start Guide?

>I even tried using a RAID locally with 2000 server to no avail. I've
>tried multiprocessors, Gigabit Networking... you name it, I've tried it.
>
>It seems like it's loading indices but I can't seem to track it down.

Nope. The engine loads index pages into the cache as and when required for
operations.

Are you using some third-party tool for these connections? Do you have the
same delays when using isql?

> > I have the same thing.
> >
> > The first connection is slow for me on my pentium with the IDE disk
> > (WindowsXP/Superserver). When I try to connect the hard disk works
> > constantly about 2 minutes and then the first connection is
> > established.

You have to suspect SystemRestore here for XP. When the first connection
opens the server exclusively locks the file. SR sneaks in when this
fileopen request occurs and image-copies the file, meaning the server has
to wait until it can get its exclusive lock.

./hb