Commented by: @AlexPeshkoff

Now password validation is done as soon as possible - right after getting database options from DPB. This makes 'bad password' first exception to happen when connecting to server, at the same time making it save a lot of job in case of wrong credentials passed.

Commented by: @pmakowski

Are you sure it is solved ?

here what I get under Windows with FB2.1.0Beta1

C:\FB21\bin>isql "192.168.1.10:c:\driver\rappin_ch09.pdf"
Statement failed, SQLCODE = -922
file C:\DRIVER\RAPPIN_CH09.PDF is not a valid database
Use CONNECT or CREATE DATABASE to specify a database
SQL> exit;

C:\FB21\bin>isql "192.168.1.10:c:\driver\rappin_ch0.pdf"
Statement failed, SQLCODE = -902
I/O error for file "c:\driver\rappin_ch0.pdf"
-Error while trying to open file
-Le fichier specifie est introuvable.

Commented by: @AlexPeshkoff

Pavel, this all makes sense only for attempts to connect by users, not having valid login/password on server. I noticed there are no -u/-p switches, but may be you have correct pair in environment? Next, since 2.1 beta1 trusted authentication also works for windows - i.e. you will be connected to a database with your windows logon as CURRENT_USER if you have logged to the windows server.

Please try something like:
isql -u QQQ -p ZZZ "192.168.1.10:c:\driver\rappin_ch09.pdf"
to make sure no default attempts to login are done.

Commented by: @pmakowski

Sorry

Seems I made the bad test

If I try to connect from another box, you are right, the bug is solved
and yes I forget the feature that even if I have no correct pair in my environnement, the trusted authentification also works for windows

so I'll close the bug

Commented by: @pmakowski

Q/A test made and ok