ASA Database Administration Guide
Client/Server Communications
Using the TCP/IP protocol
There are restrictions on connections when the client application is on one side of a firewall, and the server is on the other. Firewall software filters network packets according to network port. Also, it is common to disallow UDP packets from crossing the firewall.
When connecting across a firewall, you must use a set of communication parameters in the CommLinks (LINKS) connection parameter of your application's connection string.
ClientPort Set this parameter to a range of allowed values for the client application to use. You can then configure your firewall to allow these packets across. You can use the short form CPort.
Host Set this parameter to the host name on which the database server is running. You can use the short form IP.
ServerPort If your database server is not using the default port of 2638, you must specify the port it is using. You can use the short form Port.
DoBroadcast=NONE Set this parameter to prevent UDP from being used when connecting to the server.
The following connection string fragment restricts the client application to ports 5050 through 5060, and connects to a server named myeng running on the machine at address myhost using the server port 2020. No UDP broadcast is carried out because of the DoBroadcast option.
Eng=myeng;Links=tcpip(ClientPort=5050-5060;Host=myhost;Port=2020;DoBroadcast=NONE)
For more information, see the following: