Azure Radius Point to Site VPN

Greg Thomas 121 Reputation points
2021-05-26T13:46:06.443+00:00

Hi,

I've been following a number of walkthroughs on setting up a Point to Site VPN with Radius in Azure.

We seem to have things setup properly, but our users cannot connect via VPN. Unfortunately, when we check the client logs, we see no errors...

[cmdial32] 9:54:54 03 Pre-Init Event CallingProcess = C:\WINDOWS\system32\rasautou.exe
[cmdial32] 9:55:21 04 Pre-Connect Event ConnectionType = 1
[cmdial32] 9:55:21 06 Pre-Tunnel Event UserName = buser@GuillaumeB .mc Domain = DUNSetting = bfc80066-4b44-4072-bb6b-ab979140f85e Tunnel DeviceName = TunnelAddress = azuregateway-3727CDBA-0436-458C-9216-73A5BC27D215.vpn.azure.com
[cmdial32] 9:57:19 21 On-Error Event ErrorCode = 619 ErrorSource = RAS

This is all we get (NOTE: not the real azuregateway address).

Is there somewhere on the Radius or on the Gateway we can troubleshoot errors?

Currently we have one Radius server up and running with one policy. The Radius server has the IP address of our VPN Gateway configured on it and we have a group of users who are allowed to VPN in.

We have tried with MFA and non-MFA enabled users.

Whereabouts can we go about troubleshooting things?

Thanks.

Azure VPN Gateway
Azure VPN Gateway
An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
1,796 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. GitaraniSharma-MSFT 50,096 Reputation points Microsoft Employee Moderator
    2021-05-28T16:23:01.86+00:00

    Hello @Greg Thomas ,

    Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

    I see the below error in the log you provided:
    [cmdial32] 9:57:19 21 On-Error Event ErrorCode = 619 ErrorSource = RAS

    Error 619 occurs when VPN gateway could not reach RADIUS NPS server. And the cause for this error is NPS firewall actively ignoring local firewall rules (which were configured to accept incoming rules for ports 1812,1813,1645 and 1646).
    Check your Firewall rules and make sure the allowed rules are enabled for all profiles. And make sure that the Windows Firewall rules for these ports shows "Any" under the Program column. If it is not "Any", then you could try adding custom rules for the same ports(1812,1813,1645 and 1646) and allow them again in your Firewall. You can also test by disabling the Windows Firewall.

    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.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.