Azure-docs: Add details on this error

[danmyhre]

Seems to be a lot of people getting this
Server did not respond properly to VPN Control Packets. Session State: Key Material sent

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 88bc02bb-dec3-efb4-6948-e7478cd61c6b
• Version Independent ID: 6c84e886-215d-51ed-804a-f14561814a52
• Content: VPN Gateway: Troubleshoot VPN client - Azure AD authentication
• Content Source: articles/vpn-gateway/troubleshoot-ad-vpn-client.md
• Service: vpn-gateway
• GitHub Login: @cherylmc
• Microsoft Alias: cherylmc

[SubhashVasarapu-MSFT]

@danmyhre , We are looking into this query and will update you as soon as possible.

[SubhashVasarapu-MSFT]

@danmyhre , We have assigned this issue to the content author for updating the document accordingly. @cherylmc , Could you please provide your insights here?

[cherylmc]

reassign:anzaman

[petehauge]

I ran into this error and can't find a way to resolve it. Any pointers or help on how to handle this? I followed all the steps and can't connect the Azure VPN client to my gateway. Thanks in advance for any help!

[danmyhre]

In my scenario, it turned out to be that the "/" was missing from the end of the issuer. Make sure both the "Tenant" field and the "Issuer" field both end with "/"

[petehauge]

Thanks @danmyhre - that was the issue, you're a hero! I appreciate the help!

[joeweale]

Worthwhile noting I had the same issue and @danmyhre suggestion resolved it.

Needs to be set correctly in the Set-AzVirtualNetworkGateway powershell cmd (not just the client config)

[serverhack74]

This error is still ocurring, even with the slash "/" behind the Issuer URI.

Any solution?

[zyfaulkingham]

Receiving same error even after adding "/ " to Issuer and Tenant.

@serverhack74
@danmyhre
Edit: Fixed the issue, the Issuer did not have the DirectroyID with a "/" at the end. Saved settings and re-downloaded the client.

Imported within the Azure VPN client, and it worked!

[serverhack74]

Yes, I have added the "/" to the Issuer and Tenant:

This is the results:

[serverhack74]

Any clue?

[cdtsushant]

Any clue?

no can you find out any solution on this

[cdtsushant]

Receiving same error even after adding "/ " to Issuer and Tenant.

@serverhack74
@danmyhre
Edit: Fixed the issue, the Issuer did not have the DirectroyID with a "/" at the end. Saved settings and re-downloaded the client.

Imported within the Azure VPN client, and it worked!

sorry but I did follow the same procedure but it didn't Work

[cdtsushant]

is this azure VPN client works for only windows NOS or Windows COS also...i was try every possible way to find out the solution but yet things worked

[StefanWittmann]

I ran into the same error, my mistake: token issuer id and tenant id were not identical

[serverhack74]

Token issuer ID and Tenant ID shouldn't be identical, should it? Both have differents server URIs, for tenant ID is https://login.microsoftonline.com/XXXXXX and Issuer is https://sts.windows.net/XXXXXX

Otherwise I have checked putting the same on both boxes and the results are the same: still not working

[StefanWittmann]

I only referred to th ID, not the complete URI

at first my faulty config was something like this:
https://login.microsoftonline.com/XXXXXX/
https://sts.windows.net/YYYYYY/

but since i changed it to:
https://login.microsoftonline.com/XXXXXX/
https://sts.windows.net/XXXXXX/
it worked

[serverhack74]

That's the config I have:

[serverhack74]

and it isn't working

[Dylan-J]

@serverhack74 - have you replicated the configuration in the azurevpnconfig.xml file? I was able to replicate when the trailing / isn't added to the xml file too.

[anzaman]

a note was added to the documentation

please-close

[vibs1983]

Is anyone else still having this issue? We have a hybrid Azure AD environment and it appeared the time on a few of our client devices skewed which caused this error. To fix we changed the time source to an external ntp server rather than the default nt5ds.