A few month ago i had to deal with a similar issue, and found out the
Symantec endpoint antivirus was the problem cause.

Elkins



De: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] En nombre de jsbriantes
Enviado el: miércoles, 19 de mayo de 2010 02:57 a.m.
Para: firebird-support@yahoogroups.com
Asunto: [firebird-support] Re: Firebird 1.5.6 and Windows Server 2008





Hello. Thanks for your answers.
Yes, I know this change for Firebird 2.x (IPC vs XNET).
With Firebird 2.x it works good, with string connection <servername>:<server
path to DB>. Clients, in the LAN, can connect without problem using port
3050 (firewall opened), using the same string.

I uninstall 2.x and install 1.5.6 and the same application cann't connect
(with the same connection string).

Using port 3050 (opened on firewall). "Firebird.conf" file parameters
reviewed.
Using connect string (I always use this pattern):
<server name>:<local server path to DB>

I used gsec in the same server (on a cmd window). As Helen says, I'll test
gsec with "-database". But "gsec" was only a test. My problem is with client
connections.

Can I check something more?

Thanks.





[Non-text portions of this message have been removed]