Handling Port Conflicts
By default SigCaptX uses a starting port number of 8000 (for the SigCaptX service process). 8001 is used for the first server process, 8002 for the second and so on as required.
This can occasionally cause problems on systems where other applications are also using port numbers in the same range or where firewall or anti-virus software is restricting access to them.
You can determine whether another application or process is listening on port 8000 by running the following command:
netstat -a -o | find "LISTENING" | find ":8000"
If SigCaptX cannot gain access to ports 8000 and 8001 then it will not run.
If the access is being prevented by security software (this has been experienced particularly with Kaspersky and Sophos) then one solution is to change the settings in the security software so that it allows access to those ports.
An alternative solution is to change the port numbers which SigCaptX uses - this requires coding and registry setting changes as described below.
- Registry settings:
(for more details please see the SigCaptX installation guide included in the Signature SDK download: SigCaptX-User-Guide.pdf)
Location: **HKEY_LOCAL_MACHINE\SOFTWARE\Wacom\SigCaptX** or **HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Wacom\SigCaptX** start_port 8000 end_port 65535 Change the start_port number from 8000 to another number which you believe is less likely to cause a conflict. The end_port can be changed as well if desired.
Location: Please search in your code for the place where a call is made to the start port as follows:
wgssSignatureSDK = new WacomGSS_SignatureSDK(onDetectRunning, 8000);
Having found this line of code change the value "8000" to be the same as the new value which you have set up in the registry for "start_port" above.
So if you have specified a start_port value of 10500 then the code would now read:
wgssSignatureSDK = new WacomGSS_SignatureSDK(onDetectRunning, 10500);