Overview - Pulse Secure



Pulse Secure VPN:Troubleshooting speed concernsAshur KanoonLate update: July 19, 2018OverviewThis document will help outline a way to troubleshoot speed concerns. Typically, you’ll want to try this from home. The output below is when I am trying this from our corporate office and I’ll be VPNing into our demo environment which is at a colo. The speed of the demo environment is known to be slower so we expect the speed to drop at bit, but not significantly. We do not have split-tunneling configured. If you do, your results will vary.Troubleshooting StepsFirst, get a baseline without VPN.Get your local external IP address by googling “What’s my IP”:My non-VPN IP show 50.236.192.xGet your non-VPN speed:First by googling “speed test” and use the Google tool developed my M-LabSpeed result is 65.1 Mbps download / 89.8 Mbps uploadGet another baseline from Not that after VPN, the “local” server chosen may be differentThe non-VPN server discovered is Mimosa Networks in Santa Clara, CASpeed result is 64.78 Mbps download / 81.64 Mbps uploadNotice the difference is result alreadyGet an understanding of the route used – to for example:The above will help you determine if there are other hops in the path that may be an issue.To help better understand where issues may be, it is important to understand possible traffic flows and where issues may exist:Non-VPN traceroute hops: Your home network > Your ISP > The Internet > The destinations ISP > The destinations Network > The Server… and back.Note that the “and back” may be a different path back.VPN traceroute hops: Your home network > Your ISP > The Internet > Your Corporate ISP > Your Corporate VPN (PCS) > Your Corporate network > The destinations ISP > The destinations Network > The Server… and back to the VPN and then back to your computer.Again, note that the “and back” may be a different path back.After VPN, the issue may not be between you and PCS, it may be something else – see the “VPN traceroute hops” flow above. Now, try again after connecting to VPN.Note that speeds are different at different locations, so you may be connecting to something with slower internet.Connect to VPN, ideally a connection without split-tunneling so that the traffic is all going over the VPN tunnel. Also, note if you are connecting via ESP or SSL.Find your IP address now as outlined above. My post VPN public IP address is 64.13.174.2Rerun the two speed tests:The google speed test didn’t run because we block certain ports on the firewall between PCS and the internet.The test gave us results: 71.40 download / 108.02 uploadThese results were actually better than the non-VPN which wasn’t really expected. However, the colo has much faster speeds so something in the non-VPN path was preventing higher speeds. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download