Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error while activating 0x80070000d #74

Closed
ghost opened this issue Sep 30, 2022 · 3 comments
Closed

Error while activating 0x80070000d #74

ghost opened this issue Sep 30, 2022 · 3 comments
Labels
help wanted Extra attention is needed

Comments

@ghost
Copy link

ghost commented Sep 30, 2022

kms actication the data is invalid 0x80070000d
im getting this error while trying to run my server on my local network (docker) and trying to activate on the same network.

i do know that it happens because i run server and client on the same computer and running the server on virtualbox fixed my issue

however,

  • i think docker can do bridge networking by himself * (without virtualbox).

so the question is: how to run server and client on the same computer using docker?

@simonmicro
Copy link

You don't. Because Docker will create a new Network Interface, which is marked as local in Windows. This way any communication over that interface will still be treated as "from the same machine". You could try to use Swarm and this way bridge it over?

@simonmicro simonmicro added the help wanted Extra attention is needed label Sep 30, 2022
@Matthew-Beckett
Copy link
Collaborator

You don't. Because Docker will create a new Network Interface, which is marked as local in Windows. This way any communication over that interface will still be treated as "from the same machine". You could try to use Swarm and this way bridge it over?

@simonmicro is there specific limitations in place to prevent the KMS protocol being usable over a local/loop back interface?

Is this an attempt to prevent you running a local KMS impersonator as this project does?

@simonmicro
Copy link

@simonmicro is there specific limitations in place to prevent the KMS protocol being usable over a local/loop back interface?

Something, something Windows?

Is this an attempt to prevent you running a local KMS impersonator as this project does?

Bingo. I see NO reason why Microsoft should implement this limitation otherwise!

@simonmicro simonmicro closed this as not planned Won't fix, can't repro, duplicate, stale Oct 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants