David,

> > Exactly - this is one of the changes that IB needs, the ability to
> > define the IP port used by the client to allow defined routing
> > through a firewall.

[snip]

> InterBase has the ability to communicate over any port -- but it's
> certainly isn't well documented.
>
> Client side:
> Connection string "server:/database.gdb" is converted into
> "server/gds_db:/database.gdb". gds_db is looked up on the
> client side as (4050? I honestly can't remember!).
>
> If the client changes the connection string to
> server/protocol#:/database.gdb" -- then it uses that protocol #.
> You can either put a symbolic name here (which is looked up on
> the client again) or a decimal number.

Thank you very very much! I got it to work. I could NOT use decimal port
numbers, but I simply added my own named entries into the Services file and
wallah, I could connect through a port routing definition on my firewall (I
didn't even have to reboot which is pretty amazing under NT4 :-)

Now I can sit down and begin routing to the various servers that I want to
remotely support!

Thanks again.

Geoff Worboys
Telesis Computing
gworboys@...