About SAugustin

About 3 weeks ago, our company started rolling out the Lenovo L14 model to replace our Dell 5480 models. The laptops were sent out to a couple of remote users and soon after, we started getting complaints that the users couldn't start or accept meetings on their zoom app or even browse the zoom.us website. We do have split tunnel configured by (app & domain) for zoom, and they worked fine on our, Dells, MacBook's and other vendors., so we knew that the configs were correct. We even did traceroutes, Packet captures and added all the Zoom IPs in the split tunnel exclude access route and they all confirmed that the traffic was not going through the tunnel, so split tunnel was working as configured. Even a brand new out-the-box Lenovo L14 still didn't work with split tunnel enabled. After an extensive process of elimination with drivers and services.The problem was an Intel service called "Intel Connectivity Network Service". The service is part of Intel’s Performance Enhancement Suite. When we disabled this service. Zoom started working again with split tunnel enabled.              ... View more

wanted to know if anyone has ever experienced this issue. recently configured a new Vsys "Vsys6" which was successfully added to the correct Template_stack and device groups. everything worked fine for 2-3 weeks, however last night after adding 2 Sec.policies to the new Vsys. the commit failed. FYI for security i've edited the zone names and policy name.     . In VSYS vsys5 from zone "zone name" of type unknown and to zone "zone name" of type unknown are incompatible in security rule "rule name" . In VSYS vsys5 from zone "zone name" of type unknown and to zone "zone name" of type unknown are incompatible in nat rule "rule name" . In VSYS vsys5 from zone "zone name" of type unknown and to zone "zone name" of type unknown are incompatible in nat rule "rule name" . In VSYS vsys5 from zone "zone name" of type unknown and to zone "zone name" of type unknown are incompatible in nat rule "rule name" . Configuration is invalid It goes on for a couple more rules where the zone or rule name will change.   I've noticed that on the PAN, the Vsys# does not match the name"description" from the Vsys# name"description" on the local boxes. for example on the PAN Vsys5 is named blue and Vsys6 is yellow, but on the local box Vsys5 is Yellow and Vsys6 is blue. I've tried pushing the stack to the boxes but that didnt work, tried reverting but that didn't work either.       ... View more