MyIP (ME) protocol option

Indicates the networking interfaces that the client should use to find the database server when used on the client. Indicates the networking interfaces on which the database server should listen for connections when used on the database server.

Syntax

{ MyIP | ME }={ ip-address [, ip-address ... ] | NONE }

Available protocols

Allowed values

ip-address This string must be specified in the form of an IP address. You must separate multiple IP addresses with commas.
NONE If the keyword NONE is supplied as the IP number, no attempt is made to determine the addressing information. The NONE keyword is intended for clients on computers where this operation is expensive, such as computers with multiple network cards or remote access (RAS) software and a network card. It is not intended for use on the database server.

Remarks

The MyIP (ME) protocol option is provided for computers with more than one network adapter.

Each adapter has an IP address. By default, the database server uses every network interface it finds. If you don't want your database server to listen on all network interfaces, specify the address of each interface you want to use in the MyIP (ME) protocol option.

When specifying an IPv6 address on a Windows platform, the interface identifier should be used. Unix platforms support both interface identifiers and interface names in IPv6 addresses. The interface identifier is required on Linux (kernel 2.6.13 and later).

Example

The following command line (entered all on one line) instructs the server to use two network cards.

dbsrv12 -x tcpip(MyIP=192.75.209.12,192.75.209.32) "%SQLANYSAMP12%\demo.db"

The following command line (entered all on one line) instructs the database server to use an IPv6 network card:

dbsrv12 -x tcpip(MyIP=fe80::5445:5245:444f) "%SQLANY12%\demo.db"

The following connection string fragment instructs the client to make no attempt to determine addressing information.

LINKS=tcpip(MyIP=NONE)

Discuss this page in DocCommentXchange.