PxPlus User Forum

Twitter Twitter Twitter

Author Topic: Ports to open for WindX.utl SPAWN  (Read 1308 times)

lgondor

  • New Member
  • *
  • Posts: 2
    • View Profile
Ports to open for WindX.utl SPAWN
« on: June 27, 2018, 12:05:28 PM »
Which TCP port range should be open for the directive CALL "*WindX.utl;SPAWN" to work? I have opened up 3000- 65535, but this is not in line with best practices. Without this range open, we get an error message dialogue box displaying "Connection failure to host:[tcp]10.11.22.33:NNNNN; NODELAY; STREAM", where NNNNN is some random high port number.

This is for WindX Plugin 2017 Upd 1, and PxPlus Version 14.10.0000 running on RHEL7.5

Thanks,
Les Gondor
Electro Sonic

Mike King

  • Administrator
  • Diamond Member
  • *****
  • Posts: 3436
  • Mike King
    • View Profile
    • PVX Plus Technologies
Re: Ports to open for WindX.utl SPAWN
« Reply #1 on: June 27, 2018, 01:16:10 PM »
Generally we suggest you use Simple CS to connect to the server as it only requires a single port.  The default is 4093 which is defined by ICANN for use by us.

If using Telnet or SSH to connect then by default the system will ask the OS to provide it an available port number which, as you say, can cause trouble with firewall settings. 

Now you can override this and force the application to use a specific host/port by setting %PXPLUS_HOST prior calling *windx.utl;spawn.  This variable can be set to an asterisk followed by name/address of the host (as seen from Workstation perspective), a semi=colon, then the port number to use. 

Example

  %PXPLUS_HOST$="*server1.inhouse.net;4093"

Where "server1.inhouse.net" is the host address and 4093 is the port to use. 

This is documented at a note on the bottom of https://manual.pvxplus.com/page/windx/windxutl.htm

lgondor

  • New Member
  • *
  • Posts: 2
    • View Profile
Re: Ports to open for WindX.utl SPAWN
« Reply #2 on: June 27, 2018, 02:24:18 PM »
Thanks, Mike, I'll try that.

By the way, the note on the WindX.utl page of the local help file of the V14 installation makes no reference to any of those variables.