Sorry for the lack of clarity - this is two connections deliberately being
made from the same app (it's the way way the app is written) - the second
gets an error message (connection refused or unable to complete request -
I'll have to check on site) but connects. It was only on the initial
release of Windows Server 2003 and, iirc, is/was a MS TCP/IP stack issue
that was patched fairly promptly. It doesn't happen from all client PCs -
and seems a nuisance only - but I'd rather fix it (it's not a good look).

There was a link to the MS KB in the post, I'm sure, around the end of
2005 - but I can't find it. My memory is also that it was a "known issue"
at the time - and Helen posted the link, again can't guarantee - was
hoping for an "oh yeah - that was ..." insight - but may have to do the
hard yards yet.

Max

> --- In firebird-support@yahoogroups.com, "Max Renshaw-Fox" <maxrf@...>
> wrote:
>>
>> We have a client with the above problem.
>
> More details please?
>
> Additional connections can occur if you have accidentally left
> guardian installed with Classic Server.
>
> Adam
>
>
>
>