- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
03-10-2016 08:28 AM
Hello,
I am having an issue with some clients when they connect remotely via the global protect client. Everything is working on most of the PC's who try to connect, but some users are receiving the issue. Here is the log of where the problem occurs :
03-10-2016 08:55 AM
Hi,
I also have the same problem with the GP v3 client. Apparently, there is a bug in the netsh command that appears mostly when you have multiple network interfaces. The solve the problem, the client should use the numerical ID of the interface instead of the name "Local Area Connection 6". So the bug is in the Microsoft code, but it's up to Palo Alto Networks to work around the problem. In the meantime, you can try renaming the interface to something shorter and without spaces or special characters.
I already opened a case about this problem, and you should do the same to make sure they give it a higher priority.
Regards,
Benjamin
03-10-2016 08:55 AM
Hi,
I also have the same problem with the GP v3 client. Apparently, there is a bug in the netsh command that appears mostly when you have multiple network interfaces. The solve the problem, the client should use the numerical ID of the interface instead of the name "Local Area Connection 6". So the bug is in the Microsoft code, but it's up to Palo Alto Networks to work around the problem. In the meantime, you can try renaming the interface to something shorter and without spaces or special characters.
I already opened a case about this problem, and you should do the same to make sure they give it a higher priority.
Regards,
Benjamin
03-10-2016 08:59 AM - edited 03-10-2016 09:32 AM
Thank you! Having the clients rename the interface worked. I appreciate the help.
I'm not sure if any developers read this forum, but it seems like an easy fix for this issue on the Palo Alto end would be to give the interface a generic name like "GPInterface" when the PANGP Virtual Ethernet Adapter is installed rather than letting windows name it as "Local Area Connection x".
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!