Why am I seeing "Unable to find MFT server" error on the Kiosk?

Customers may encounter an error on the Kiosk stating:

Even though network paths and firewall rules appear correctly configured. Network monitoring may still show partial communication between the Kiosk and the MFT server.

Observed Behavior in Logs (e.g for URL is opswat.com)

Analysis of the Kiosk and MFT logs revealed the following:

• Attempts to reach opswat.com failed with errors such as:

  • Could not resolve host

  • Failed to connect to server after timeout

• Local Service Status

  • Successful local socket connections (e.g., 127.0.0.1:52988) indicate the Kiosk service itself is running correctly.

Cause

The errors suggest DNS resolution issues and/or network connectivity problems between the client Kiosk and the Vault server. Despite proper firewall and service configuration, the client is unable to reach the target servers using the hostnames.

Recommended Troubleshooting Steps

• Verify Server Hostnames and Reachability

  • Confirm that opswat.com is correct.

  • Attempt to reach the servers using their IP addresses to bypass DNS issues.

• Test DNS Resolution

• Test Network Connectivity

• Check Firewall, Proxy, and Routing Rules

  • Ensure outbound connections on ports 80 and 443 are allowed.

  • Verify that there is no proxy or routing configuration blocking access.

• Review Local Hosts File (Optional)

  • If DNS cannot be resolved correctly, consider adding entries to the local hosts file as a temporary workaround.

Conclusion

The “Unable to find MFT server” error is generally caused by network/DNS issues rather than Kiosk or MFT service failures. Confirming hostname resolution and connectivity from the client machine usually resolves the problem.