How to Troubleshoot “connection to KMS server failed” error | KMS Server failed [Solved]
The issues described here are related to an error message they got as below.
The connection to my KMS server failed! Trying to connect to another one… Please wait…
Sorry! Your version is not supported.
There are two main causes of this issue.
1. The cause of client
First of all, please make sure that Windows Update is enabled and your intenret connection is stable. To check if my KMS servers are blocked or not, please open your internet browser then try going to: http://kms8.msguides.com. If the page is visible, it means this server is not blocked.
One other point to note is that you need to run command prompt/batch file with admin rights.
One other point to note is that you need to run command prompt/batch file with admin rights.
Otherwise, the connection will be denied by UAC system.
2. The cause of server
Recently I need to do some experiments in the kms7 server so I changed the default KMS port (1688) to another one. And besides, I upgraded CPU and RAM memory on the kms8 server.
Because the number of daily clients is too big and still increasing over time, so the server can also be stuck at times. You can check and see if the server is overloaded or not here: http://status.msguides.com.
Because the number of daily clients is too big and still increasing over time, so the server can also be stuck at times. You can check and see if the server is overloaded or not here: http://status.msguides.com.
To check if the port 1688 is open, you can use the telnet command on windows or use this online port check tool in simpler way
====================================================================
How do I troubleshoot KMS activation issues?
1. Check you Internet connection
- Open the Start Menu.
- Type in cmd.
- Double click on Command Prompt.
- In Command Prompt window, enter ping google.com -n 25 .
Sometimes the error shows only because the internet connection is spotty. If everything looks good, you can proceed with the next steps.
2. Check if the computer is activated
- On the KMS client, open System control panel.
- Search for Windows is activated message.
If it is not activated, you need to do this first and then proceed to activating your Office copy. Still having issues? Then see how to fix Windows activation errors.
Before activating your Office copy, we need to make sure that on the client computer, Windows is activated.
3. Check if you have more than 25 clients
- Open Command Prompt window as admin.
- Run slmgr.vbs /dli command to check if the threshold is met. Currently the threshold is 5 for Server editions and 25 for everything else.
4. Check if the client communicated with the host
On the KMS host computer, look in the Application event log for event ID 12290. Check this log for requests made by the client computer. If there are no requests, it means that the client could not communicate with the host.
5. Open the right port
- Run as administrator the Command Prompt.
- In the cmd window, enter slmgr.vb /dlv command.
- Look for Listening on Port.
Make sure that there are no firewall rules that block TCP traffic on the KMS port. The default port value is 1688. If you don’t know the port you can find that out on your host computer.
6. Configure DNS properly for multiple KMS hosts
- Make sure the all the computers are on the same Active Directory Domain Services domain.
- In the Active Directory Domain Service create a global security group.
- Add each computer running KMS in the newly created global security group.
- Set permissions to enable updates by members of this new group on the DNS server.
When using KMS, the host computer must be discoverable in your local network. The first host computer automatically publishes it’s existence when it creates a SRV record on the DNS server.
The rest of the hosts cannot change or update SRC if the DNS server is not configured properly.
7. Newly added computers do not increase the KMS count
- On the client computer, open the search bar.
- Type cmd.
- Right click on Command Prompt and select Run as administrator.
- In the Command Prompt window type sysprep /generalize to reset the client computer ID. If that doesn’t work, try slmgr /rearm.
Sometimes client computers look identical to the host and therefore it doesn’t count them as separate.
the connection to my kms server failed office 2019
the connection to my kms server failed office 2013
the connection to my kms server failed office 2016
the connection to my kms server failed office 365
the connection to my kms server failed office 2010
kms server failed windows 10
sorry your version is not supported windows 10
kms server windows 10
windows license activation event log
ping kms server dns
restart kms service
windows 10 kms key not activating
kms error 0xc004f074
0xc004c008 server 2019
microsoft kms traffic
kms not activating windows 7
event id 12290
kms event log
volume_kms_ws16 channel
bit ly downloadmsp 2013
windows 10 your version is not supported
kms activator not working
connect to kms server
kms dns
cannot activate office 2019
kms error 0xc004f074 server 2019
kms registry key windows 10
clear stored kms server
kms error 0xc004f074 office 2016
how to activate windows behind firewall
kms error 0xc004f074 server 2016
how to check kms license count
kms license status notification
check which kms server is being used
nslookup _vlmcs tcp
slmgr set kms server
kms testing
windows license activation event log
ping kms server dns
restart kms service
windows 10 kms key not activating
kms error 0xc004f074
0xc004c008 server 2019
microsoft kms traffic
kms not activating windows 7
event id 12290
kms event log
volume_kms_ws16 channel
bit ly downloadmsp 2013
windows 10 your version is not supported
kms activator not working
connect to kms server
kms dns
cannot activate office 2019
kms error 0xc004f074 server 2019
kms registry key windows 10
clear stored kms server
kms error 0xc004f074 office 2016
how to activate windows behind firewall
kms error 0xc004f074 server 2016
how to check kms license count
kms license status notification
check which kms server is being used
nslookup _vlmcs tcp
slmgr set kms server
kms testing
