This is happening because the redirectproxyserver.dll is not handling or parsing the HTTP/S request as expected as it is missing in the request.
This issue has been raised to our engineering team to get a fix in place. As a temporary workaround, the following line <SymNetDrv>0</SymNetDrv> can be added under the <roaming_agent> line found at the top of the agentconfigure.xml file, which is located under C:\Program Files (x86)\Symantec.cloud\Smart Connect then restart the Symantec Web Security.cloud Smart Connect service.
This would allow the users to access the internet. This setting will disable the usage of redirectproxyserver.dll file which allows the communication between Smart Connect and Windows MetroApps, therefore the users would not be able to use any of the MetroApps that need access to the internet in the mean time.
NOTE: These instructions are for individual computers running Smart Connect 2.0. Changes through Group Policy will require the administrator to know the equivalent area within GPO to make the changes.
Subscribing will provide email updates when this Article is updated. Login is required.