我们建议使用域名而不是 IP 地址连接到网域控制器,因为托管式 Microsoft AD 不提供静态 IP 地址。如果使用域名,即使网域控制器的 IP 地址发生变化,Active Directory DC 定位器进程也可以找到它。
使用 IP 地址进行 DNS 解析
如果您使用 IP 地址连接到网域,则可以在 VPC 网络上创建入站 DNS 政策,以便它可以使用与托管式 Microsoft AD 相同的名称解析服务。托管式 Microsoft AD 使用 Cloud DNS 为使用 Cloud DNS 对等互连的托管式 Microsoft AD 网域提供名称解析。
如需使用入站 DNS 政策,您必须配置本地系统或域名服务器,将 DNS 查询转发到与 Cloud VPN 隧道或 VLAN 连接位于同一区域的代理 IP 地址将您的本地网络连接到您的 VPC 网络。了解如何创建入站服务器政策。
使用对等互连
托管式 Microsoft AD 不支持嵌套对等互连,因此只有直接获得 Active Directory 授权的网络才能访问网域。已获授权的网络的对等互连网络无法访问托管式 Microsoft AD 网域。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[],[],null,["# Connect to a Managed Microsoft AD domain\n\nThis page describes the various options for connecting to a Managed Service for Microsoft Active Directory\ndomain.\n\nConnecting to a domain-joined Windows VM with RDP\n-------------------------------------------------\n\nYou can connect to your domain with Remote Desktop Protocol (RDP). For security\nreasons, you cannot use RDP to connect directly to a domain controller. Instead,\nyou can use RDP to connect to a Compute Engine instance, and then use the\nstandard AD manageability tools to work remotely with your AD domain.\n\nAfter [domain-joining your Windows VM](/managed-microsoft-ad/docs/quickstart-domain-join-windows), you can\n[use RDP in the Google Cloud console to\nconnect to your domain-joined Windows VM](/compute/docs/instances/connecting-to-windows)\nand [manage your Active Directory objects](/managed-microsoft-ad/docs/manage-active-directory-objects).\n\n### Troubleshooting RDP connections\n\nIf you have difficulty connecting to your Windows instance with RDP,\nsee [Troubleshooting RDP](/compute/docs/troubleshooting/troubleshooting-rdp)\nfor tips and approaches to troubleshoot and resolve common RDP issues.\n\n#### Resolving Kerberos issues\n\nIf you try to use Kerberos for your RDP connection, but it falls back to NTLM,\nyour configuration may not meet the necessary requirements.\n\nTo RDP to a Managed Microsoft AD-joined VM using Kerberos, the RDP client\nneeds a ticket issued for the target server. To get this ticket, the client\nmust be able to do the following tasks:\n\n- Determine the service principal name (SPN) of the server. For RDP, the SPN is derived from the server's DNS name.\n- Contact the domain controller of the domain the client's workstation is joined to and request a ticket for that SPN.\n\nTo ensure that the client can determine the SPN, add an IP-based SPN to the server's\ncomputer object in AD.\n\nTo ensure that the client can find the right domain controller to contact, you\nmust do one of the following tasks:\n\n- Create a trust relationship with your on-premises AD domain. Learn more about [creating and managing trusts](/managed-microsoft-ad/docs/create-manage-trusts).\n- Connect from a domain-joined workstation using [Cloud VPN](/network-connectivity/docs/vpn) or [Cloud Interconnect](/network-connectivity/docs/interconnect).\n\nConnecting to a domain-joined Linux VM\n--------------------------------------\n\nThis section lists some of the open source options for managing Active Directory\ninteroperation with Linux. Learn\n[how to join a Linux VM to a Managed Microsoft AD domain](/managed-microsoft-ad/docs/quickstart-domain-join-linux).\n\n#### System Security Services Daemon (SSSD) joined directly to Active Directory\n\nYou can use System Security Services Daemon (SSSD) to manage Active Directory\ninteroperation. Note that SSSD does not support cross-forest trusts. Learn about\n[SSSD](https://docs.pagure.org/SSSD.sssd/).\n\n#### Winbind\n\nYou can use Winbind to manage Active Directory interoperation. It uses Microsoft\nRemote Procedure Calls (MSRPCs) to interact with Active Directory, which is\nsimilar to a Windows client. Winbind supports cross-forest trusts. Learn about\n[Winbind](https://www.samba.org/samba/docs/old/Samba3-HOWTO/winbind.html).\n\n#### OpenLDAP\n\nOpenLDAP is a suite of LDAP applications. Some third-party providers have\ndeveloped proprietary Active Directory interoperation tools based on OpenLDAP.\nLearn about\n[OpenLDAP](https://en.wikipedia.org/wiki/OpenLDAP).\n\nConnecting to a domain using trust\n----------------------------------\n\nIf you create a trust between your on-premises domain and your\nManaged Microsoft AD domain, you can access your AD resources in Google Cloud\nas if they are in your on-premises domain. Learn how to\n[create and manage trusts in Managed Microsoft AD](/managed-microsoft-ad/docs/create-manage-trusts).\n\nConnecting to a domain with Hybrid Connectivity products\n--------------------------------------------------------\n\nYou can connect to your Managed Microsoft AD domain with Google Cloud Hybrid\nConnectivity products, like Cloud VPN or Cloud Interconnect. You can\nconfigure the connection from your on-premises or other network to an authorized\nnetwork of Managed Microsoft AD domain.\n\n### Before you begin\n\n- [Create a Managed Microsoft AD domain](/managed-microsoft-ad/docs/quickstart-create-domain).\n\n- [Join your Windows VM](/managed-microsoft-ad/docs/quickstart-domain-join-windows) or\n [your Linux VM](/managed-microsoft-ad/docs/quickstart-domain-join-linux) to the Managed Microsoft AD\n domain.\n\n### Connecting using domain name\n\nWe recommend connecting to a domain controller using its domain name rather than\nits IP address because Managed Microsoft AD does not provide static IP\naddresses. Using the domain name, the Active Directory DC locator process can\nfind the domain controller for you, even if its IP address has changed.\n\n### Using IP address for DNS resolution\n\nIf you use the IP address to connect to a domain, you can create an inbound DNS policy\non your VPC network so that it can use the same name resolution services that\nManaged Microsoft AD uses. Managed Microsoft AD uses Cloud DNS to provide\nname resolution to Managed Microsoft AD domain using Cloud DNS peering.\n\nTo use the inbound DNS policy, you must configure your on-premises systems or\nname servers to forward DNS queries to the proxy IP address located in the same\nregion as the Cloud VPN tunnel or VLAN attachment that\nconnects your on-premises network to your VPC network.\nLearn about [creating an inbound server policy](/dns/docs/policies#create-in).\n\nUsing peerings\n--------------\n\nManaged Microsoft AD does not support nested peering, so only networks\nthat are directly authorized for Active Directory can access the domain. Peers\nof the authorized network cannot reach the Managed Microsoft AD domain."]]