Azure VPN P2S Platform 5 error

Question

Azure VPN P2S Platform 5 error

Mitchell Meadows 21

We have recently setup a Generation1 VPN Gateway using our AD Authentication. I have created an xml file for import, roughly 25 users for their P2S configuration. Utilizing the Azure VPN connection Client from the Windows store we are allowing them to install and import the file since we are 100% remote. I have a few users that are getting an error: "VPN Connection NoName could not be saved. Platform Error Code: 5" The xml is titled in case someone asks.

The error code is random, the same exact model machines with the latest updates (1/7/21) are not having the issue. We have attempted to manual enter the information, same error. We have created a totally new xml file from Azure, same error. Searching the web and this forum I have found no instance of this being reported.

I have attached a copy of the error from my user's error.

Accepted answer

0 additional answers

Your answer

Answer 1

GitaraniSharma-MSFT 50,096 Microsoft Employee Moderator

Hello @Mitchell Meadows ,

Issue description:
When attempting to connect to the P2S VPN using the Windows store client and AAD you receive the following error:
Vpn connection noname could not be saved. Platform error code: 5

Cause:
This is currently being caused when FIPS aka Federal Information Processing Standards is enabled via a group policy or similar. Disabling FIPS mitigates but some customers have a hard requirement to have this enabled.

How to check if FIPS is enabled:

Press Windows Key+R to open the Run dialog.
Type “gpedit.msc” into the Run dialog box (without the quotes) and press Enter.
Navigate to “Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options” in the Group Policy Editor.
Locate the “System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing” setting in the right pane and double-click it.
See if enabled or disabled.

Solution:
Disable FIPS (if possible).
Or manually install the following KB:
https://www.catalog.update.microsoft.com/Search.aspx?q=KB4577063

Post that reboot your machine and try to connect to PS VPN again and check if it connects successfully.

Kindly let us know if the above helps or you need further assistance on this issue.

----------------------------------------------------------------------------------------------------------------

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

Mitchell Meadows 21 Reputation points

2021-01-12T17:11:51.387+00:00

Thank you for that, however, the issue is when they attempt to IMPORT the XML file or enter the XML file in Azure VPN Client and save. They haven't even been able to connect to a VPN Gateway so I believe the issue is with the client.

We went ahead and attempted what you asked for and FIPS was already Disabled and the KB Article returned an error of "The update is not Applicable to your Computer".
GitaraniSharma-MSFT 50,096 Reputation points Microsoft Employee Moderator

2021-01-12T17:44:24.713+00:00

Hello @Mitchell Meadows ,

Yes, this has been an issue with few machines/clients and the error pops up while saving the config. The KB update that I suggested has fixed the issue for all impacted users. May I know what is the OS version of the machine where you are trying to install the KB?

Thanks,
Gita
Mitchell Meadows 21 Reputation points

2021-01-12T17:46:39.997+00:00

Hopefully this helps. We used the Windows 10 x64 msi.
GitaraniSharma-MSFT 50,096 Reputation points Microsoft Employee Moderator

2021-01-12T18:20:11.583+00:00

@Mitchell Meadows , thank you for the screenshot. I see the machine is at OS version 18363. The fix/KB update was released in 9C. And your machine/client needs to be on 20H1 or 19041 version or higher.
Please refer : https://learn.microsoft.com/en-us/windows/release-information/
https://blogs.windows.com/windows-insider/2020/04/16/getting-the-may-2020-update-ready-for-release/

Does this machine have the latest updates?
Mitchell Meadows 21 Reputation points

2021-01-13T20:11:28.56+00:00

This appears to be the fix. We upgraded the machines on PRO to the 20H2 update that was available and it allows import of the xml and it connects. Thank you for your help!
GitaraniSharma-MSFT 50,096 Reputation points Microsoft Employee Moderator

2021-01-15T04:32:31.78+00:00

Thank you for the update @Mitchell Meadows . Glad to hear that the issue is now fixed.

Regards,
Gita

Share via

Azure VPN P2S Platform 5 error

0 additional answers

Your answer