VerifyServerName (VERIFY) protocol option (client side only)

Controls whether clients must verify the database server name before connecting.

Syntax

{ VerifyServerName | VERIFY }={ YES | NO }

When connecting over TCP using the DoBroadcast=NONE parameter, the client makes a TCP connection, then verifies that the name of the server found is the same as the one it is looking for. Specifying VerifyServerName=NO skips the verification of the server name. This allows SQL Anywhere clients to connect to a SQL Anywhere server if they know only an IP address/port.

The server name must still be specified in the connection string, but it is ignored. The VerifyServerName (VERIFY) protocol option is used only if DoBroadcast=NONE is specified.

If the server is using -sb 0 or BroadcastListener=NO, the client does not need to specify DoBroadcast=NONE to connect to it, although the client must still specify the HOST protocol option. The dblocate utility will not find the server.

Note

It is recommended that you only use this protocol option in the rare circumstance where it is not possible to give each server a unique server name, and use that unique name to connect. Giving each server a unique server name, and connecting to the server using that name is still the best way to connect.