question

dotandy avatar image
0 Votes"
dotandy asked dotandy answered

Can't activate Windows in Azure using BYOIP public IP

I can't seem to be able to activate any Windows instances in Azure (using the Azure provided licence, rather than HUB).

I believe the problem is that the instances are all using BYOIP public IP addresses, so when the instance tries to contact kms.core.windows.net it is failing to authorize the activation because the public IP isn't from the standard Azure range.

If I change the instance to use a public IP in the Azure range the activation then proceeds immediately.

Is this an issue within Azure, or do I need to do anything different when using BYOIP addresses?

azure-virtual-machines
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

pituach avatar image
0 Votes"
pituach answered dotandy commented
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I can contact the KMS fine it seems, here's an example:

Test-NetConnection kms.core.windows.net -Port 1688

ComputerName : kms.core.windows.net
RemoteAddress : 23.102.135.246
RemotePort : 1688
InterfaceAlias : Ethernet
SourceAddress : 10.0.1.12
TcpTestSucceeded : True

It seems that when using BYOIP the KMS doesn't know that the source IP addresses have been provisioned in Azure.

0 Votes 0 ·
Dev073 avatar image
0 Votes"
Dev073 answered Dev073 commented

Hi,

Seems azure only accepts activation request from azure public IP address. Hence the failure. But I couldn't fine any documented known issues.

are you able to psping to the KMS address ? steps given in @pituach response.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

As above the connection to the KMS seems fine - here's a PSPing too:

.\psping.exe kms.core.windows.net:1688

PsPing v2.10 - PsPing - ping, latency, bandwidth measurement utility
Copyright (C) 2012-2016 Mark Russinovich
Sysinternals - www.sysinternals.com

TCP connect to 23.102.135.246:1688:
5 iterations (warmup 1) ping test:
Connecting to 23.102.135.246:1688 (warmup): from 10.0.1.12:49893: 105.49ms
Connecting to 23.102.135.246:1688: from 10.0.1.12:49894: 105.80ms
Connecting to 23.102.135.246:1688: from 10.0.1.12:49896: 105.78ms
Connecting to 23.102.135.246:1688: from 10.0.1.12:49899: 105.11ms
Connecting to 23.102.135.246:1688: from 10.0.1.12:49904: 105.26ms

TCP connect statistics for 23.102.135.246:1688:
Sent = 4, Received = 4, Lost = 0 (0% loss),
Minimum = 105.11ms, Maximum = 105.80ms, Average = 105.49ms

It's all direct, there's no split tunnel. Using the Network Watcher Next Hop tool it is showing:

Result
Next hop type
Internet

0 Votes 0 ·

Hi, I think its the issue with BYOIP and KMS is rejecting due to non-azure IP. Please riase a case with MS to get deeper clarification.

0 Votes 0 ·
dotandy avatar image
1 Vote"
dotandy answered

Just to add an update to this.

The Azure networking team investigated this, and they have a roadmap for a permanent resolution to this issue. So shouldn't be a problem going forward.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.