How to Fix Connection to KMS Server Failed Error

Updated December 2024: Stop getting error messages and slow down your system with our optimization tool. Get it now at this link

1. Download and install the repair tool here.
2. Let it scan your computer.
3. The tool will then repair your computer.

If a KMS host fails, you must install a KMS host key on a new host and then activate the host. Ensure that the new KMS host has an RR VRS in the DNS database. If you install the new KMS host with the same computer name and IP address as the failed KMS host, the new KMS host can use the failed host’s DNS SRV RR entry. If the new host has a different computer name, you can manually remove the failing host’s DNS SRV-RR or (if scanning is enabled in DNS) have DNS remove it automatically. If the network uses DDNS, the new KMS host automatically creates a new SRV RR on the DNS server. The new KMS host then begins collecting client renewal requests and begins activating clients when the KMS activation threshold is reached.

When your KMS clients use auto-discovery, they automatically select another KMS host if the original KMS host does not respond to renewal requests. If clients are not using Auto Discovery, you must manually update the KMS client computers that have been assigned to the failed KMS host by running slmgr.vbs /skms. To avoid this scenario, configure the KMS clients to use Auto Discovery.

Configuring DNS for Multiple KMS Hosts Correctly

• Make sure that all computers are in the same Active Directory service domain.
• Create a global security group in the Active Directory service domain.
• Add each computer running KMS to the newly created global security group.
• Set permissions to allow updates by members of this new group on the DNS server.
• If you are using KMS, the host computer must be discoverable on your local network. The first host computer automatically reveals its existence when it creates an SRV record on the DNS server.

Other hosts cannot modify or update the SRC if the DNS server is not properly configured.

Ensure that the server clock is synchronized with the KMS clock.

If the 0xC004F074 The Key Management Server (KMS) error is not available, the time on the cloud server is radically different from the time on the KMS.

• At this point, you must configure the server to use a Network Time Protocol (NTP) time source by executing the appropriate command.
• Once the time is synchronized, try executing each of the following commands:
• You must open port 123 of the User Datagram Protocol (UDP) to enable synchronization.
• Make sure your firewall allows outgoing connections on port 1688 of the Transmission Control Protocol (TCP).

Newly added computers do not increase the number of KMS.

• Open the search bar on the client computer.
• Type cmd.
• Right-click at the command prompt and select Run as Administrator.
• In the command prompt window, type sysprep /generalize to reset the client computer ID. If this does not work, try slmgr /rearm.
• Sometimes client computers appear identical to the host and are not counted as separate computers.

If you are still experiencing problems, you can switch to AD-based activation by following the official documentation.

If you have further questions or suggestions, please feel free to contact the “Comments” section below.

https://docs.microsoft.com/en-us/windows-server/get-started/activation-troubleshoot-kms-issues

Expert Tip: This repair tool scans the repositories and replaces corrupt or missing files if none of these methods have worked. It works well in most cases where the problem is due to system corruption. This tool will also optimize your system to maximize performance. It can be downloaded by Clicking Here