--- title: "Client to client connectivity checklist" slug: "client-client-connectivity-checklist-v7-0" description: "Optimize your AppGate ZTNA setup with essential network settings, IP pools, and routing for seamless client-to-client communication." tags: ["Troubleshooting", "Connectivity"] updated: 2026-06-05T19:17:37Z published: 2026-06-05T19:17:37Z canonical: "support.appgate.com/client-client-connectivity-checklist-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Client to client connectivity checklist The AppGate ZTNA system relies on the wider network to ensure traffic can pass successfully from one client to another client. In addition to configuring policies and entitlements, various network-related settings are defined in the AppGate ZTNA system such as DNS settings and the client IP address pool. The following sections describe the UI locations and actions required to route your application traffic successfully. Refer to [troubleshooting user and device access](/v1/docs/troubleshooting-user-and-device-access-v7-0) if you experience access issues. #### System > Appliances > Function > - **System TLS Connection > Allowed Sources:** if this list is empty, no inbound client connections str allowed to the appliance. See [Adding a new appliance](/v1/docs/adding-a-new-appliance-v7-0) for more information. #### Identity > IP Pools - For IP telephony, consider having the IP pools share the address space of a L2 VLAN with the upstream routers to the internal network where the IP telephony Controllers and non-AppGate ZTNA users reside. - **Create an IP Pool**: provide a range of IPs large enough for all client-to-client users on the virtual tunnel interfaces. Edit the default IP pool if required. See [IP pools](/v1/docs/ip-pools-v7-0) for more information. #### System > Sites IP telephony systems typically make UDP connections directly between clients. They rely on knowing the IP address of the clients, so disable source NAT. The L2 network must also support ARP, because if two clients connect to different Gateways, their traffic routes across the protected network between the Gateways. - **General > Tunnel Traffic**: Select *Disable Source NAT on Gateways*. If there is only one Gateway, source NAT can be enabled or disabled, but enabling it may not work correctly for IP telephony. See [Configuring Sites](/v1/docs/configuring-sites-v7-0) for more information. Because IP telephony can establish any client-to-client combination, subnet-based routing is a suitable option. The subnet matches the IP pool and directs traffic destined for any other client to the virtual tunnel interface. - **Client Routing > Subnet Based Routing**: defines static routes that include the IP pool used by the other clients. See [Configuring Sites](/v1/docs/configuring-sites-v7-0) for more information. #### Access > Entitlements IP telephony may require TCP up entitlements to the IP telephony Controllers. UDP up and down entitlements are required for the IP pool address range for client-to-client calls. UDP up and down are also required for all office networks where non-AppGate ZTNA users who may make or receive calls are located. - Actions: At a minimum, set an allow action in each direction (up and down) covering the tunnel IP pool of the other clients. > [!NOTE] > **NOTE** > > A new API resolves the IPs for a given DN (user). You can use it in combination with [entitlement scripts](/v1/docs/entitlement-scripts-v7-0) to allow a user to connect back to another computer also used by that same user.