| Subject | Re: [firebird-support] remote access of firebird database |
|---|---|
| Author | Helen Borrie |
| Post date | 2007-06-18T01:30:22Z |
At 07:18 AM 18/06/2007, you wrote:
using the IP address, you need the *static* IP address of the host
machine and there has to be a NAT entry in the router that permits
access from the WWW. The firewall of the target LAN will also need
to allow it.
If the target LAN is using DHCP then the IP address is no good. You
need the domain name. If you need to specify the port in the
connection string, the format is
mydomain.com/3050:c:\mydata\resource.gdb
machine". Clients connect remotely to the server, whether the host
machine is sitting on the next desk or is located half-way across the
world. But a direct TCP/IP connection across the Internet is not
suitable for 2-tier client server! It is both slow and
insecure. Passing the database path "in clear" is not nice
either. (Use an alias!)
Many people use SSL tunneling for occasional, low-octane WAN access
for 2-tier clients - Zebedee is a popular free software for this.
The preferred way to do WAN is a 3-tier arrangement, whereby
applications execute on the server in response to requests from
browser-based clients (simplest) or specialised distributed networking layers.
In between 2- and 3-tier, you can use remote desktop if the entire
system is homogeneously Windows. If the client machines are Win2K or
higher you can have them connect to the LAN as Windows remote desktop
clients and run their client application in the remote network
(remotely for them, locally on the LAN).
There are other virtual network options, too, e.g. VNC at the
low-cost end; and many more..
./heLen
>When I access firebird over my LAN I use:The router is not the host machine. If you are going to connect
>192.168.1.201:c:\mydata\resource.gdb
>
>What is the proper way to access firebird over a WAN. For instance,
>the firebird server is in NYC and I want to access the database from a
>pc in San Francisco. The ip address of the New York router is
>162.83.141.186.
>
>I tried:
>162.38.141.186:3050\c:\mydata\resource.gdb and
>162.38.141.186:c:\mydata\resource.gdb, neither of which work.
using the IP address, you need the *static* IP address of the host
machine and there has to be a NAT entry in the router that permits
access from the WWW. The firewall of the target LAN will also need
to allow it.
If the target LAN is using DHCP then the IP address is no good. You
need the domain name. If you need to specify the port in the
connection string, the format is
mydomain.com/3050:c:\mydata\resource.gdb
>What is the preferred way to address the firebird database on a"Remote" is relative. It means "any host machine that is not my
>remoter server.
machine". Clients connect remotely to the server, whether the host
machine is sitting on the next desk or is located half-way across the
world. But a direct TCP/IP connection across the Internet is not
suitable for 2-tier client server! It is both slow and
insecure. Passing the database path "in clear" is not nice
either. (Use an alias!)
Many people use SSL tunneling for occasional, low-octane WAN access
for 2-tier clients - Zebedee is a popular free software for this.
The preferred way to do WAN is a 3-tier arrangement, whereby
applications execute on the server in response to requests from
browser-based clients (simplest) or specialised distributed networking layers.
In between 2- and 3-tier, you can use remote desktop if the entire
system is homogeneously Windows. If the client machines are Win2K or
higher you can have them connect to the LAN as Windows remote desktop
clients and run their client application in the remote network
(remotely for them, locally on the LAN).
There are other virtual network options, too, e.g. VNC at the
low-cost end; and many more..
./heLen