Users accessing internet via WSS using SEP WTR agent
Users working fine until PAC file change
After PAC file change pushed out to group of users, all users in group could not access any internet resources
SEP WTR agent sent authentication traffic to one WSS pod, and the explicit Web requests to another.
Apply SEP WTR update 126.96.36.1993.
A PCAP from the workstation using Wireshark shows what is happening
- user tries to access http://www.example.com via GGBLO (188.8.131.52)
- user is asked to authenticate by sending a CONNECT request to client-id.wss.symantec.com via GGBLR (different data center - 184.108.40.206)
- user is redirected back to original URL, again going to GGBLO
Because of a SEP communication issue between the authentication and proxy engines, the authentication engine failed back to the last working IP address which was the one accessed prior to the PAC file change. The new SEP WTR build addresses and recovers from any communication breakdown.