It is best to validate that connection options are set correctly on a single computer, before applying changes to all computers.
Depending on the way you have applied connection options and product you are using, you need to check appropriate application logs.
Below is an example of ISL Light Client log, after ISL Light session is successfully established. The entries you are looking for are marked in bold and should resemble the section below (forward proxy IP address and transport should reflect your settings):
2019-10-22T09:16:19Z connect options: .. using [boost]=[wsstun-proxy] 2019-10-22T09:16:19Z connect options: .. using [http_proxy]=[... NA ...] ... 2019-10-22T09:16:19Z AT.0 AutoTransport: boosting type [wsstun-proxy] +34 ... 2019-10-22T09:16:19Z AutoTransport: custom HTTP proxy [34.199.41.164:32000] 2019-10-22T09:16:19Z AutoTransport: Resolving HTTP proxy setting: [34.199.41.164:32000] 2019-10-22T09:16:19Z AutoTransport: HTTP proxy: 34.199.41.164:32000 2019-10-22T09:16:19Z AutoTransport: HTTPS proxy: 34.199.41.164:32000 2019-10-22T09:16:19Z AT.0 AutoTransport: Secure WebSocket (permissive SSL) tunnel to isllight-myipccmhcjkeuqhg.islonline.net:443 through web proxy 34.199.41.164:32000 (1031) 2019-10-22T09:16:19Z dialog: Secure WebSocket (permissive SSL) tunnel to isllight-myipccmhcjkeuqhg.islonline.net:443 through web proxy 34.199.41.164:32000 (1031) 2019-10-22T09:16:19Z AT.0 HTTP connection: TCP connect to 34.199.41.164:32000 ... 2019-10-22T09:16:20Z AT.0 WebSockets: connection established 2019-10-22T09:16:20Z AT.0 AutoTransport: success wsstun-proxy