Okay, I followed the steps in the video, and what I got out of it was the key log entry:
"TCP_DENIED/307 0 HEAD http://updates.sugarsync.com/versioninfo?userid=3005570 - NONE/- - OTHER-NONE-MyCompany_Internal_Policy-NONE-NONE-NONE-NONE <-,-,-,"-",-,-,-,-,"-",-,-,-,"-",-,-,"-","-",-,-,-,-,"-","-","-","-","-","-",0.00,0,Local,"-","-"> -"
Now apparently HTTP 307 status refers to a Temporary Redirect. This was not immediately helpful. What I did realize though is that (using nslookup) updates.sugarsync.com corresponds to IP 74.201.86.21. Having spent a lot of time looking at the configuration of the WSA, this IP was familiar to me. It was listed under the proxy bypass settings.
So taking a chance, I removed it from the proxy bypass settings and retried SugarSync. It now appears to work. To me this is counter-intuitive, as I would think that anything in this list would not be subject to any scanning or interference from the WSA.
So, I don't understand the problem. I don't know why I was getting the HTTP/307 message in the first place, and why removing that IP from the proxy bypass settings resolved the problem. And I don't know why it was in the proxy bypass settings in the first place, but that's up to the person who first configured it and I'll likely never know the answer.
If you could help me to understand the resolution, I'd appreciate it. Thanks.
