Hello,

just a follow-up to my connectin problems with Classic. See below ...

> I encounter weird connection problems with Classic whereas the same
> connection string works fine with Superserver. This happens for both
> Firebird 1.5.3 and Firebird 2.0.0 on the same machine with Windows XP
> Prof. SP2.
>
> For example, I've an alias defined "employee.fdb". With Superserver I
> can connect with isql by using a connection string of
> localhost:employee.fdb. The same fails under Classic with the following
> error messages:
>
> - Firebird 1.5.3
>
> c:\Programme\Firebird\Firebird_153_3050\bin>isql
> Use CONNECT or CREATE DATABASE to specify a database
> SQL> connect localhost:employee.fdb user sysdba password masterkey;
> Statement failed, SQLCODE = -902
>
> Unable to complete network request to host "localhost".
> -Failed to establish a connection.
> SQL>
>
> - Firebird 2.0.0
>
> c:\Programme\Firebird\Firebird_200_3050\bin>isql
> Use CONNECT or CREATE DATABASE to specify a database
> SQL>
> SQL> connect localhost:employee.fdb user sysdba password masterkey;
> Statement failed, SQLCODE = -923
> connection rejected by remote interface
> SQL>
>
>
> As said, the same connection string works fine with Superserver. Tests
> have been made with Firewall (ZoneAlarm) enabled and disabled. Doesn't
> matter.

I've identified Panda Antivirus 2007 as the cause for the connection
problems. Even with the included Firewall deinstalled, I couldn't
establish a connectin via Classic. Removed Panda Antivirus 2007 and
installed an other antivirus product, everything is fine now.

In hope this is useful for someone.

> As I want to use Classic on my new Core 2 Duo laptop, I would appreciate
> any help.

--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com