Troubleshoot a Topaz Signature Pad

Use this guide when Enceit Care reports that a Topaz signature pad was not detected or the Device signing option does not start.

First check: is SigWeb running?

On the Windows computer connected to the pad, open PowerShell and run:

Test-NetConnection 127.0.0.1 -Port 47290

A working SigWeb installation should show:

TcpTestSucceeded : True

You can also test the service directly in Chrome:

https://tablet.sigwebtablet.com:47290/SigWeb/TabletState?noCache=1

A response of 0 normally means that SigWeb is reachable and the tablet is idle.

If the hostname cannot be found

If Chrome shows DNS_PROBE_FINISHED_NXDOMAIN for tablet.sigwebtablet.com, but 127.0.0.1 on port 47290 succeeds, SigWeb is running but the Topaz local hostname mapping is missing.

This hostname is intentional. Enceit Care uses tablet.sigwebtablet.com because the production site is HTTPS and the SigWeb certificate is issued for that hostname. Do not replace the production endpoint with http://localhost or https://127.0.0.1 in the application.

Ask a Windows administrator or IT support to add this line to:

C:\Windows\System32\drivers\etc\hosts
127.0.0.1 tablet.sigwebtablet.com

Then run:

ipconfig /flushdns
Resolve-DnsName tablet.sigwebtablet.com
Test-NetConnection tablet.sigwebtablet.com -Port 47290

The hostname should resolve to 127.0.0.1, and the port test should succeed.

If Windows says the hosts file is locked

The hosts file is protected and may also be monitored by antivirus or endpoint-security software such as Webroot. Do not disable security software permanently or change the file permissions.

Have IT:

  1. Open an elevated PowerShell or Notepad session.
  2. Check whether endpoint security is blocking the file.
  3. Authorize the single local mapping above through the security policy, or repair Topaz SigWeb using the organization’s software-management process.
  4. Flush DNS and repeat the hostname test.

If the file is reported as being used by another process, restart Windows first. If it remains locked, IT can use Microsoft Process Explorer or Sysinternals Handle to identify the process holding C:\Windows\System32\drivers\etc\hosts.

If the browser asks for local network access

Recent Chromium browsers may ask whether Enceit Care can access devices on the local network. Select Allow. This permission is required for the web page to contact the SigWeb service running on the same computer.

If the prompt was dismissed, open the site permissions for Enceit Care in Chrome or Edge and allow local network access, then reload the signing page.

If the service is reachable but the tablet is not detected

  • Confirm that the Topaz pad is connected directly by USB.
  • Open Device Manager → Ports (COM & LPT) and confirm the device appears.
  • Confirm that the Topaz SigWeb configuration uses the same COM port as the device.
  • Restart SigWeb after changing the COM port.
  • Close other applications that may be using the pad.
  • Reload Enceit Care after changing the service or hosts configuration.

Browser and security notes

  • Use a current Chromium-based browser such as Chrome or Microsoft Edge.
  • Corporate DNS filtering, antivirus, endpoint protection, VPN software, and firewall rules can block the local hostname or the SigWeb port.
  • Do not disable certificate validation or use an arbitrary IP address in the production application.
  • The Device mode can be used only when the local SigWeb service and browser permissions are available. Type and Draw modes remain available as alternatives.

If the problem continues, send Support the results of Resolve-DnsName, Test-NetConnection, and the browser Console error. Do not send the contents of the hosts file if it contains unrelated corporate entries.

Last reviewed: 2026-10-10

Need more help? Back to Help Center