synxfpng utility

WTSupported in traditional Synergy on Windows
WNSupported in Synergy .NET on Windows
USupported on UNIX
VSupported on OpenVMS

The synxfpng utility can be used for troubleshooting network connections to Synergy TCP/IP services including xfServer (rsynd), License Manager server (synd), and SQL OpenNet server (vtxnetd). To verify that a client can access one of these services, run synxfpng from the client. Synxfpng uses only TCP/IP API calls and tests only whether the client can create and bind a socket. Synxfpng is installed in the dbl\bin directory.

Synxfpng prints a report to the screen, showing each port tested. If there are errors, try running it again with the ‑v option to get more information, including the TCP/IP error number. This information can be used by your network administrator to resolve TCP/IP network socket communication problems.

You can use synxfpng to determine if a DNS lookup problem is the cause of a slow connection. To do this, first run synxfpng with the host name as the server_name argument, and then run it with the IP address as the server_name argument. If the connection is faster using the IP address, there is a DNS lookup problem. Consult your network administrator for assistance in resolving the problem.

By default, synxfpng first looks up the IP as an IPv4 formatted address; then, if that fails, it tries IPv6. You can specify that only one or the other be used with the ‑v4 and ‑v6 options. If both ‑v4 and ‑v6 are included on the command line, the last one takes precedence.

xfServer

When pinging xfServer, synxfpng has the following syntax:

synxfpng [‑dsize] [‑h] [‑inum] [‑pport] [‑rnum] [‑v] [‑v4|‑v6] [‑vers] server_name

‑d size

Specify a packet size for sending to xfServer.

‑h

Display usage information.

‑i num

Ping the specified (or default) port num times. The default is 5.

‑p port

Ping the specified port.

‑r num

Ping a range of num ports, starting with the port specified with the ‑p option or, if ‑p is not specified, with the default port.

‑v

Verbose output. See sample output below.

‑v4

Server uses IPv4 addressing. (Default)

‑v6

Server uses IPv6 addressing.

‑vers

Returns the version of the server if it is version 10 or higher.

server_name

The host name or IP address of the system to ping.

By default, synxfpng pings the default xfServer port, 2330. If no service is found on that port, it increments the port number by 1 (i.e., 2331) and tests again. Synxfpng will continue incrementing the port number and testing ports until it finds a service or has tested 10 ports. You can specify a non‑default port with ‑p, in which case only that port is tested.

