1. Remote server is not available.
2. Internet connection is missing or unstable.
3. Application is blocked individually via firewall/antivirus/etc.
4. One of the used ports or addresses is blocked for the entire system.
Not much can be done for the first and second cases, but server downtime is very rare and brief. Next steps will help to resolve this problem in the third and fourth cases.
1. Checking port availability.
1.1. We will use standard telnet client for this operation because Windows components is rarely blocked by protection software. Telnet client is already activated for Windows XP, but you need to turn it on manually for Windows Vista and later versions.
1.2. In order to activate telnet client, go to the `main menu -> control panel -> programs and features -> turn windows features on or off` and make sure that `telnet client` box is checked, then press `OK`.
1.3. Open console window and type `telnet 126.96.36.199 23457` then press enter.
1.4. If you see black screen with cursor then telnet is successfully connected to the server, which means that port is available system wide and something is blocking WICReset specifically.
1.5. If you will see some errors in the console output (typically: `could not open connection to the host on port`), then this port is blocked for entire system or on the remote device.
2. If application blocked individually.
2.1. You need to add WICReset to the exception lists of each protection software or create individual rules if this option is available. Please, see documentation of the corresponding software to find out how to do this.
2.2. While it's not advisable, you may consider to briefly disable protection software until waste counters reset is finished.
3. If used ports blocked system wide.
3.1. If your PC is in the local network, make sure that connections to the 23457 port is allowed in the gateway server's firewall settings.
3.2. If you are using router with enabled firewall rules, make sure that connections to the 188.8.131.52:23457 is allowed for target PC (firewall settings usually available via router's web interface).
3.3. If VPN provider is used, make sure, that system routing table contains correct entries that include remote server address.
3.4. Make sure, that protection software doesn't have global rule that blocks connections to the used ports. Some protection software may have default rules that limit connections only to the most widely used port numbers (http, ftp, etc).
3.5. Some third party software (for example, some VPN software) may also provide additional firewall-like protection service. Make sure, that these applications either disabled during waste reset or WICReset is added to their exclusion list when possible.
4. List of used ports :
4.1. Application will connect to remote server on 184.108.40.206:23457 (TCP) for waste counters reset.
4.2. Application will use 80 (TCP/HTTP) port in order to download database and RSS feed during initialization.
4.3. Ports 3289 (UDP/ENPC), 161 (UDP/SNMP) and 515 (TCP/LPD) will be used to discover network printers and communicate with them.