0x80072EE7

SCEP server name could not be resolved

Last reviewed 2026-07-18 by the Just Software engineering team · also seen as 80072ee7, ERROR_INTERNET_NAME_NOT_RESOLVED

What it means

0x80072EE7 is the WinINet/WinHTTP error "The server name or address could not be resolved" (Win32 12007). The device never got as far as connecting — DNS resolution of the hostname in the SCEP profile's server URL failed.

Common causes

  1. The SCEP URL uses an internal DNS name (e.g. ndes.corp.local) but the device is off the corporate network — the classic mistake in cloud-managed deployments.

  2. The public hostname exists but is missing from external DNS, or a split-DNS zone is incomplete.

  3. Device-side DNS problems: captive portals, VPN DNS misconfiguration, or a typo in the profile URL.

How to fix it

  1. From a failing device (off-network, as a user would be), run nslookup <scep-hostname> — if it fails, the profile URL is not resolvable where devices actually live.

  2. Publish the SCEP endpoint on an externally resolvable name — for NDES behind Entra application proxy, use the external URL the proxy assigns, not the internal server name.

  3. Check the profile for typos: Devices > Configuration > (SCEP profile) > SCEP Server URLs.

An unhandled error has occurred. Reload 🗙