Clients cannot ping each other

Post Reply
MicahZoltu
OpenVpn Newbie
Posts: 2
Joined: Tue Dec 31, 2019 2:51 pm

Clients cannot ping each other

Post by MicahZoltu » Tue Dec 31, 2019 3:33 pm

I have an OpenVPN Access Server running in the cloud using mostly defaults. I can connect to the internet through it and have verified that traffic is correctly routed through it (tracert shows OpenVPN gateway as first hop). Its configuration is mostly default other than adding a couple users and enabling Inter-Client Communication.

However, my clients cannot see each other. When I try to ping their OpenVPN assigned IP the request times out. A tracert shows the route goes through the OpenVPN gateway but it dies there.

I have tried flipping every switch I can think of in the OpenVPN Access Server GUI and have reset it to defaults several times but nothing I do seems to have any effect. One thing of potential interest is that each client seems to have its own gateway, they don't end up on the same subnet (they each end up on a subnet with one address).

MicahZoltu
OpenVpn Newbie
Posts: 2
Joined: Tue Dec 31, 2019 2:51 pm

Re: Clients cannot ping each other

Post by MicahZoltu » Tue Dec 31, 2019 3:56 pm

FWIW, I have searched this forum, followed every tutorial I could find, read the instructions, etc. Coming here for configuration assistance is my last effort.

Both clients are Windows, OpenAccess server is running on Linux.

luckman212
OpenVPN User
Posts: 39
Joined: Fri Jun 10, 2011 12:03 am

Re: Clients cannot ping each other

Post by luckman212 » Wed Jan 08, 2020 1:13 pm

Should be no problem as long as you enable the "Inter-Client Communication" option under Advanced VPN Settings... did you do this?

Image

novaflash
OpenVPN Inc.
Posts: 1034
Joined: Fri Apr 13, 2012 8:43 pm

Re: Clients cannot ping each other

Post by novaflash » Mon Jan 13, 2020 6:22 am

And since this is on Windows, try turning off the firewall.

Lepofsky
OpenVpn Newbie
Posts: 1
Joined: Tue Feb 11, 2020 3:42 pm

Re: Clients cannot ping each other

Post by Lepofsky » Tue Feb 11, 2020 3:44 pm

I think routing may be required to communicate with clients; the defaults are to use NAT. I have that same problem, but have to use NAT to connect via Peering Connections to different VPCs in AWS. So, it's one or the other for me.

Post Reply