Yes, the problem is with the server/host. KMS clients activate against kms hosts. Clients all use same keys, found on the MS website, and these are not being blocked. When kms hosts are built using leaked host keys, then it is a problem. MS can detect which host a client has used for activation, and mark them non-genuine, if activated against a bad host.
Everybody and his brother has been doing this the last couple of months, i.e. setting up kms host vm's using leaked activation tokens, then placing them on the internet at xxxxx.no-ip.org for others to use. The blocking is based on an epid returned to the client by the host, ip address and dns doesn't matter at all. For windows 8, they are still getting away with it, since genuine testing/validation has not yet been implemented.
Yes Vymrdal, and don't think I forgot who tipped me on that one!! All my XP systems thank you!:flowers2:
I guess time will tell. A lot has changed in the activation process since XP. I doubt M$ would let this one go. But who knows. ~MC
Dns Guys, mpa.one.microsoft.com is just a Host name that resolves to a public IP. If I was MS I would change the Host name (after all microsoft.com is the one that counts...........if you understand DNS) and you would be blocking something that does not exist anymore. They will get you with the new one. I am not trying to be negative but as Daz has mentioned in other posts, this time we face a difficult one, like no one before. Cheers