About millerh1

No -- but it does happen for me at certain times of day. Particularly around 9am, 12pm, and 4-5pm.    Anyways, the new modem and router seems to have fixed it! Still would like to know why this is happening since I don't think "buy a new modem/router" is going to be great solution for most people. ... View more

Still looking into the problem. They asked me to get a new modem/router and see if the problem goes away -- currently testing that now. ... View more

@MP18and @rmikalauskas  Yes we are currently in contact with them. They are still reviewing our logs and we are looking at different possible causes.  ... View more

Hi @henrique.correia -- The drivers are up to date on the client machine (Acer laptop).    I switched to a different network that has a static IP address and no router (modem only). It seems to be performing fine on this new setup -- but it's not clear why that would make a difference. The original router is a 2017 model Arris Surfboard and I don't see any issues with normal internet connectivity -- the issue starts only when I am connected to GlobalProtect.  ... View more

Hi @SteveCantwell thank you for the reply! We have no opened a ticket with support and I will be sure to let you know what they say. If nothing else, I'll try downgrading to 5.1.5 and see if that helps!   ... View more

Thank you so much for the advice!   I have tried the MTU check:   C:\Users\mille>ping -l 1373 -f 8.8.8.8 Pinging 8.8.8.8 with 1373 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 8.8.8.8: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Users\mille>ping -l 1372 -f 8.8.8.8 Pinging 8.8.8.8 with 1372 bytes of data: Reply from 8.8.8.8: bytes=68 (sent 1372) time=131ms TTL=117 Reply from 8.8.8.8: bytes=68 (sent 1372) time=123ms TTL=117 Reply from 8.8.8.8: bytes=68 (sent 1372) time=131ms TTL=117 Reply from 8.8.8.8: bytes=68 (sent 1372) time=125ms TTL=117 Ping statistics for 8.8.8.8: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 123ms, Maximum = 131ms, Average = 127ms   It appears that my minimum MTU may also be 1372, just like you showed.    It sounds like you are advising that I try lowering the MTU on the PanGP adapter from 1400 (the default) to something below 1372. I lowered it to 1300 by identifying the index of the GP adapter (idx 18 on my computer) and then setting the mtu for that adapter to 1300. I did this for ipv4 (shown) and ipv6.   C:\Windows\system32>netsh interface ipv4 show interfaces Idx Met MTU State Name --- ---------- ---------- ------------ --------------------------- 1 75 4294967295 connected Loopback Pseudo-Interface 1 11 70 1500 disconnected Wi-Fi 22 25 1500 connected Ethernet 17 25 1500 disconnected Local Area Connection* 1 7 25 1500 disconnected Local Area Connection* 2 18 1 1400 connected Ethernet 2 23 5000 1500 connected vEthernet (WSL) C:\Windows\system32>netsh interface ipv4 set interface 18 mtu=1300 Ok.   However, the disconnect events still persist with the same debug message: (T30932)Debug(1564): 01/12/21 08:33:05:755 Received a virtual interface packet with fragment 0x2000 (T30932)Debug(1564): 01/12/21 08:33:05:761 Received a virtual interface packet with fragment 0xA0 (T30932)Debug(1564): 01/12/21 08:33:10:557 Received a virtual interface packet with fragment 0x2000 (T30932)Debug(1564): 01/12/21 08:33:10:557 Received a virtual interface packet with fragment 0xA0 (T30932)Debug(1564): 01/12/21 08:33:20:121 Received a virtual interface packet with fragment 0x2000 (T30932)Debug(1564): 01/12/21 08:33:20:121 Received a virtual interface packet with fragment 0xA0   I will do my best to contact support -- I do not know if our institute has a support account, however.    Do you have any other suggestions regarding what might be causing this?    Thank you for your time, Henry ... View more