I am curious: did you even try upgrading to Firebird 2.0.5 as was suggested earlier in this topic?

A lot of the suggestions in this topic have been variations on cargo-cult; the suggestion of upgrading to Firebird 2.0.5 was one of the few that actually has merit in my opinion.

Mark

> Helen:
>
> First of all, thanks for your answer.
>
> The users form the other building connect to the server (the PC with
> Windows
> XP which has the EXE of the application and the databases .FDB files)
> using
> Terminal Server. Then they run the EXE.
>
> Each time a user starts the application, he connects to 6 databases.
> That´s
> why when the 11th user starts the application, he exceeds the connections
> limit of 64.
>
> Yes, they have XP SP3. I googled what you said but I found nothing about a
> TCP/IP to < 64 concurrent connections limit. What I found is that there is
> a
> limit of 10 concurrent "half connections", that is simultaneous connection
> attempts and apparently this is, as you said, to protect against worm
> virus.
>
> I finally don´t know if the cause is really Windows XP (or XP SP3) or
> NOD32
> or both, but I follow Vlad´s suggestion of not using TCP/IP connections
> and
> it seems to be working. What I did is not to use HOST:path and instead I
> use
> \\HOST\path. For Terminal server I had to use \\127.0.0.1\\path because
> \\LOCALHOST\path doesn´t work. BTW does anybody knows why this doesn´t
> work?
>
> And now I have a question:
>
> Is there any difference in using HOST:path against using \\HOST\path in
> performance, security, etc.?
>
> Thanks to everybody!

--
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01