If the SCSPORT environment variable is set in the environment (and you do not specify ‑p), synxfpng will ping the SCSPORT port. If no service is found on that port, synxfpng will test up to 10 ports as described above. (On Windows, if SCSPORT is set in the registry, it is not read by synxfpng.

By default, synxfpng pings 5 times when it finds a service. You can specify a different number of pings with the ‑inum option.

You can specify the number of ports to test with ‑rnum. By default synxfpng will test up to 10 ports, and it stops as soon as it finds the service. But when ‑r is used, synxfpng continues pinging until num ports are tested, even if it finds a service early in the sequence.

Normally, the packet sent by synxfpng is only a few bytes. To specify that a packet of a particular size be sent, specify the size with the ‑d option. The packet will be the size you specify plus the usual packet size. (For example, if it’s usually 28 bytes and you specify ‑d1024, the packet will be 1052 bytes.)

The example below pings the server named Tiger on the default xfServer port (2330):

synxfpng tiger
Pinging Synergy/DE xfServer on host [tiger] port 2330
Round trip (28 bytes) 31.933 ms
Round trip (28 bytes) 2.055 ms
Round trip (28 bytes) 0.795 ms
Round trip (28 bytes) 0.951 ms
Round trip (28 bytes) 0.551 ms

Average round trip 7.257 ms

The example below pings the server named Tiger on the default xfServer port and requests verbose output. The sample output is from Windows.

synxfpng -v tiger
WinSock status information:
    Description: WinSock 2.0
    SystemStatus: Running
    Using version 1.1
    Supports up to version 2.2
Starting DNS Lookup tiger Wed Oct 03 11:28:44 2012
 -- Complete 127.0.0.1 Wed Oct 03 11:28:44 2012
Pinging Synergy/DE xfServer on host [tiger] port 2330
Starting socket(AF_INET, SOCK_STREAM, IPPROTO_TCP) -- Completed
Starting bind() -- Wed Oct 03 11:28:44 2012
Starting connect() -- Wed Oct 03 11:28:44 2012
     -- Completed Wed Oct 03 11:28:44 2012
Starting setsockopt(, SOL_SOCKET, SO_KEEPALIVE,,) -- Completed
Starting setsockopt(, IPPROTO_TCP, TCP_NODELAY,,) -- Completed
Starting Ping Wed Oct 03 11:28:44 2012
Round trip (28 bytes) [v10.0.3 server] 3.464 ms
Round trip (28 bytes) [v10.0.3 server] 8.340 ms
Round trip (28 bytes) [v10.0.3 server] 0.772 ms
Round trip (28 bytes) [v10.0.3 server] 28.167 ms
Round trip (28 bytes) [v10.0.3 server] 0.598 ms
Average round trip 8.268 ms
Socket closed Wed Oct 03 11:28:49 2012

License Manager server

Run synxfpng with the ‑s option to ping License Manager server (synd). This option is supported on Windows only.

synxfpng [‑h] [‑inum] [‑pport] [‑rnum] ‑s [‑v] [‑v4|‑v6] [‑vers] server_name

‑h

Display usage information.

‑i num

Ping the specified (or default) port num times. The default is 5.

‑p port

Ping the specified port.

‑r num

Ping a range of num ports, starting with the port specified with the ‑p option or, if ‑p is not specified, with the default port.

‑s

Ping License Manager server connection.

‑v

Verbose output.

‑v4

Server uses IPv4 addressing. (Default)

‑v6

Server uses IPv6 addressing.

‑vers

Returns the version of the server if it is version 10 or higher.

server_name

The host name or IP address of the system to ping.

When ‑s is used, by default synxfpng pings port 2380, the default License Manager server (synd) port. If no service is found on that port, it will increment the port number by 1 (i.e., 2381) and test again. Synxfpng will continue incrementing the port number and testing ports until it finds a service or has tested 10 ports. When it finds a service, it pings 5 times by default. To specify a different number of pings, use ‑inum.

To ping a non‑default port, use the ‑p option. When ‑rnum is used, synxfpng continues pinging until num ports are tested, even if it finds a service early in the sequence.

This example pings License Manager server on port 2445, located on the server named Tiger, three times:

synxfpng -s -p2445 -i3 tiger

SQL OpenNet server

Run synxfpng with the ‑x option to ping SQL OpenNet server.

synxfpng [‑h] [‑pport] [‑rnum] [‑v] [‑v4|‑v6] ‑x server_name

‑h

Display usage information.

‑p port

Ping the specified port.

‑r num

Ping a range of num ports, starting with the port specified with the ‑p option or, if ‑p is not specified, with the default port.

‑v

Verbose output.

‑v4

Server uses IPv4 addressing. (Default)

‑v6

Server uses IPv6 addressing.

‑x

Ping SQL OpenNet server connection.

server_name

The host name or IP address of the system to ping.

When ‑x is used, by default synxfpng pings port 1958, the default SQL OpenNet server port. If no service is found on that port, it will increment the port number by 1 (i.e., 1959) and test again. Synxfpng will continue incrementing the port number and testing ports until it finds a service or has tested 10 ports.

When used ‑x is used with the ‑v option, synxfpng provides more verbose SQL OpenNet error reporting than is available with vtxping.

To ping a non‑default port, use ‑p option. When ‑rnum is used, synxfpng continues pinging until num ports are tested, even if it finds a service early in the sequence.

To ping SQL OpenNet on ports 1955 through 1959 on the server named Tiger:

synxfpng -x -p1955 -r5 tiger