大网数据广告活动
网络与域名解析

Troubleshoot DC and Kerberos for DirectAccess troubleshooting

· 52CE 我爱测

This article discusses how to troubleshoot DC and Kerberos for DirectAccess server troubleshooting.

DirectAccess writes all configuration on Group Policy policies. The loss of access to the domain controller is indicated on the operation console.

Domain controller error

Error:

The corporate domain controller for contoso.local is not available.

Cause

  • Network connectivity is disrupted.
  • The firewall is blocking access.

Resolution

To resolve this issue, make sure that the domain controller can be accessed.

You can use network trace tools to verify that communication with the domain controllers is occurring.

Kerberos error

Kerberos errors don't appear on the console as often as domain controller errors do.

Here's an example that occurs when the KDC proxy service is not running. The KDC Proxy Server service runs on edge servers. It proxies Kerberos protocol messages to domain controllers on the corporate network.

Kerberos: Not working properly
Error:
A network authentication service (kpssvc) is not available. This service helps in authenticating DirectAccess clients when they connect to the corporate network via DirectAccess.

This issue might occur is the kpssvc service was stopped or the service stopped responding.

The service will restart automatically, or you can restart it manually.

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
适用范围
- Supported versions of Windows Server · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

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

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