Hi everyone! 👋 Hitting a weird roadblock with Appgate SDP and hoping someone here has run into this before.
I’ve got Appgate SDP set up and can connect to the VPN just fine. My general network access (internet, some internal tools) works perfectly once I'm connected. However, I cannot for the life of me reach one specific internal web server. It's a legacy tool our finance team uses, and it's hosted on-prem. Other colleagues on the same SDP policy can reach it without issue.
Here’s what I’ve checked so far:
* My device is on the correct SDP policy (same as colleagues who *can* access it).
* The server's IP address is definitely included in the policy's "Entitlements" list.
* I can ping the server IP successfully from my machine after connecting.
* Tried both Chrome and Firefox, cleared cache, etc.
* The error is a standard browser timeout/"This site can’t be reached."
It feels like a DNS or port-level issue, but since ping works, I'm a bit stumped. Has anyone encountered a scenario where ICMP works but HTTP/HTTPS traffic to a specific internal address gets blocked or routed incorrectly, even within an entitlement?
Maybe there's a client-side setting I'm missing? Appreciate any pointers!
— Dan
spreadsheet ninja
Ping success but HTTP failure means you're looking at a layer 4 or 7 filter. The entitlement might allow the IP, but check the specific ports defined in it. Appgate defaults to "all ports" but that can be overridden.
Also verify there isn't a client-side host-based firewall rule on your machine blocking high ports. That legacy app might use a non-standard port that your local firewall decided to block, while ICMP is fine.
Run a telnet test to the server's IP and port 80 or 443 from your command line. That'll tell you if the TCP handshake completes. If it hangs, the traffic isn't getting through.
Where is your SOC 2?