GP Client IP/Route Assignment

Reply
Highlighted
L0 Member

GP Client IP/Route Assignment

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 :

 

(T3584) 03/08/16 13:04:49:394 Debug(2280):        Adapter friendly name is: Local Area Connection 6
(T3584) 03/08/16 13:04:49:394 Debug(2460): cmd = cmd /C netsh interface ip set address "Local Area Connection 6" static 172.28.6.17 255.255.255.255> "C:\Program Files\Palo Alto Networks\GlobalProtect\tmp.txt"
(T3584) 03/08/16 13:04:49:472 Debug(  95): Element not found.
(T3584) 03/08/16 13:04:49:472 Debug(  95):
(T3584) 03/08/16 13:04:49:472 Debug(  95):
(T3584) 03/08/16 13:04:49:472 Debug(2476): cmd = cmd /C netsh interface ip set dns "Local Area Connection 6" static 192.168.20.6 validate=no > "C:\Program Files\Palo Alto Networks\GlobalProtect\tmp.txt"
(T3584) 03/08/16 13:04:49:566 Debug(  95):
(T3584) 03/08/16 13:04:49:566 Debug(2476): cmd = cmd /C netsh interface ip add dns "Local Area Connection 6"  192.168.20.8 validate=no > "C:\Program Files\Palo Alto Networks\GlobalProtect\tmp.txt"
(T3584) 03/08/16 13:04:49:659 Debug(  95):
(T3584) 03/08/16 13:04:49:659 Debug(2513): cmd = cmd /C netsh interface ip set wins name="Local Area Connection 6" source = static addr = 192.168.20.6 > "C:\Program Files\Palo Alto Networks\GlobalProtect\tmp.txt"
(T3584) 03/08/16 13:04:49:769 Debug(  95):
(T3584) 03/08/16 13:04:49:769 Debug(2513): cmd = cmd /C netsh interface ip add wins name="Local Area Connection 6"  addr = 192.168.20.8 > "C:\Program Files\Palo Alto Networks\GlobalProtect\tmp.txt"
 
It looks like the netsh command is not properly setting the client IP and other settings as it is showing "Element not found" after running the netsh command. Any help would be greatly appreciated.
 
 
Thank you!

Accepted Solutions
Highlighted
L4 Transporter

Re: GP Client IP/Route Assignment

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

View solution in original post


All Replies
Highlighted
L4 Transporter

Re: GP Client IP/Route Assignment

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

View solution in original post

Highlighted
L0 Member

Re: GP Client IP/Route Assignment

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".

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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 Live Community as a whole!

The Live Community thanks you for your participation!