A) I have found this : Under SYSAM directory (/Sysam-2_0/Flexnet_enduser.pdf)
FLEXLM_TIMEOUT Windows only: Sets the timeout value a FLEXenabled application uses when attempting to connect to a license server system port in the range 27000-27009. Values are in microseconds, within the range 0 through 2147483647. The default setting is 100000 microseconds.
Which corresponds to 100 ms of which you speak.
Following documentation you can set Registry
On Windows, the FLEX net Licensing registry location is: HKEY_LOCAL_MACHINE\Software\FLEXlm License Manager
I have never play with this
B) Usually when PD communicate with SYSAM two ports are used and defined by the ADMIN guy. If no TCP/IP port number is specified, default ports in the range of 27000 and 27009 is used. it's a bad practice. For security reason you wan't open many ports on your Firewall. Also each time SYSAM is restarted the ports number can be a new one. See the user documentation to know how defined the two ports used by SYSAM.
If the ADMIN guy at your enterprise does not know the ports used by SYSAM. You can say to do netstat -ba.
(Where SYSAM is installed under windows start MS-DOS command as Administrator and wrote at command line netstat -ba. A list of all program listening on port is displayed. Search for SYSAM and the ports number.)
Ping allow to know if you are able to reach a server where SYSAM is installed from your client computer.
Telnet is a program available on your Windows computer.
Historically, Telnet provided access to a command-line interface (usually, of an operating system) on a remote host. Most network equipment and operating systems with a TCP/IP stack support a Telnet service including Windows OS.
Why use telnet to test port opening? Is this a simple way to determine if you are able to reach the ports listen by SYSAM from your client computer.
You log in under your VPN access. You open a MS-DOS command . You type telnet server_ip port_number
If SYSAM answer. A black window open and a blink cursor appear.
If not it's because you have firewall issue and not a timeout problem.
I think it's my last comment about this issue. Good luck.
If you find the solution does not hesitate to let me know.