# Inter-client communications not working, not able to ping between connected clients

**URL:** <https://forum.pritunl.com/t/inter-client-communications-not-working-not-able-to-ping-between-connected-clients/636>\
**Category:** Pritunl VPN\
**Created:** [December 20, 2022, 9:50pm UTC](https://forum.pritunl.com/t/inter-client-communications-not-working-not-able-to-ping-between-connected-clients/636 "2022-12-20T21:50:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![atwskris](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/a/bc8723/32.png) [@atwskris](https://forum.pritunl.com/u/atwskris)\
**Post date:** [December 20, 2022, 9:50pm UTC](https://forum.pritunl.com/t/inter-client-communications-not-working-not-able-to-ping-between-connected-clients/636/1 "2022-12-20T21:50:22Z")

</div>

Hi!

We are unable to ping between connected clients on the same host. We can receive a ping back from the GW on the subnet ( .1 ) but nothing else.

The inter-client routing is enabled and looking in the docs there is an option for inter-client communication which doesn’t appear to be available.

Is there additional settings or FW rules I would need in place to support this?

Thanks!  
Kris

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [December 21, 2022, 6:15pm UTC](https://forum.pritunl.com/t/inter-client-communications-not-working-not-able-to-ping-between-connected-clients/636/2 "2022-12-21T18:15:13Z")

</div>

This may be an issue with firewalls configured on the client operating system.

---

<div class="post-metadata">

**Author:** ![atwskris](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/a/bc8723/32.png) [@atwskris](https://forum.pritunl.com/u/atwskris)\
**Post date:** [January 8, 2023, 8:47pm UTC](https://forum.pritunl.com/t/inter-client-communications-not-working-not-able-to-ping-between-connected-clients/636/3 "2023-01-08T20:47:45Z")

</div>

SO we have turned off all of the firewalls and it still not working as expected.

However we did look at the TAP Adapter after we found that ipconfig was retuning a 169 ip address. Once we statically set teh ip address of the vpn then we were able to ping both directions. We could ping the GW both direction at all times.

Not sure the lost ip is because of the bypass secondary authentication however that was the only difference between the 2 profiles.

Even after setting it staticly on the device, once it disconnected and reconnected it would lose the ip at random.
