topic Re: Issues with GlobalProtect on Windows 10 1703 in General Topics

Issues with GlobalProtect on Windows 10 1703

arvesynd — Wed, 26 Apr 2017 08:36:22 GMT

Hi,

I recently had a collegue who installed Windows 10 1703, also called the Creators Update.

After the update GlobalProtect appears to be able to connect to the gatway, but it fails to retrieve an IP address and DNS servers from the firewall.

Have anyone else had this issue, and have anyone been able to find a solution?

I will try to have him do a reinstall of the GlobalProtect client and see if that resolves the issue.

Re: Issues with GlobalProtect on Windows 10 1703

bbilut — Wed, 26 Apr 2017 15:06:45 GMT

I went to 1703 on my home machine the day it was released and I have not had any problems with the 3.1.5 version.

Re: Issues with GlobalProtect on Windows 10 1703

BPry — Wed, 26 Apr 2017 15:36:29 GMT

What is your GP version; it could be that your version itself is having issues after the creators update due to it being older.

Re: Issues with GlobalProtect on Windows 10 1703

bbilut — Wed, 26 Apr 2017 15:46:23 GMT

3.1.5

Re: Issues with GlobalProtect on Windows 10 1703

BPry — Wed, 26 Apr 2017 17:57:14 GMT

Not yours Brad, @arvesynd's. Sorry probably should have specified.

Re: Issues with GlobalProtect on Windows 10 1703

arvesynd — Thu, 27 Apr 2017 06:11:37 GMT

We're currently running 3.1.6, I have also opened a support case with Palo Alto regarding this issue.

In the past we've seen issues with the localized names of ethernet adapters causing issues for GlobalProtect, and this could be related as it fails to do netsh on the interface.

I'll give an update as soon as I've heard back from Palo Alto.

(T6972) 04/26/17 09:24:40:925 Debug(3308): cmd = cmd /C netsh interface ip set address 5 static 192.168.0.190 255.255.255.255> "C:\Program Files\Palo Alto Networks\GlobalProtect\tmp.txt"
(T6972) 04/26/17 09:24:41:072 Debug( 118): 
(T6972) 04/26/17 09:24:41:072 Debug(3321): cmd = cmd /C netsh interface ip set dns 5 static 192.168.0.1 validate=no > "C:\Program Files\Palo Alto Networks\GlobalProtect\tmp.txt"
(T6972) 04/26/17 09:24:41:110 Debug( 118): 
(T6972) 04/26/17 09:24:41:110 Debug(1715): number of route is 2
(T6972) 04/26/17 09:24:41:110 Error(1747): SetIpForwardEntry(0.0.0.0) failed (The system cannot find the file specified.)
(T6972) 04/26/17 09:24:41:125 Error(1747): SetIpForwardEntry(192.168.0.1) failed (The system cannot find the file specified.)

Re: Issues with GlobalProtect on Windows 10 1703

arvesynd — Tue, 16 May 2017 10:47:38 GMT

This issue seems to have been a single incident, I have tried upgrading several other computers to 1703 without any issues.