|
WSupported on Windows
|
USupported on Unix
|
VSupported on OpenVMS
|
NSupported in Synergy .NET
|
This program is used to test a connection to SQL OpenNet. Vtxping uses only TCP/IP API calls and tests only whether the server has been started successfully. Vtxping prints a report to the screen. If there are errors, the report includes the TCP/IP error number. This information can be used by your network administrator to resolve TCP/IP network socket communication problems.
|
For more verbose error reporting, run synxfpng with the -x and -v options. See synxfpng utility. |
vtxping [-mnum] [-pport] server_name [server_name...]
Options
-mnum
(optional) Retry a maximum of num times. The default is 3.
-pport
(optional) Ping the specified port (the port number on which SQL OpenNet is running). This is required on Windows and Unix unless a port number is specified for SQL OpenNet in the services file for your system. See Configuring Connectivity Series for more information.
server_name […]
The host name of the machine that SQL OpenNet is running on. You can put multiple server names on the command line as long as they all use the same port number. Vtxping will ping each one in turn.
Discussion
If -p is not specified, vtxping uses the port specified in the services file on Windows and Unix and port 1958 on OpenVMS.
When you run vtxping without any options, it displays usage information.
Usage
- Ping the SQL OpenNet server named tiger on port 1958.
vtxping -p1958 tiger
- Ping the servers tiger and lion, both of which are running SQL OpenNet on port 4444. If vtxping cannot connect on the first try, it will attempt twice more.
vtxping -m2 -p4444 tiger lion
If the server was started successfully, you’ll receive a “vtxnetd is alive and kicking” message. If there’s a problem, you’ll see an error message.
