RAS VPN Server no connection to clients whatsoever

TheStaticTurtle 96 Reputation points
2021-10-06T07:59:09.4+00:00

I currently testing the fesability of a VPN server using RAS on a test network.

Here is my test network in question:
Servers:

  • AD / DHCP/ NPS - 192.168.33.1
  • RAS - 192.168.33.2
    LAN dhcp range: 192.168.33.10 - 192.168.33.200
    Vpn static pool range: 192.168.34.11 - 192.168.34.254

I managed to get clients to connect and they are assinged an ip (lets say 192.168.34.11 for clientA), However, no one can ping anyone.
When a client connects, I can see that the RAS server gets an ip on 192.168.34.10

However, the client can't ping anyone in the .33 subnet nor the .34 including the server
The RAS Server is able to ping anyone in the .33 subnet but can't ping anyone in the .34 subnet

I feel like this is a routing issue but I have 0 clue where to look, here is my routing table on the RAS Server:
138083-image.png
And here is The routing table of a client connects to the VPN via a mobile hotspot
137920-image.png

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,621 questions
0 comments No comments
{count} votes

Accepted answer
  1. TheStaticTurtle 96 Reputation points
    2021-10-13T13:42:14.433+00:00

    So I found the issue a while ago, because I could open ports directly on my router I had to do some wierd port forwarding with ssf, I didn't think that it would pose an issue but it turns out that running it directly on the RAS server will not work because it won't accept connections from localhost

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Limitless Technology 39,511 Reputation points
    2021-10-07T09:54:01.13+00:00

    Hello @TheStaticTurtle ,

    Thank you for your question.

    If your Always On VPN configuration is failing to connect clients to your internal network, the cause is likely to be an invalid VPN certificate, incorrect NPS policies, or problems with client deployment scripts or in Routing and Remote Access.

    Access the link below to see the different ways to fix this type of problem:

    https://learn.microsoft.com/en-us/windows-server/remote/remote-access/vpn/always-on-vpn/deploy/always-on-vpn-deploy-troubleshooting

    https://learn.microsoft.com/en-us/windows-server/remote/remote-access/vpn/always-on-vpn/deploy/vpn-deploy-ras

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

    If the answer is helpful, please vote positively and accept as an answer.

    0 comments No comments