Chapter 3 Connection and Communication Parameters
65
Network communications parameters
If you experience problems with client/server network communications,
there are a number of command line parameters for both the client and the
server. These parameters enable you to work around peculiarities of different
network protocol implementations.
You can supply the network communication parameters on the server
command line as in the following example:
dbsrv7 -x tcpip(PARM1=value1;PARM2=value2;. . .),IPX
From the client side, the communications parameters are entered as the
CommLinks communication parameter:
CommLinks=tcpip(PARM1=value1;PARM2=value2;. . .),IPX
If there are spaces in a parameter, the network communication parameters
must be enclosed in quotation marks to be parsed properly by the system
command interpreter:
dbsrv7 -x "tcpip(PARM1=value 1;PARM2=value 2;...),IPX"
CommLinks="tcpip(PARM1=value 1;PARM2=value 2;...),IPX"
The quotation marks are required under UNIX if more than one parameter is
given, because UNIX interprets the semicolon as a command separator.
Boolean parameters are turned on with YES, ON, TRUE, or 1, and are turned
off with any of NO, OFF, FALSE, and 0. The parameters are case-
insensitive.
The examples provided should all be entered on a single line; you can also
include them in a configuration file and use the @ server command-line
switch to invoke the configuration file.
The parameters currently available are as follows.
ClientPort parameter [CPort]
TCP/IP. Client side only.
Assigned dynamically per-connection by the networking implementation. If
you do not have firewall restrictions, it is recommended that you do not use
this parameter.
"Host parameter" on page 68
"DoBroadcast parameter" on page 66
"ServerPort parameter" on page 70
"Connecting across a firewall" on page 96 of the book ASA User’s Guide
Usage
Default
See also
To Next Page
Loading...