>
> Hi Alexandre,
>
> I've tried and it seems impossible to connect through any other ports
> than 3050. That is,
>
> ssh -L 3050:localhost:22 <remote host>
> isql localhost/3050:<remote database>
>
> It seems that the localhost port 3050 is critical for connection, it
> seems to be able to work with any other unused ports on the remote
> host. For example, the following works:
>
> ssh -L 3050:localhost:20000 <remote host>
> isql localhost/3050:<remote database>
>
> But this won't work:
>
> ssh -L 3000:localhost:22 <remote host>
> isql localhost/3000:<remote database>
>
> Cheers
> Maurice

Hi Alexandre,

I've actually found another issue.

Scenario 1: I connect to a remote server using SSH and performs port
forwarding at the same time using "ssh -L 3050:localhost:20000 <remote
host>". Then in that login shell, I do a "isql <database> -u <user> -p
<password>".

Scenario 2: I connect to a remote server using SSH and performs port
forwarding at the same time using "ssh -L 3050:localhost:20000 <remote
host>". Then on local machine, I attempt to connect to remote database
using the SSH tunnel by "isql localhost/3050:<database> -u <user> -p
<password>".

Both scenarios allow me to connect to the remote database, no errors
so far, and I can see the tables using "show tables;" command. The
problem is this, when I issue commands as "select count(*) from <a
table>;",
Scenario 1 reports 6000, which is correct but
Scenario 2 reports 0, which is wrong.

I have no feel for what exactly is wrong... Somehow in both cases, the
metadata is correct but the data in the database is not connected...

Any reasons?

Cheers
Maurice