5191 questions

6344 answers

10170 comments

6278 members

0 votes
101 views 0 comments
by

Dear all,
I have configured an OpenVPN Access Server on Microsoft Azure and on the same network there is a windows machine

Access Server
There is the public (static) address of the 20.61.113.145
and the internal is 10.0.0.5/20

Windows Machine
internal address 10.0.0.4/20

VPN Client network
172.28.224.0/24

These are the configuration of a connected client

Connection-specific DNS Suffix . :
Link-local IPv6 Address : fe80::8561:b59a:9035:392d%16
IPv4 Address. : 172.28.224.130
Subnet Mask  : 255.255.255.128
Default Gateway:
I don't get the subnet mask in the beginning. I would have expected 255.255.255.0
From this client I can connect to 10.0.0.4 by NAT
What I would be able to reach is the opposite, that means, being able from 10.0.0.4 machine to RDP the VPN Client.
I have set up in VPN Settings Routing:
Should VPN clients have access to private subnets (non-public networks on the server side)? Yes, using routing
Specify the private subnets to which all clients should be given access (one per line): 10.0.0.0/20
In the user settings:
Select addressing method:Use Routing
Allow Access To these Networks: 10.0.0.0/20
Allow Access From: [checked] all server-side private subnets
Allow Access From: [checked] all other VPN clients
But I cannot connect in any side. The only machine that pings everything is the Access Router that can ping 10.0.0.4 and 172.28.224.130
I have read an article that tries to give instruction:
https://openvpn.net/vpn-server-resource ... e-network/
But I get nowhere.
Anyone was successful in Routing traffic from the OpenVPN Local Network to the the Clients network?
 

1 Answer

0 votes
by
Hello,

Regarding this query of yours may i know if there is any usage of our RUT device because from the given information your issue is on your Microsoft Azure OpenVPN access server and Windows Machine in this case the RUT240 is just giving internet to the windows machine right?. We cannot provide you support regarding this because the said platform are 3rd party platforms that is supported by our Teltonika networking products.

Kindly correct me if i am wrong.

Hope it helps.

Regards,
Jerome