Differences

This shows you the differences between two versions of the page.

Link to this comparison view

control_error_-_unable_to_locate_sslip_message [2019/01/27 11:28] (current)
Line 1: Line 1:
 +====== Control Error - Unable to Locate SSLIP ======
 +
 +
 +
 +===== Error Message =====
 +
 +
 +
 +"​Unable to Locate SSLIP" when Control is launched.
 +
 +
 +
 +===== Explanation of Error =====
 +
 +
 +
 +When launched, one of the first thing Control does it try to locate the SSLIP to obtain the list of user login names (among other things). It does this using a UDP broadcast on the local network (by default this is on port **xxx**).
 +
 +
 +
 +This message indicates that Control did not get response from a the SSLIP. This is usually caused (in order of likelihood) by one of the following:
 +  - The SSLIP is not running.
 +  - The SSLIP'​s socket is hung.
 +  - The SSLIP is running but cannot be accessed via UDP.
 +  - The [[control_parameter_-_sslipaddress|control_parameter_-_sslipaddress]] is set to force Control to look for the SSLIP at the wrong address.
 +  - The SSLIP or Control is running on a different port offset.
 +
 +
 +
 +===== Severity =====
 +
 +**High**. The user is unable to open Control.
 +
 +
 +
 +===== Resolution =====
 +  - Restart the SSLIP. If some users are able to connect but not others, then the problem is probably in the network connection.
 +  - UDP is often blocked by firewalls. Add an exemption for UDP port **xxx** (the default port) and an exemption for the SSLIP.EXE.
 +  - The UDP broadcast used to locate the SSLIP will not travel beyond a router. If the SSLIP and Control are behind different routers, UDP will be ineffective. In this case, Control must be told the IP address of the SSLIP instead of using UDP to locate it. Use the parameter [[control_parameter_-_sslipaddress|control_parameter_-_sslipaddress]] to specify the address of the SSLIP.
 +  - If you are on a client machine, ensure that User Account Control (UAC) is not turned up too high. If it is on the two highest levels all network activity attempted by Control is denied because a network application is attempting to communicate across the network. UAC sees this attempt of communication as suspicious and blocks the activity. Use one of the lower two levels to resolve the problem or have the user run Control as administrator by right-clicking and choosing Run As Administrator.
 +
 +
 +
 +===== Possible Root Cause(s) =====
 +
 +
 +
 +Firewall blocking, UDP Broadcasts do not travel beyond a router, SSLIPAddress manually configured but incorrect.
 +
 +
 +
 +===== Related Errors =====