- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
I ran a packet capture on PAN to try and figure out an intermittent problem with one of my GP 126.96.36.199 users (Windows, Surface Pro) where certain web based or internal applications will just start working. The external are Outlook O365, Teams for example. If he disables GP then everything starts working again. We verified he's connected to VPN during these periods of failure and narrowed to a DNS problem. When I ran a pcap on the PAN, I could see that his system was first sending a query for the expected domain
with the host - say scooper-p01.acme.com. But then the next packet would be trying to resolve scooper.hdcl.fl.comcast.net.
So while his system was clearly connected to GP VPN (I couldn't have grabbed the packets otherwise), the presumed suffix
was changing one DNS lookup to another. Has anyone seen anything like this? Any recommended fix?
Since 5.2.5 is relatively older at this point and a brief glance through the latest release notes show a few suffix fixes alongside split tunnel fixes that saw split DNS requesting DNS across both interfaces, I would highly recommend allowing this user to just try running 5.2.12 and seeing if they run into the same issue. It's possible that they're running into a bug that has been fixed in a later release, and since 5.2.12 fixes the OpenSSL infinite loop vulnerability I would recommend getting it deployed to everyone anyways.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!