SmartConsole shows an active site-to-site tunnel, but a branch client cannot open an application at the other site. Record one approved test flow with its timestamp, source, destination, and service. Compare the same connection attempt on both peers.
Verify how each peer classifies the flow. Check whether the local and remote addresses belong to the intended VPN domains. Compare both sides’ definitions, including subnet masks and any network objects introduced during a recent change. For a route-based design, check the intended tunnel interface and routing instead of assuming the domain-based forwarding model.
Check policy and direction. In SmartConsole Logs & Monitor, look for the test’s action, matching rule, gateway, and VPN information where available. Compare translated addresses if NAT applies. If the initiating gateway sends the flow through the tunnel but the destination sees nothing, inspect the remote gateway’s receipt and policy evidence. If the destination sees the request and answers, follow the reply toward the initiating subnet.
Worked example. Existing branch devices work, while a newly added subnet fails. The application’s logs show no connection from the new subnet, and the Check Point gateway’s classification differs between old and new sources. The engineer compares the approved encryption domains and finds the new subnet missing. After the approved update, a fresh test matches the intended VPN path and the application returns a response. Verify existing subnets as well.