大网数据广告活动
域与目录服务

Error (Can't connect to the service) when you try to register a device

· 52CE 我爱测

Describes a problem that triggers an error when you try to register a device in a Windows 8.1 or Windows Server 2012 R2 environment.

Original product version:   Windows 8.1 Enterprise, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Datacenter, Microsoft Entra ID
Original KB number:   3045378

Symptoms

When you try to perform a Workplace Join operation and register your device to your local Active Directory domain from a Windows 8.1 device, you receive the following error message:

Can't connect to the service
We can't connect to the service you need right now. Check your network connection or try this again later.

Cause

This problem may occur for one of the following reasons:

  • Although the Active Directory Federation Services (AD FS) proxy server can resolve the name of the federation server, the name resolves to an incorrect host.
  • The AD FS service is not running on the AD FS proxy server.
  • The WAP role is not installed.
  • The WAP role is installed but is not configured.

Resolution

To resolve this problem, follow these steps:

  1. Sign in to your AD FS proxy server:

    1. Run the Services Management Console (services.msc).
    2. Locate the AD FS service.
    3. Verify that the service is in a Started state.
  2. Verify name resolution of the Internal AD FS instance:

    1. From the AD FS proxy server, open a command prompt.
    2. Type PING adfsserver.contoso.com, and then press Enter.

    [!NOTE] The adfsserver.contoso.com placeholder represents the address of your AD FS server, such as sts.contoso.com.

  3. Don't worry about whether the PING is successful or unsuccessful. Instead, notice whether the target address resolves to the IP address of the server.

  4. If the address is incorrect, correct the resolution conflicts:

    • Check the Hosts file on the AD FS proxy server to see whether the correct entry is included and whether it targets your AD FS instance.
    • If you do not use a Hosts file, check internal DNS by using the Nslookup command to verify DNS records.

More information

For more troubleshooting information, see the following article:

Diagnostic logging for troubleshooting Workplace Join issues

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
See source applicability · Source date 06/08/2020
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。